Submit a request
 
PRODUCT
Privacy Policy |  AAS Advertising Policy | Terms of Use
Cookie Preference
✖

Amazon Ad Server will be sunset in Q4 2024, please visit this page (AAS offboarding information) for offboarding support resources and sunset FAQs. Details shared on that page represent the most up to date information in the Help Center, if you find disparate information in other resources please default to the information in the AAS offboarding information page accordingly.

Please note that on October 1, 2024, the ability to create new campaigns, placements and tag managers was disabled.

Follow
Last Update:
  viewable by end users
  editable by agents

Before receiving access to the AAS production API environment, you will need to use one of our test plans to test your integration. Testing your API integration ensures that the setup is correct and aligns with Amazon Ad Server standards. The testing process also ensures that basic functionality is implemented correctly, and that campaigns that you traffic using the API will work as expected.

Attached are the test plans for the Reporting API, Trafficking API, and Creative API. To perform the necessary testing, download the relevant documents:

Please note these important points when working with the AAS API:

  • Once a session token is generated, each API request includes the token and API key in the request headers in the Authorization field.

  • When accessing the AAS REST API, the application uses the session token/sessionId and API key to authenticate each request.

  • The AAS password policies and rules apply to both API and application users. Make sure that you renew your API password every 120 days. If your password has expired, an error message will be displayed when you try to log in.

  • The default throttling limit for API calls is 10,000 every 24 hours. Ad Server Support can configure the throttling limit according to the estimate of the number of calls per day/month.

  • A session token is valid for three hours, regardless of the idle/active state of the session. Once the token expires, any requests receive the relevant error message; the user will need to refresh the token.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments