canonical: https://jentic.com/apis/datananas.com/sarbacane-engage # Datananas Sarbacane Engage API Sarbacane Engage (formerly Datananas) is a sales engagement platform for managing outbound prospecting at scale. The 94-endpoint REST API exposes contacts, multi-step sequences, message templates, automated workflows, team and user management, and integration grants - everything needed to build, send, and measure prospecting campaigns from outside the Sarbacane UI. Bearer token auth and JSON throughout make it straightforward to wire into existing CRMs and AI-driven outreach tooling. ## For AI agents Manage prospecting contacts, build multi-step email sequences, send messages from templates, and automate engagement workflows in Sarbacane Engage. ## Scope Does not handle SMS, voice dialling, or transactional email delivery - use for outbound sales engagement sequences and prospecting contact management only. ## Capabilities - Create and segment prospecting contacts via POST /contacts and bulk endpoints - Build multi-step engagement sequences and enrol contacts into them - Compose and version reusable message templates - Authenticate users and grant or revoke OAuth integrations via /users/integrations endpoints - Manage team membership and role assignments through /users/{id}/roles - Bulk-check contact deliverability before adding them to a sequence with POST /contacts/bulk-check ## Use cases ### CRM-Driven Outbound Sequences Sales teams sync their CRM into Sarbacane Engage so that newly qualified leads are enrolled into a multi-step outbound sequence automatically. POST /contacts/bulk creates the prospects, POST /contacts/bulk-check validates deliverability, and a sequence-enrolment call moves them into the engagement workflow. The pattern keeps the CRM as system of record while Sarbacane handles cadence, deliverability, and reply detection. Example prompt: POST /contacts/bulk with 50 newly qualified leads, run POST /contacts/bulk-check, then enrol the verified contacts in sequence ID 'q3-saas-outreach' ### Template Lifecycle Management Marketing ops teams keep email templates versioned outside the Sarbacane UI by scripting against the templates endpoints. Templates are created, updated, and rotated programmatically so that the same copy can be reused across multiple sequences and A/B tested without manual UI edits. Centralised template management also makes it easier to audit messaging consistency across teams. Example prompt: Create a new template 'follow-up-v3' with the provided subject and HTML body, then update sequence step 2 to reference it ### Integration Grant Auditing Security teams use the /users/integrations endpoints to audit which third-party integrations users have authorised against Sarbacane and to revoke them when employees leave or rotate roles. POST /users/integrations/grant provisions a connection, DELETE /users/integrations/revoke removes it, and the audit trail surfaces in the user record. Example prompt: List all users with active Gmail integrations and call DELETE /users/integrations/revoke for any user not on the approved list ### AI Agent Outbound Operations AI sales agents call Sarbacane Engage through Jentic to enrol new prospects in sequences, generate template variants, and pull engagement metrics for reporting. Jentic isolates the bearer token in its vault so the agent operates only on contact and sequence IDs. This avoids exposing user-scoped credentials to the LLM at any point. Example prompt: Find contacts that opened the last campaign but did not reply, generate a personalised follow-up using a template, and enrol them in sequence 'reengage-q3' ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /contacts | Create a single prospecting contact | | POST | /contacts/bulk | Bulk-import contacts | | POST | /contacts/bulk-check | Validate deliverability for a list of contacts | | POST | /users/login | Authenticate a user and receive a bearer token | | POST | /users/refresh | Refresh an existing bearer token | | PATCH | /users/{id}/roles | Update role assignments for a user | | DELETE | /users/integrations/revoke | Revoke a third-party OAuth integration | ## Key resources - **Contacts** — Create, update, bulk-import, and validate prospecting contacts - **Users** — Manage user accounts, authentication, password resets, and roles - **Integrations** — Grant and revoke OAuth integrations such as Gmail and Outlook - **Sequences** — Multi-step outbound campaigns and contact enrolment - **Templates** — Reusable email templates referenced by sequence steps ## Why Jentic - **Setup:** Wiring the Sarbacane Engage API by hand means learning its bearer auth against api.datananas.com, running its login and refresh flow, and building the contact and retry plumbing for prospecting sequences yourself. Through Jentic you install once, import the Sarbacane Engage API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Sarbacane Engage carries its contact details in the request body while only user administration takes an id in the path, so limit the agent to the operations it needs, such as creating contacts or bulk-checking emails. You choose the operations it may call, so changing user roles or revoking integrations is not included unless you add them. - **Credential handling:** Your Sarbacane Engage bearer token and any third-party integration secrets are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'enrol a prospect in a sales sequence' or 'bulk-validate email addresses', and Jentic returns the matching Sarbacane Engage operation with its input schema so the agent calls the right endpoint without browsing the operation catalogue. ## Related APIs - **Outreach.io** — Outreach.io is a US-focused enterprise sales engagement platform with similar sequence and contact APIs. - **Salesloft** — Salesloft is another major sales engagement platform with cadences, calls, and email tracking APIs. - **HubSpot** — HubSpot CRM is a common system of record that syncs leads into Sarbacane sequences. ## FAQ ### What authentication does the Sarbacane Engage API use? Sarbacane Engage uses HTTP bearer token authentication, with the token issued via POST /users/login or refreshed via POST /users/refresh. Through Jentic, the bearer token lives in your Jentic One instance and is injected at call time. ### Can I bulk-import contacts via the Sarbacane Engage API? Yes. POST /contacts/bulk accepts a list of contact records in a single call, and POST /contacts/bulk-check validates email deliverability before enrolment. This is the right path for syncing CRM exports. ### What are the rate limits for the Sarbacane Engage API? The OpenAPI spec does not declare per-endpoint rate limits; check your Sarbacane Engage plan in docs.datananas.com for current quotas, and back off on 429 responses. ### How do I enrol a contact in an outbound sequence through Jentic? Search Jentic for 'enrol a contact in a sales sequence', load the sequence-enrolment operation, and execute it with the contact ID and sequence ID. Jentic injects the bearer token so the agent never handles raw credentials. ### Can I revoke a user's third-party integration via the API? Yes. DELETE /users/integrations/revoke removes a previously granted OAuth integration (such as Gmail) for the authenticated user, useful for offboarding workflows and security audits. ### Is Datananas the same as Sarbacane Engage? Yes. Datananas was rebranded as Sarbacane Engage, but the api.datananas.com host and existing tokens continue to work. New integrations should still target this base URL. ### Can I limit what my agent is allowed to do with the Sarbacane Engage API? Yes. Because Jentic One is self-hosted, your own rules decide which Sarbacane Engage operations and which stored bearer token the agent may use. You can allow it to create and bulk-import contacts via POST /contacts and POST /contacts/bulk and validate emails with POST /contacts/bulk-check, while excluding user-administration paths like PATCH /users/{id}/roles or DELETE /users/integrations/revoke. Those higher-privilege operations stay off limits unless you explicitly add them to the agent's allowed set.