Skip to main content
Use the method shown on each endpoint: GET to read, POST to create, PATCH to update, and DELETE to remove an item. Contact creation can also update an existing contact matched by email.

Send JSON

For POST and PATCH, send a JSON object with Content-Type: application/json:
Send only the fields documented for that endpoint. For updates, leave out fields you want to keep. Use null to clear an optional text field. Arrays such as tags and contactDetails replace the whole list when supplied; [] removes all items.

Successful responses

Workspace, contact, and team-member responses place the result inside data. A list also includes pagination. A successful delete returns 204 No Content without a body. Contact and team-member create endpoints return 201 when an item is new or 200 when an existing item is matched. Check data.created to tell which happened. Matching an existing contact updates the supplied fields; matching an existing team member returns them unchanged.
Zapier’s trigger endpoints use a different response shape: contact samples are a bare array, and a subscription returns a bare object. Each Zapier endpoint shows its response.

Pagination

The contact and team-member list endpoints return up to 100 items per request. For example, request one contact:
This example shortens the contact’s fields:
Add the number of items received to offset for the next request. Stop when hasMore is false. Use the same sort order throughout. Lists can change while you page through them, so use each item’s id to avoid processing it twice. Contacts also support sorting by creation or update date. There is no date-range or search filter on these list endpoints.

Errors

Errors from supported endpoints contain a code and message:
Some errors include details with extra information. Use the HTTP status and error code to decide what to do. An unsupported HTTP method returns 405 Method Not Allowed and may not use this JSON error format.

Rate limits and retries

Limits apply per API key: A 429 response includes Retry-After in seconds. Wait at least that long before retrying.
After a timeout or server error during a write, check whether the change succeeded before repeating it. Repeating contact creation without an email can create duplicate contacts.

Dates and IDs

Dates use ISO 8601, such as 2026-07-28T09:30:00.000Z. Empty optional fields are usually null. Store IDs as strings and use the IDs returned by Tapify in later requests.