Agendor APIs
3 APIs109 Endpoints1 Category
Categories
API Catalog
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.
30 endpointsAgendor 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.
21 endpointsAgendor API
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.
Connect Your Agent
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.