canonical: https://jentic.com/apis/agendor.com.br/agendor-agendor # Agendor API 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. ## For AI agents Manage people, organizations, deals, tasks, and products in the Agendor Brazilian CRM with native CPF/CNPJ support and pipeline workflows. ## Scope Does not handle email marketing campaigns, call recording, or invoice issuance - use for Brazilian B2B CRM contact, organization, deal, and task workflows only. ## Capabilities - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: 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. Example prompt: 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 | 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 | ## Key resources - **People** — Contact records with CPF and Brazilian address fields - **Organizations** — Company records with CNPJ identification - **Deals** — Sales opportunities through the Agendor pipeline - **Tasks** — Follow-up tasks assigned to users - **Products** — Product catalog used on deals - **Users** — Agendor user records and roles - **Configuration** — Account-level CRM configuration ## Why Jentic - **Setup:** Wiring the Agendor API by hand means managing its token in the Authorization header and coding calls across people, organizations, deals, and tasks including upsert operations. Through Jentic you install once, import the Agendor API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Agendor puts the deal id in the URL path for deal reads (/deals/{id}), while upserts of people and organizations take their input in the body, so a rule can pin the agent to reading a specific deal or limit it to the upsert operations it needs. You choose which operations are in the allowed set, so anything you leave out is not reachable. - **Credential handling:** Your Agendor API token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list Agendor deals' or 'criar tarefa no Agendor', and Jentic returns the matching operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Agendor API** — Subset spec covering core sales pipeline objects without products or configuration. - **Pipedrive API** — Pipeline CRM with similar deal-stage primitives, popular outside Brazil. - **HubSpot Account Info API** — Broader CRM and marketing platform; alternative for non-Brazil-specific workflows. - **Stripe API** — Payments platform used to charge deals once they close. ## FAQ ### 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 with Jentic One, the self-hosted execution layer. ### 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. ### Can I limit what my agent is allowed to do with the Agendor API? Yes. Because you run Jentic One yourself, your own rules decide which Agendor operations and credentials the agent may use, and anything you leave out of the allowed set is not reachable. Agendor puts the deal id in the URL path for deal reads such as GET /deals/{id}, while people and organization upserts take their input in the request body, so you can pin the agent to reading one specific deal or restrict it to just the upsert operations it needs. The Agendor token is injected only when the agent calls an operation you have permitted.