OppBot API
★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbearer7 EndpointsREST
For Agents
Add and manage prospects in an OppBot workspace and push them into outbound nurture sequences using a bearer token, across 7 REST endpoints.
Use for: Add a new prospect from an inbound form into OppBot, Push a prospect into the cold-email sequence after enrichment, Retrieve a prospect's record by ID, List all prospects in the workspace
Not supported: Does not handle email sending infrastructure, calendaring, or CRM record-of-truth — use for OppBot prospect management and sequence enrolment only.
Jentic publishes the only available OpenAPI specification for OppBot API, keeping it validated and agent-ready. OppBot is a sales-engagement platform that nurtures underserved leads into sales-ready opportunities for demand generation teams. The API exposes a small set of endpoints for managing prospects — listing, fetching, creating, updating, and deleting prospect records — and pushing prospects into outbound sequences. Authentication is a bearer token issued by OppBot to each customer workspace.
Install Jentic One Beta
Connect the OppBot API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OppBot 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 OppBot API.
Add a prospect record with contact details and assign ownership
Update a prospect's status, fields, or owner from another system
Push a prospect into a named outbound sequence to start nurture
Retrieve prospect records by ID for sync into a CRM
Remove a prospect record when the lead opts out or converts
Verify a workspace's bearer token through the /me endpoint
Use Cases
Patterns agents use OppBot API for, with concrete tasks.
★ Inbound lead capture to OppBot nurture
When an inbound form fills, an automation agent can call POST /prospect/store to create the OppBot prospect and POST /prospects/sequences/add to drop them straight into a cold-outreach sequence. This shortens the gap between marketing capture and sales follow-up to seconds and removes the need for a CSV upload step.
POST /prospect/store with email, first_name, last_name, then POST /prospects/sequences/add to push the new prospect into the 'inbound-warm' sequence.
CRM-to-OppBot sync
RevOps teams can keep OppBot in step with a CRM by treating the OppBot endpoints as the system of action. New CRM contacts trigger POST /prospect/store, status changes trigger PUT /prospect/update/{id}, and deletions trigger DELETE /prospects/delete/{id}. The /me endpoint provides a quick health check for the integration credentials.
On a CRM webhook, call PUT /prospect/update/{id} with the new title and company so the OppBot record matches the CRM.
Prospect enrichment then sequence
Agents can enrich a prospect with a data provider, write the enriched fields back to OppBot via PUT /prospect/update/{id}, and then call POST /prospects/sequences/add only if the enrichment confidence clears a threshold. This avoids burning sequence sends on weak leads.
Enrich the prospect with Clearbit, PUT /prospect/update/{id} with the enriched company, then POST /prospects/sequences/add only when confidence > 0.8.
AI agent for outbound demand gen
Through Jentic, an AI agent can answer 'add this person to our outbound flow' by translating it into a chained call: POST /prospect/store followed by POST /prospects/sequences/add. The bearer token sits in the Jentic vault, so an SDR-assistant agent can run this multiple times a day without exposing the credential.
Search Jentic for 'add a prospect to oppbot and start a sequence', execute /prospect/store then /prospects/sequences/add for the supplied lead.
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for oppbot api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/me
Test authentication for the workspace token
GET
/prospects
List prospects in the workspace
POST
/prospect/store
Add a new prospect
PUT
/prospect/update/{id}
Update an existing prospect
DELETE
/prospects/delete/{id}
Delete a prospect
POST
/prospects/sequences/add
Add a prospect to a sequence
GET
/me
Test authentication for the workspace token
GET
/prospects
List prospects in the workspace
POST
/prospect/store
Add a new prospect
PUT
/prospect/update/{id}
Update an existing prospect
DELETE
/prospects/delete/{id}
Delete a prospect
POST
/prospects/sequences/add
Add a prospect to a sequence
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OppBot bearer tokens are stored encrypted in the Jentic vault per workspace. Agents receive a scoped execution context — the token is added as the Authorization header at request time and is never present in agent prompts or logs.
Intent-based discovery
Agents search Jentic with intents like 'add a prospect to oppbot' and Jentic returns the POST /prospect/store and POST /prospects/sequences/add operations with their input schemas.
Time to first call
Direct integration: half a day to wire OAuth-style token handling and write CRUD clients. Through Jentic: under 30 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using OppBot API through Jentic.
Why is there no official OpenAPI spec for OppBot API?
OppBot does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call OppBot API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the OppBot API use?
The OppBot API uses an HTTP bearer token issued per workspace. Through Jentic the token is stored encrypted in the vault and added as the Authorization header on each call, so an agent never receives the raw token.
Can I add a prospect to a sequence in one call with this API?
It takes two calls: POST /prospect/store creates the prospect and POST /prospects/sequences/add enrolls them in the named sequence. The two operations are commonly chained together by Jentic agents to mirror a one-step user intent.
What are the rate limits for the OppBot API?
OppBot does not publish a fixed rate limit in this spec. Treat 429 responses with exponential backoff and check the OppBot workspace settings for any per-plan ceilings before running a high-volume sync.
How do I delete a prospect through Jentic?
Search Jentic for 'delete an oppbot prospect', load the DELETE /prospects/delete/{id} operation, and execute it with the prospect ID. The vaulted bearer token is supplied automatically.
How do I test that my OppBot token is working?
Call GET /me. A 200 response with workspace details confirms the bearer token is valid; any 401 or 403 indicates the token is missing, expired, or scoped to a different workspace.
GET STARTED