Source

List ownership, import & exit — found from sitemap — ActiveCampaign

Checked for ActiveCampaign on 30 Sep 2026

Technical details

type: page
http status: 200
content hash: sha256:238803c19cf40e328eb421a515ce7e891b8b4e760f5eb6fdd716ba22b5fdd30a
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Bulk sync contacts Report an error

“Upserts up to 250 contacts in one request, matching each one on its email address: an existing contact with that email is updated, otherwise a contact is created.”
Bulk sync async Report an error

“The work is done in the background. The response is a 202 carrying the id of the process that was created, and the contacts are written after the response is sent, so a contact read back immediately afterwards may not reflect the request yet.”
Bulk sync oversize rejected Report an error

“A request holding more than 250 contacts is rejected as a whole and no process is created.”
Bulk sync row errors skipped Report an error

“Rows are otherwise handled independently: a row that cannot be written (no email, a validation failure, a contact the caller cannot access) is logged and skipped without failing the rest of the batch, and the outcome of an individual row is not reported back anywhere in the API.”
Bulk sync required permission Report an error

“Requires the pg_subscriber_add permission.”
Bulk sync contacts param Report an error

“contacts array of objects required The contacts to upsert, at most 250 per request.”
Bulk sync 422 contact limit Report an error

“422 More than 250 contacts were sent, or the account's contact limit would be exceeded. No process is created and no contact is written.”
API base URL Report an error

“https://{youraccountname}.api-us1.com/api/3/contact/bulkSync”

1 fact read from this page is not shown because it could not be confirmed on the page as captured.