Question: A customer wants a ticket’s data called on a certain web page to also be available in other parts of the integration. What could you do to ensure you’re not making too many of the same calls to the API?
- Cache the data on the first call and then grab the data from the cache on subsequent uses.
- Use a batch API to call the data multiple times with one endpoint.
- Write an automation with a webhook API that’ll call the data on subsequent uses.
- Restrict the data to only appear on certain web pages.
Explanation
Storing the first response for reuse prevents repeated requests for the same ticket data. This reduces unnecessary API traffic and helps avoid rate limits. In Amazon Ads workflows, efficient use of Amazon Ads API calls is important when the same resource data is needed in multiple places. Reusing already retrieved data is better than repeatedly calling the same endpoint for unchanged information. This approach improves performance while keeping request volume controlled.
Why the other options are incorrect
Batch API This is not ideal because it still makes API requests instead of reusing already available data.
Webhook API This is incorrect because webhooks are for event notifications, not repeated retrieval of the same stored data.
Data restriction This avoids showing the data in some areas but does not solve the underlying duplicate-call problem.
Source for verification
https://advertising.amazon.com/API/docs/en-us/reference/concepts/rate-limiting
https://advertising.amazon.com/API/docs/en-us/reference/api-overview
The answer(s) to the question is highlighted in the BOLD text above. You can also find more questions and answers related to the exams on the "Integrating With HubSpot I: Foundations" page.