How to Set-Up the Integration Based on Auth Type AWS Signature

This documentation provides a comprehensive, step-by-step guide to understanding the Amazone Seller Central setup process. For example purposes, we have chosen "Amazone Seller Central" as our focus application.

Follow these steps to build the app integration of other Amazon app services.

• App Details and Auth Configuration:

We followed the Amazon Seller Central API docs for selecting the Auth type as AWS Signature. Learn more
To get the above details such as Client ID, Client secret, Access Key, and Secret Key, you need to register the app in the Amazon developer portal.

1. Authorize URL - Enter your app Authorize URL to retrieve the authorization code here e.g. https://www.facebook.com/v10.0/dialog/oauth
2. Token URL - Enter your app Token URL to exchange the authorization code for an access token here e.g. https://graph.facebook.com/v10.0/oauth/access_token
3. Application ID - Enter the Application ID generated for your developer app in the AWS developer area.
4. Access Key - Enter the access key generated while creating the user from the AWS console.
5. Secret Key - Enter the secret key generated while creating the user from the AWS console.
6. Client ID - Enter your app Client ID.
7. Client Secret - Enter your app Client Secret.

• How to Configure Triggers Event:

Trigger - New Order (Polling method)
In this type of integration, you need to configure Get API similar to Post webhook trigger integration to fetch new data in a specific interval.

1. In the above screenshot, we set the parameter as "OrderStatuses" to add a multi-select dynamic dropdown.
2. Set the Request Body JSON.
3. Save and Send the test request and fetch the response.

Simplify Array Response allows you to choose an array key from the above step and simplify the array response in the key-value pair.

The New Record Order Setting section as shown below allows you to tell Pabbly Connect about how it can recognize the fetched record is new.

1. Unique Record ID: Choose a unique record ID from the received response of the above step that uniquely identifies the new record.
2. Sorting Order: Since the fetched records may be single or a bunch so, it is important to identify the record as new it may be based on any specific field of the new data like date value. Based on its value, the system compares the old data with this one and processes it for triggering if it finds any difference.

In case, there is no such field value present in the response, you can opt for By Position and locate the new record's presence either at the top or at the bottom of the bunch of JSON responses.

Trigger Frontend View:

• How to Configure Action Event:

Action - Get Order Details
Type - Get

Action Frontend View:

For further details, refer to this guide for creating new actions and triggers in your application. Learn more

Refer to the video below for instructions on creating your app with a similar authentication type: Learn more