Agendor API
Browse all Agendor APIs★ Only Publicly Available OpenAPI DocumentCRMDeal PipelineapiKey30 EndpointsREST
For Agents
Manage people, organizations, deals, tasks, and products in the Agendor Brazilian CRM with native CPF/CNPJ support and pipeline workflows.
Use for: I need to create a new lead in Agendor with a CPF, Upsert an organization record by CNPJ, Move a deal from 'Qualificação' to 'Proposta', Create a follow-up task for a sales rep
Not supported: Does not handle email marketing campaigns, call recording, or invoice issuance — use for Brazilian B2B CRM contact, organization, deal, and task workflows only.
Jentic publishes the only available OpenAPI specification for Agendor API, keeping it validated and agent-ready. Agendor is a Brazilian CRM built around the realities of B2B sales in Brazil — CPF and CNPJ identifiers, Brazilian address formats, and Portuguese-language workflows. The v3 API exposes 30 endpoints covering people, organizations, deals, tasks, products, users, and account configuration, with upsert variants for syncing data from external systems and configuration endpoints for shared sales settings.
Install Jentic One Beta
Connect the Agendor API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Agendor 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 Agendor API.
Create and upsert people records with CPF and Brazilian address fields
Manage organizations with CNPJ identification and Brazilian tax metadata
Move deals through the sales pipeline with stage and status transitions
Create and assign tasks to sales reps with due dates and reminders
Maintain a product catalog used in Agendor deal line items
Read and update Agendor user records and team assignments
Configure shared CRM settings like deal stages and lead sources
Use Cases
Patterns agents use Agendor API for, with concrete tasks.
★ Lead Capture Sync from Marketing
Brazilian marketing tools push captured leads into Agendor via POST /people/upsert and /organizations/upsert, keyed on CPF or CNPJ to dedupe against existing records. The upsert endpoints make sync jobs idempotent so the same lead form submission can replay safely. Marketing automation tools use this to keep Agendor as the single sales source of truth.
For each new marketing lead, upsert the person via POST /people/upsert (keyed on CPF) and the organization via POST /organizations/upsert (keyed on CNPJ), then create a follow-up task for the assigned rep
Pipeline Reporting and Forecasting
Sales ops teams pull deals via GET /deals into BI tools to forecast Brazilian revenue by stage, owner, and product. Combined with /deals/{id} for full detail and the configuration endpoints for stage names, this powers dashboards that match how Brazilian sales teams actually report — in Portuguese, with stages mapped to local sales motions.
List all deals via GET /deals filtered to current quarter, then group by stage and owner for a Portuguese-language forecast dashboard
Task Automation for Sales Reps
Agendor's tasks endpoints let an integration auto-create follow-up tasks based on deal events — stage changes, dormant deals, or expiring quotes. Reps see the tasks inside Agendor's existing UI rather than juggling a second tool, which matters in Brazilian B2B teams that resist tool sprawl.
When a deal moves into the 'Proposta' stage, create a task on POST /tasks for its owner with a 3-day due date and the proposal-followup template
AI Agent Sales Operations
Through Jentic, an agent embedded in WhatsApp or a Brazilian sales-enablement tool can read deal status, update people records, and create tasks in Agendor without holding the customer's API token. The agent searches Jentic by intent in Portuguese or English, executes the call, and Jentic injects the Authorization header at runtime.
Search Jentic for 'list agendor deals', load the GET /deals schema, and execute it filtered by owner to produce a daily pipeline summary for a sales rep
Key Endpoints
30 endpoints — jentic publishes the only available openapi specification for agendor api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/people
List people (contacts)
POST
/people/upsert
Upsert a person by external identifier
GET
/organizations
List organizations
POST
/organizations/upsert
Upsert an organization by CNPJ or external id
GET
/deals
List deals across the pipeline
GET
/deals/{id}
Retrieve a specific deal
GET
/tasks
List tasks
GET
/people
List people (contacts)
POST
/people/upsert
Upsert a person by external identifier
GET
/organizations
List organizations
POST
/organizations/upsert
Upsert an organization by CNPJ or external id
GET
/deals
List deals across the pipeline
GET
/deals/{id}
Retrieve a specific deal
GET
/tasks
List tasks
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Agendor API tokens are stored encrypted in the Jentic vault and injected into the Authorization header at execution time. Agents never hold the raw token, which matters because the token grants full read/write to the Brazilian sales pipeline.
Intent-based discovery
Agents search Jentic by intent (e.g., 'list agendor deals' or 'criar tarefa no agendor') and Jentic returns the matching operation with its parameter schema, so the agent picks the right endpoint without reading Agendor docs.
Time to first call
Direct Agendor integration: 1-2 days for auth, the upsert flow, and Portuguese field mappings. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Payments platform used to charge deals once they close.
Pair so an agent can charge a Stripe customer when an Agendor deal moves to 'Ganha'.
FAQs
Specific to using Agendor API through Jentic.
Why is there no official OpenAPI spec for Agendor API?
Agendor does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Agendor 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 Agendor API use?
Agendor uses an API token sent in the Authorization header. Through Jentic, the token is stored encrypted in the credential vault and injected at execution time, so the agent never holds the raw token.
Can I dedupe organizations by CNPJ in Agendor?
Yes. POST /organizations/upsert accepts a CNPJ as the natural key and either creates a new record or updates the existing one with the supplied fields. Use POST /people/upsert for CPF-keyed person dedupe.
What are the rate limits for the Agendor API?
The public spec does not include explicit rate limits. Agendor enforces per-account throttling — keep batch syncs paced to a few requests per second per account and back off on HTTP 429.
How do I move a deal stage through Jentic?
Search Jentic for 'update agendor deal', load the schema for the deal-update endpoint, and execute it with the deal id and target stage. Jentic returns the updated deal payload to the agent.
How is this Agendor spec different from agendor-api on Jentic?
Both target the v3 base URL. This 'agendor' spec is the broader 30-endpoint surface including products and configuration; 'agendor-api' is a 21-endpoint subset focused on the core sales-pipeline objects. Pick this one when you need product or configuration access.
GET STARTED