canonical: https://jentic.com/apis/agendor.com.br/agendor-main

# Agendor API

Jentic publishes a curated, agent-optimized OpenAPI 3 specification for Agendor API, converted from the Swagger 2.0 document Agendor publishes for its v3 API and kept 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.

## For AI agents

Manage Brazilian-Portuguese sales pipelines: create and update people, organizations, and deals; log tasks and activities; advance deals through funnel stages.

## Scope

Does not handle invoicing, payment collection, marketing automation, or customer support tickets - use for sales pipeline and contact management only.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **People** — Create, list, update, delete, and upsert individual contacts and their associated tasks and deals
- **Organizations** — Manage company records with nested endpoints for related people, deals, and tasks
- **Deals** — Track sales opportunities through pipeline stages with value, products, and custom fields
- **Tasks** — Schedule and complete activities linked to people, organizations, or deals
- **Products** — Reference catalog used to build deal line items and pipeline value

## Why Jentic

- **Setup:** Wiring the Agendor API by hand means managing its Token header and coding your own create and update logic across deals, people, and tasks in the sales pipeline. 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 updates (/deals/{id}) and the person id for tasks (/people/{person_id}/tasks), so a rule can pin the agent to a specific deal or person. You choose which operations it may call, such as reading deals, so create and update operations are not included unless you add them.
- **Credential handling:** Your Agendor API token is stored once, encrypted, by your own Jentic One instance and injected as the Token header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a deal in the Brazilian CRM', and Jentic returns the matching Agendor operation with its JSON schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Pipedrive API** — Sales-focused CRM with similar deal-stage modelling and a richer activity API
- **HubSpot CRM Contacts** — Free-tier CRM with broader marketing and service modules beyond pipeline management
- **Stripe API** — Payment processing that pairs with deal-won events to charge the customer

## FAQ

### Which OpenAPI specification does this Agendor API page describe?

A curated, agent-optimized Jentic specification covering 58 Agendor operations across 43 paths. Agendor also publishes its own Swagger 2.0 document for the v3 API at `https://api.agendor.com.br/v3/swagger.json`, which covers the same 43 paths and 58 operations. The Jentic variant is an OpenAPI 3.0.3 conversion of that document, validated and kept agent-ready so agents can load operation schemas and execute calls directly. Get started with Jentic One, the self-hosted execution layer.

### 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.

### 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 the agent may call and which credential it uses, so you can grant read-only access to GET /deals while withholding the create and update operations. Since Agendor puts the deal id in the URL path for updates (/deals/{id}) and the person id for tasks (/people/{person_id}/tasks), a rule can also pin the agent to a specific deal or person. Nothing outside the operations you explicitly allow is available to the agent.