Agendor API

Name: Agendor API API
Brand: Agendor API
Availability: InStock

★ Only Publicly Available SpecCRMDeal PipelineapiKey21 EndpointsREST

For Agents

Read and write organizations, people, deals, tasks, and users in the Agendor Brazilian CRM via a focused 21-endpoint surface.

Quickstart

Get started with Agendor API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list agendor deals in the pipeline"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Agendor API API.

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

GET STARTED

Start building with Agendor API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Agendor API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Agendor API API for, with concrete tasks.

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

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.

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.

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.

Search Jentic for 'find organization by cnpj agendor', load the GET /organizations schema, and execute with the CNPJ filter

Key Endpoints

21 endpoints — jentic publishes the only available openapi specification for agendor api, keeping it validated and agent-ready.

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

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}

Why though 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. The agent never sees the raw token, which is essential because that token has full pipeline read/write.

Intent-based discovery

Agents search Jentic by intent (e.g., 'list agendor deals') and Jentic returns the matching Agendor operation with its parameter schema, so the agent picks the right endpoint without reading docs.

Time to first call

Direct integration: about 1 day for auth and the core pipeline objects. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Agendor API

Broader 30-endpoint Agendor spec including products and configuration.

Use the broader spec when you also need product catalog and configuration access. Use this one when you only need core pipeline objects.

Alternative

Pipedrive API

Global pipeline CRM with similar deal-stage primitives.

Pick Pipedrive for global teams without Brazilian-specific data needs. Agendor is locally idiomatic for Brazil.

Alternative

HubSpot Account Info API

Broader CRM and marketing platform.

Pick HubSpot when the team also needs marketing automation alongside CRM.

Complementary

Stripe API

Payments platform used to charge customers once deals close.

Pair to charge a Stripe customer when an Agendor deal moves to 'Ganha'.

FAQs

Specific to using Agendor API 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 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.