In an effort to continue improving our documentation and developer experience, we identified specific areas in our code that are currently providing very vague response status information where they could be more explicit.
We therefore decided to replace several generic 400 errors. The following changes will be implemented on Monday morning, July 8, Pacific time.
- All create endpoints for records, either singular or jobs (bulk), will return a 429 instead of a 400 when the product limit for the number of records is reached.
- The Jobs endpoint will return a 413 instead of a 400 when too many records are included in a single request (you have exceeded the maximum number of entities in a request).
- Errors that displayed
400 The account being accessed could not be determinedwill now return a 500 error.
Thank you for partnering with us as we continue our work to make Custom Objects APIs an increasingly developer friendly experience!