Skip to main content
POST
cURL
Send up to 5,000 custom activities in one request, with the whole request at most 5 MB. The request is checked and answered straight away with a batch id, and the events are stored in the background, usually within seconds. Use Get Batch Result to see what happened to each one. One batch request counts once against the rate limit, however many events it carries.

Request

Each event needs at least one identifier that the activity type links on: phone, email or LinkedIn URL for contact types, domain for company types. The person or company must already exist. Logging an activity never creates a contact.

Responses

202, the batch is accepted:
400, one or more events are invalid. Nothing from the batch is stored. Fix the listed events and send the whole batch again:
422, the source is unknown or not enabled for one of the activity types. 429, the workspace has reached its daily event limit. The response says when it resets and carries a Retry-After header:
413, the request is larger than 5 MB. Send fewer events per request. 503, the batch could not be queued. Nothing was stored; send it again.
Send one or two batches at a time rather than all at once, and back off on a 429. Allow at least 60 seconds for a response: a full batch takes several seconds to check.

Authorizations

X-API-KEY
string
header
required

Response

200

No response body