- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think the easiest way may be to loop through the transaction numbers and do a getTransactionDetails method call for each. The orders page would do this on each page load. As our transactions list gets long, this may end up requiring 100 or more API calls within the space of a few seconds or less.
Does anyone know if there is a limit to the # of API calls you can make in any given timeframe before you trigger some flag or limit that will cause you to be denied?
There is an older question about this on the thread below-
https://community.developer.authorize.net/t5/Integration-and-Testing/Transaction-Details-API-service...
Solved! Go to Solution.
โ12-21-2018 08:58 AM - edited โ12-21-2018 08:59 AM
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Renaissance,
There is no limit to the number of calls that are allowed, however some things should be taken into consideration.
The time between when the transaction processes and when it will be returned with a getTransactionDetailsRequest can vary based on current processing volume and replication of the data across all of the datacenters. Meaning, if the transaction has processed and then you request the transaction details via API immediately, depending on which datacenter you hit it may or may not have replicated yet.
I would recommend putting a delay between the createTransactionRequest and the getTransactionDetailsRequest of 10-15 seconds. This is longer than is needed really, but will prevent any errors from returning when/if the replication is taking longer due to higher system/network load than usual.
Additionally, if malformed/erroneous data is submitted, or you're running an automated script unmanaged, which is causing errors to occur you may begin to see timeouts or other errors and your requests can be blocked to protect network integrity.
I hope this information is helpful.
Thank you,
Elaine
โ12-22-2018 01:11 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Renaissance,
There is no limit to the number of calls that are allowed, however some things should be taken into consideration.
The time between when the transaction processes and when it will be returned with a getTransactionDetailsRequest can vary based on current processing volume and replication of the data across all of the datacenters. Meaning, if the transaction has processed and then you request the transaction details via API immediately, depending on which datacenter you hit it may or may not have replicated yet.
I would recommend putting a delay between the createTransactionRequest and the getTransactionDetailsRequest of 10-15 seconds. This is longer than is needed really, but will prevent any errors from returning when/if the replication is taking longer due to higher system/network load than usual.
Additionally, if malformed/erroneous data is submitted, or you're running an automated script unmanaged, which is causing errors to occur you may begin to see timeouts or other errors and your requests can be blocked to protect network integrity.
I hope this information is helpful.
Thank you,
Elaine
โ12-22-2018 01:11 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ12-26-2018 04:27 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
โ12-26-2018 04:28 PM

