ITiterable
events

Bulk track events

Events are created asynchronously and <b>processed separately from single event (non-bulk) endpoint</b>. To make sure events are tracked in order, send them all to the same endpoint (either bulk or non-bulk). <br/><br/>There is a soft limit (default is 8,000) on the number of unique fields a custom event can have. For events of the same name, identically named data fields must be of the same type.<br/><br/>Learn about <a href="https://support.iterable.com/hc/articles/29156459027348">identifying users by <code>userId</code> and <code>email</code></a>.<br/><br/><b>Rate limit</b>: 10 requests/second, per project.

post/api/events/trackBulk

Request

  • Base URL
    https://api.iterable.com
  • Auth
    API key in header Api-Key

Request body

Response

successful operation

createdFieldsstring[]

Fields that were created because <code>createNewFields</code> was <code>true</code> or <code>createNewFields</code> was not set and the project is configured to add unrecognized event fields.

disallowedEventNamesstring[]
failCountinteger required

Number of events that could not be updated. See <code>failedUpdates</code> for more details.

filteredOutFieldsstring[]

Fields that were dropped because <code>createNewFields</code> was <code>false</code> or <code>createNewFields</code> was not set and the project is configured to drop unrecognized event fields.

invalidEmailsstring[]

Malformed <code>email</code> addresses. This field is deprecated — use <code>failedUpdates</code> instead.

invalidUserIdsstring[]

<code>userId</code> values that were not found. This field is deprecated — use <code>failedUpdates</code> instead.

successCountinteger required

Number of events that were updated in response to the request.

Changes

No recorded changes to this operation across all 4 revisions of this API.