Agendor API
Browse all Agendor APIs★ Only Publicly Available OpenAPI DocumentCRMDeal PipelineapiKey58 EndpointsREST
For Agents
Manage Brazilian-Portuguese sales pipelines: create and update people, organizations, and deals; log tasks and activities; advance deals through funnel stages.
Use for: I need to create a new sales lead in the Brazilian CRM, Find all deals stuck in the proposal stage for more than 30 days, Upsert an organization record without checking if it already exists, List the open tasks assigned to a specific salesperson
Not supported: Does not handle invoicing, payment collection, marketing automation, or customer support tickets — use for sales pipeline and contact management only.
Jentic publishes the only available OpenAPI specification for Agendor API, keeping it validated and agent-ready. Agendor is a Brazilian CRM built for inside and outside sales teams, offering structured access to people, organizations, deals, tasks, products, and activity history. The v3 REST API exposes 58 endpoints for managing the full sales pipeline, including upsert operations, deal stage progression, custom fields, and team-scoped data. Responses follow a consistent JSON shape with data, meta, and links envelopes for pagination across collections.
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.
Upsert people and organizations to keep contact records in sync without duplicate detection logic
Move deals through pipeline stages and record win/loss reasons against /deals/{id} endpoints
Schedule and complete tasks linked to a person, organization, or deal with due dates and ownership
Read deal value, products, and custom field data for forecasting and reporting workflows
Filter and paginate collections of people, organizations, and deals by owner, stage, or activity date
Attach products and line items to deals to track pipeline value at the SKU level
Use Cases
Patterns agents use Agendor API for, with concrete tasks.
★ Lead Capture from Website Forms
Push inbound leads from web forms or marketing platforms into Agendor as new people and deal records. Agents call POST /people followed by POST /deals to attach the lead to the correct pipeline and stage. Upsert endpoints prevent duplicates when the same email submits multiple times. Integration is suitable for low-volume B2B sales teams running on the Brazilian market.
Create a person with name 'Maria Silva' and email 'maria@example.com.br', then create a deal valued at R$15,000 attached to that person in the 'Qualificação' stage
Pipeline Stage Automation
Move deals automatically between pipeline stages based on external triggers such as proposal sent, contract signed, or payment received. Agents read the current stage from /deals/{id}, then PUT updates to advance the deal and create follow-up tasks. Useful for sales operations teams reconciling Agendor with billing or e-signature platforms.
Update deal 12345 to the 'Ganhos' stage with closing value R$45,000 and create a task 'Send onboarding kit' due in 2 days
Sales Reporting and Forecasting
Pull deal, person, and organization data into BI tools or LLM-driven dashboards to forecast pipeline revenue and territory performance. Agents page through /deals with stage and owner filters to reconstruct the open funnel, then enrich with product line items. Suited to teams replacing or augmenting Agendor's native reports.
List all deals where stage equals 'Proposta' and owner_id equals 78, then sum the value field for forecasting
Agent-Driven CRM Hygiene
Use a Jentic-connected agent to deduplicate people and organizations, complete missing fields, and close stale deals on a schedule. The agent searches for the upsert and update operations, loads the schemas, and executes batch corrections. This removes the need for hand-built ETL scripts and keeps the pipeline data clean for downstream forecasting.
Find all people created in the last 90 days with missing phone numbers, then upsert each record after looking up the phone via an enrichment API
Key Endpoints
58 endpoints — jentic publishes the only available openapi specification for agendor api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/people/upsert
Create or update a person without duplicate checks
POST
/organizations/upsert
Create or update an organization without duplicate checks
GET
/deals
List deals with stage, owner, and date filters
POST
/deals
Create a deal attached to a person or organization
PUT
/deals/{id}
Advance a deal to the next pipeline stage
POST
/people/{person_id}/tasks
Create a follow-up task for a person
POST
/people/upsert
Create or update a person without duplicate checks
POST
/organizations/upsert
Create or update an organization without duplicate checks
GET
/deals
List deals with stage, owner, and date filters
POST
/deals
Create a deal attached to a person or organization
PUT
/deals/{id}
Advance a deal to the next pipeline stage
POST
/people/{person_id}/tasks
Create a follow-up task for a person
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Agendor API tokens are stored encrypted in the Jentic vault. Agents receive scoped execution requests — the raw Token header value never enters agent context or logs.
Intent-based discovery
Agents search by intent (e.g. 'create a deal in the Brazilian CRM') and Jentic returns the matching Agendor operations with their JSON Schemas, so the agent can call POST /deals or POST /people/upsert without browsing docs.
Time to first call
Direct Agendor integration: 1-2 days for token handling, pagination, and Portuguese field name mapping. Through Jentic: under 30 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Complementary
Stripe API
Payment processing that pairs with deal-won events to charge the customer
Use Stripe when an Agendor deal moves to 'Ganhos' and you need to invoice or charge the linked person or organization.
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 passed in the Authorization header with the Token scheme, e.g. Authorization: Token your-token-here. Through Jentic the token is held in the credential vault and never enters the agent's context — agents request a scoped execution and Jentic injects the header at call time.
Can I create a deal and link it to a contact in one call with the Agendor API?
Not in a single request. Use POST /people (or POST /people/upsert) to create the contact first, then POST /deals with the person_id field set on the body. The /deals endpoint accepts both person and organization linkage in the same payload.
What are the rate limits for the Agendor API?
Agendor's public documentation does not list a numeric rate limit on the v3 API; the service throttles abusive traffic at the network layer. Build retry-with-backoff into your agent and check response headers if a 429 is returned.
How do I move an Agendor deal to a different pipeline stage through Jentic?
Use the Jentic search query 'update agendor deal stage'. Jentic returns the PUT /deals/{id} operation; load its input schema, supply the deal id and the target stage_id, and execute. The deal moves immediately and the response includes the updated stage object.
Does the Agendor API support pagination on list endpoints?
Yes. List endpoints under /people, /organizations, and /deals accept a page query parameter starting from 1, with up to 100 items per page. The response includes a meta.totalCount field and links.next / links.prev for navigation.
Can I upsert a person to avoid duplicate Agendor records?
Yes. POST /people/upsert and POST /organizations/upsert match on a key field (typically email or document number) and either create a new record or update the matching one, returning the canonical id either way.
GET STARTED