Authenticate requests with your API key or OAuth token. Use the scope ‘contacts.readonly’ for read-only access, and add write permissions when creating or updating data.
SALT authenticates to the Contacts API using the same secure token mechanism. Keep credentials safe and rotate tokens regularly.
GET /contacts/:contactId — Retrieve a single contact\nGET /contacts/:contactId/tasks — Get tasks for a contact\nGET /contacts/:contactId/tasks/:taskId — Get a specific task\nGET /contacts/:contactId/notes — List notes for a contact\nGET /contacts/:contactId/notes/:id — Get a note\nGET /contacts/:contactId/appointments — Get appointments for a contact\nGET /contacts/ — List all contacts\nGET /contacts/business/:businessId — Get contacts for a business\ncontacts.write — Scope reference for write access\nPOST /contacts/ — Create a new contact\nPUT /contacts/:contactId — Update a contact\nDELETE /contacts/:contactId — Delete a contact\nPOST /contacts/:contactId/tasks — Create a new task for a contact\nPUT /contacts/:contactId/tasks/:taskId — Update a task\nPUT /contacts/:contactId/tasks/:taskId/completed — Mark a task as completed\nDELETE /contacts/:contactId/tasks/:taskId — Delete a task\nPOST /contacts/:contactId/tags — Add tags to a contact
Trigger: a new or updated contact in SALT prompts a fetch of the contact’s data via GET /contacts/:contactId to ensure SALT reflects the latest information.
Actions: retrieve the contact details, then pull related tasks, notes, and appointments to assemble a complete profile for SALT.
GET /contacts/:contactId
id, name, email, phone, tags
Trigger: when a task is created in SALT, push it to the Contacts API to keep the task list in sync.
Actions: create and update tasks for the contact, enabling progress tracking directly from SALT.
POST /contacts/:contactId/tasks
title, dueDate, status
Trigger: when tags are added or notes are updated in SALT, synchronize changes with the Contacts API.
Actions: add tags via POST /contacts/:contactId/tags and retrieve/update notes as needed to maintain consistency.
POST /contacts/:contactId/tags
tags
Connect SALT to the Contacts API without writing code—use Zapier App Connector or built-in SALT integrations to automate data flows.
Orchestrate end-to-end workflows across contacts, tasks, notes, and tags within SALT for seamless operations.
Scale your automations as your contact data grows, with robust error handling, retries, and observability.
This glossary defines core terms used to connect SALT to the Contacts API, including endpoints, triggers, actions, and data fields.
A person or business record stored in the Contacts API with fields like id, name, email, phone, and tags.
Free-form text notes attached to a contact to capture context or history.
An assignable item linked to a contact, with a title, due date, status, and completion state.
A label applied to a contact for segmentation and routing.
Fetch all contacts, detect duplicates by email, and merge into a single SALT contact record to keep data clean.
Assign tags based on lead status to route contacts into tailored SALT automation paths.
Pull latest notes to trigger timely follow-ups and context-rich conversations in SALT.
Obtain an API key or OAuth token and set the required scopes (e.g., contacts.readonly) for SALT to access data.
Select endpoints relevant to your workflows, such as GET /contacts/:contactId, POST /contacts/, and POST /contacts/:contactId/tasks.
Run tests, verify data accuracy, monitor logs, and deploy automation in SALT.
No coding required. You can connect SALT to the Contacts API using no-code tools like Zapier App Connector or SALT’s built-in connectors to automate data flows between SALT and Contacts API. Start with read operations to surface contact data and progressively add actions as you validate the workflow.\nAs you gain confidence, you can expand to write operations (create/update) by configuring the appropriate scopes and endpoints in your integration setup.
Permissions center around scopes. For read-only operations, use contacts.readonly. For creating, updating, or deleting data, ensure the contacts.write scope is granted and used only where needed. Always follow the principle of least privilege.\nIf your app requires broader access, request elevated scopes and implement token rotation and audit logging to maintain security.
For syncing contacts, use GET /contacts/:contactId to retrieve a single contact and GET /contacts/ to list contacts. To build workflows, combine endpoints like POST /contacts/ to create a contact, POST /contacts/:contactId/tasks to add tasks, and POST /contacts/:contactId/tags to apply labels. \nThese endpoints enable reliable data synchronization and robust automation within SALT.
Handle errors with standard HTTP status codes and structured error messages. Implement retries with exponential backoff for transient errors, log failures for debugging, and alert when rate limits are approached. Validate responses against expected schemas to catch data inconsistencies early.
Yes, updating notes can be done via API when supported by your plan. If a direct note-update endpoint is available (e.g., PUT /contacts/:contactId/notes/:id), use it to modify content. If not, use supported create/replace patterns or update note content via SALT workflows that surface changes to the API. Always test updates in a staging environment first.
Tags are used to categorize and route contacts. You can add tags with POST /contacts/:contactId/tags, remove or update tags through appropriate tag-management endpoints, and leverage tags to trigger automations within SALT. Maintain tag consistency to avoid fragmentation in workflows.
API rate limits depend on your plan and throttle configuration. Monitor response headers for remaining quota and implement backoff strategies to stay within limits. If you anticipate high throughput, consider upgrading or batching requests to optimize performance.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
