Invalid API Requests

Invalid API Requests


What you see below is the list of error messages shown when API calls are rejected due to the sending limits mentioned in our API documentation. In addition to the responses we give to your API calls, our system is set up to automatically notify you about API limit infractions we find problematic. When available, you will be given samples of the data we received that exceeded the limits. Note that the middle of the sample data we send may be truncated (" ...<truncated>... ") in order to limit the size of the exported error data. To prevent data loss, you'll want to address the issues mentioned in that file and/or listed below as soon as possible whenever they come up.

Errors related to identify calls (sending People profile data)

  • id attribute must be present
  • id attribute must be a string value
  • id attribute cannot be an empty string
  • cannot identify more than 30 attributes in one request
  • attribute name cannot be longer than 150 bytes
  • value for attribute 'ATTRIBUTE-NAME' cannot be longer than 1000 bytes

Errors related to track calls (sending event data)

  • event name must not be blank
  • event name cannot be longer than 100 bytes
  • event name must be less than 500 characters
  • event data must be a hash
  • event data cannot be longer than 10000 bytes

Why only 30 attributes and 1000 bytes per attribute name?

These limits have been put in place to ensure the performance and reliability of your Customer.io account.

What happens if I don't change anything?

If you get these errors and do not fix your integration so that, for example, it only sends a maximum of 30 attributes per identify call and a maximum of 1000 bytes for attribute values, these types of requests will continue to fail.

If you have a use-case which needs these limits relaxed and it doesn’t interfere with our ability to provide the service, we can raise them on request. Please contact us so that we can discuss your use-case in detail.

Was this article helpful?