ADS API - Suggestion for Next version
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As a recommendation for the next API version - please avoid using GET as a method for submitting the report and instead please revert back to a POST request. First, for the GET request the parameters for arrays do not follow HTTP standards in the current V2 version and instead of handling arrays like most servers, it is not compliant with entity_id[]=XXXX&entity_id[]=XXXY&entity_id[]=XXXZ but instead does a not standard format and requires that they be sent through as entity_id=XXXX&entity_id=XXXY&entity_id=XXXZ which causes issues with almost all standard API libraries for request formatting and requires custom query builders to work. Additionally, GET requests cannot support body text, nor can they take the supposed maximum number of ids as your documentation claims to support due to the limit in URI length for most servers and load balancer software which is approximately 2000 characters as a general rule - your own servers reject things that go too long. Considering your use GUIDs for each entity id, which each contains 36 characters alongside the rest of the various filters available and the need to specify fields, it becomes unusable as a protocol method for larger reports - this requires additional requests, queries, and overall network bandwidth in order to process - the result is untenable and frequently larger queries get rejected.
- Labels:
-
Possible Bug
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page