canonical: https://jentic.com/apis/agendor.com.br/agendor-agendor-api # Agendor API Jentic publishes the only available OpenAPI specification for Agendor API, keeping it validated and agent-ready. This 21-endpoint variant focuses on the core sales-pipeline objects in the Agendor Brazilian CRM: organizations, people, deals, tasks, and users. It targets the same v3 base URL but trims out the product catalog and account-configuration endpoints, which keeps the surface tight for integrations that only need to read and write the pipeline itself. ## For AI agents Read and write organizations, people, deals, tasks, and users in the Agendor Brazilian CRM via a focused 21-endpoint surface. ## Scope Does not handle product catalog management, account configuration, marketing campaigns, or invoicing - use for core Brazilian CRM pipeline operations on organizations, people, deals, and tasks only. ## Capabilities - List, retrieve, and update organizations identified by CNPJ - Manage people records with CPF and Brazilian address fields - Read and update deals across the sales pipeline - Create, list, and complete tasks for sales reps - Look up Agendor users to assign records and tasks - Filter deals by owner and date range for forecasting ## Use cases ### Sales Pipeline Sync External sales tools pull Agendor pipeline data via GET /deals on a schedule and push status changes back to keep the CRM authoritative. The 21-endpoint surface is ideal for this - it gives full read/write to organizations, people, deals, and tasks without exposing endpoints the integration does not need. Example prompt: List all deals via GET /deals modified in the last 24 hours and push the diff into the analytics warehouse ### WhatsApp Sales Assistant Brazilian sales teams that operate inside WhatsApp build assistants that read deal and contact context from Agendor before responding to a prospect. The assistant resolves a phone number to a person via /people, looks up the linked organization by CNPJ via /organizations, and returns deal status from /deals - all without leaving WhatsApp. Example prompt: Given a prospect's phone number, find the matching person via GET /people, fetch their organization, and return the most recent open deal status ### Task Reminder Bot Reminder bots use the tasks endpoints to read overdue tasks and ping reps on Slack or WhatsApp. Each morning the bot pulls GET /tasks filtered by owner and due date, then sends individual reminders so the rep does not need to log into Agendor to triage their day. Example prompt: Each morning, list overdue tasks per owner via GET /tasks and send a Slack DM to each rep listing the tasks past due ### AI Agent CRM Operations Through Jentic, an agent can read and update Agendor pipeline objects without holding the customer's API token. Jentic injects the Authorization header at execution time and the agent works with the structured response - ideal for embedded copilots in Brazilian sales tools. Example prompt: Search Jentic for 'find organization by cnpj agendor', load the GET /organizations schema, and execute with the CNPJ filter ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /organizations | List organizations | | GET | /organizations/{id} | Retrieve a specific organization | | GET | /people | List people | | GET | /people/{id} | Retrieve a specific person | | GET | /deals | List deals | | GET | /deals/{id} | Retrieve a specific deal | | GET | /tasks | List tasks | ## Key resources - **Organizations** — Company records keyed on CNPJ - **People** — Contact records keyed on CPF - **Deals** — Sales pipeline opportunities - **Tasks** — Follow-up tasks for sales reps - **Users** — Agendor user records ## Why Jentic - **Setup:** Wiring the Agendor API by hand means managing its token in the Authorization header and coding calls across organizations, people, deals, and tasks. 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 resource id in the URL path for reads (/deals/{id}, /people/{id}), and every operation on this surface is a read, so a rule can pin the agent to reading a specific record. You choose which read 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', and Jentic returns the matching Agendor operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Agendor API** — Broader 30-endpoint Agendor spec including products and configuration. - **Pipedrive API** — Global pipeline CRM with similar deal-stage primitives. - **HubSpot Account Info API** — Broader CRM and marketing platform. - **Stripe API** — Payments platform used to charge customers once deals 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 in the Authorization header. Through Jentic, the token is stored encrypted in the vault and injected per call so the agent never holds it directly. ### Can I find an organization by CNPJ with this API? Yes. GET /organizations supports filtering, and GET /organizations/{id} returns the full record. CNPJ is one of the natural identifiers Agendor uses for Brazilian companies. ### What are the rate limits for the Agendor API? The public spec does not include explicit limits. Agendor throttles per account in practice - keep sync jobs to a few requests per second and back off on HTTP 429. ### How do I list deals through Jentic? Search Jentic for 'list agendor deals', load the GET /deals schema, and execute with whatever filters (owner, status) the agent needs. Jentic returns the deal list directly to the agent. ### How does this differ from the other Agendor spec on Jentic? This spec is the focused 21-endpoint pipeline surface. The 'agendor' spec is the broader 30-endpoint version that also covers products and account configuration. Use this one for tight integrations that only need pipeline objects. ### 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 you pick exactly which read operations sit in the allowed set. Every operation on this surface is a read, and the resource id lives in the URL path for calls like GET /deals/{id} and GET /people/{id}, so a rule can pin the agent to reading a specific record such as one deal or one person. Anything you leave out of the allowed set, whether that is listing organizations, reading tasks, or looking up users, is not reachable by the agent.