Datananas Sarbacane Engage API
66
AI ReadinessAI-Aware (B)66/100
Official vendor OpenAPI document · agent-readyMarketingMarketing Automationbearer94 EndpointsREST
For Agents
Manage prospecting contacts, build multi-step email sequences, send messages from templates, and automate engagement workflows in Sarbacane Engage.
Use for: Add a prospect to an outbound email sequence, Bulk-import a CSV of contacts into Sarbacane Engage, Create a new message template for a follow-up email, Pause a sequence for a specific contact
Not supported: Does not handle SMS, voice dialling, or transactional email delivery - use for outbound sales engagement sequences and prospecting contact management only.
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.
Install Jentic One Beta
Connect the Sarbacane Engage API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sarbacane Engage API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdatananas.com%2Fsarbacane-engage" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdatananas.com%2Fsarbacane-engage" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Sarbacane Engage API.
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
Patterns agents use Sarbacane Engage API for, with concrete tasks.
★ 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.
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.
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.
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.
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
94 endpoints — sarbacane engage (formerly datananas) is a sales engagement platform for managing outbound prospecting at scale.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
S
Sarbacane Engage API
- AI-Aware (B)66/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience86
Agent Usability60
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
41%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
58%
Summary Coverage
Coverage of summaries across operations/tags/info.
86
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
86%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Sarbacane Engage API through Jentic.
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.
GET STARTED