Rest API Rate Limit
Hi I'm developing a little desktop application to help out a client who needs to semi-automate some of their day-to-day admin tasks. One of the tasks is to set profile background images for a l...
Forum Discussion
Hey geekcubed,
I don't believe you are running into a throttling issue. You can verify that it's not a throttling issue by adding an artificial delay between calls (maybe about a second between each call), if you still see a timeout, then it's not a throttling issue.
Can you tell me a bit more about how you make the calls, specifically:
1) What are the timeout parameters on your side? (after how long will a call timeout)
2) Where is your application hosted?
Using Endpoints is probably a better solution than making multiple API calls:
In the Lithium community application we allow our customers to create endpoints. You can read more about them here. If you work with someone who has access to Studio in the Lithium application, they will be able to set up an endpoint to make all the calls (thus reducing number of calls made from the external application). From the external application, you will then only need to call the endpoint rather than all the rest APIs.
Thank you,
Yuri
The application is a desktop app - it's being used on machines in various physical locations in the UK. The underlying code is performing the requests via System.Net.WebRequest objects which have default timeout of 100 seconds.
I'm just digging in to the .Net documentation and it might be that I'm hitting some internal limits when making concurrent requests to the same host, but I will have a play with throttling things on the application side and see if that sheds any more light on things.
