PartnerPRO API
58
AI ReadinessFoundational (C+)58/100
Community OpenAPI document · agent-readyCRMDeal Pipelineoauth254 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage clients, partners, and sales opportunities through a pipeline, attach comments and files, record receivables, and maintain a product list. Authenticates with OAuth2 client credentials.
Use for: Create a new client record, List all sales opportunities, Move an opportunity to the next pipeline stage, Add a comment to an opportunity
Not supported: Does not handle payment processing, email campaigns, or document signing. Use for client, opportunity, and sales pipeline management only.
The PartnerPRO API runs a partner-sales CRM, managing clients, partners, affiliates, and the opportunities that move through a sales pipeline. It creates and updates clients and opportunities, advances an opportunity's pipeline stage, and attaches comments and files to it, while partner and affiliate operations link each deal to the account that owns it. Finance operations record accounts-receivable entries, and a product list with categories and brands backs the deals being sold.
Install Jentic One Beta
Connect the PartnerPRO API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PartnerPRO API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpartnerpro.com.br%2Fpartnerpro" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpartnerpro.com.br%2Fpartnerpro" | 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.
Capabilities
What an agent can do with PartnerPRO API.
Create and update clients and their contact records
Track sales opportunities and advance them through pipeline stages
Attach comments and file attachments to opportunities
Manage partners and affiliates linked to each opportunity
Record accounts-receivable entries and update their status
Maintain a product list with categories and brands
Use Cases
Patterns agents use PartnerPRO API for, with concrete tasks.
★ AI Agent Sales Operations
An AI agent supporting a sales team can create clients, open opportunities, and advance them through the pipeline through Jentic. The agent searches for each operation, supplies the client and opportunity details, and runs the call, without the developer handling the OAuth2 client-credentials flow or reading the PartnerPRO reference docs.
Call POST /api/cliente/oportunidade to create an opportunity, then PATCH /api/cliente/pipeline-oportunidade to advance its stage
Pipeline Management
Sales managers keep deals moving and attach context as they progress. PartnerPRO creates and updates opportunities, records comments and file attachments against them, and updates the pipeline stage, so an agent can log an update and move a deal forward in one flow.
Call POST /api/cliente/oportunidade/comentario to add a comment to an opportunity
Receivables and Products
Back-office teams track what customers owe and keep the product list current. PartnerPRO records accounts-receivable entries and updates their status, and manages products, categories, and brands, so an agent can raise a receivable against a closed deal and keep the product list in sync.
Call POST /api/financeiro/conta-receber to record an accounts-receivable entry
Key Endpoints
54 endpoints — the partnerpro api runs a partner-sales crm, managing clients, partners, affiliates, and the opportunities that move through a sales pipeline.
METHOD
PATH
DESCRIPTION
POST
/api/cliente
Create a client
GET
/api/cliente
List clients
POST
/api/cliente/oportunidade
Create an opportunity
PUT
/api/cliente/oportunidade
Update an opportunity
PATCH
/api/cliente/pipeline-oportunidade
Advance an opportunity's pipeline stage
GET
/api/produtos
List products
POST
/api/financeiro/conta-receber
Create an accounts-receivable entry
GET
/api/parceiro
List partners
POST
/api/cliente
Create a client
GET
/api/cliente
List clients
POST
/api/cliente/oportunidade
Create an opportunity
PUT
/api/cliente/oportunidade
Update an opportunity
PATCH
/api/cliente/pipeline-oportunidade
Advance an opportunity's pipeline stage
GET
/api/produtos
List products
POST
/api/financeiro/conta-receber
Create an accounts-receivable entry
GET
/api/parceiro
List partners
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
PartnerPRO API
- Foundational (C+)58/100
66
Foundational Compliance64
Developer Experience & Jentic Compatibility36
AI-Readiness & Agent Experience93
Agent Usability85
Security60
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
66
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
89%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
99%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
64
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
6%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
50%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
36
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
83%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
61%
Summary Coverage
Coverage of summaries across operations/tags/info.
93
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
93%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
85
Security
Trust, risk posture, and security compliance.
Grade: ASignals: 1
85%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
60
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
60%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PartnerPRO API by hand means running the OAuth2 client-credentials exchange, refreshing the bearer token, and mapping its Portuguese resource names yourself. Through Jentic you install once, import PartnerPRO from the API Directory, store the client credentials once, and your agent calls it.
Permission scoping
You choose the exact PartnerPRO operations a rule allows, such as reading clients and opportunities, so write operations like creating a client or an accounts-receivable entry stay out of reach. The agent works within that set and touches nothing beyond it.
Credential isolation
Your PartnerPRO client credentials are stored once, encrypted, by your own Jentic One instance and the access token is injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a sales opportunity' or 'list clients', and Jentic returns the matching PartnerPRO operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PartnerPRO API through Jentic.
What authentication does the PartnerPRO API use?
The PartnerPRO API authenticates with OAuth2 using the client-credentials flow, exchanging your client ID and secret for a bearer token at the token endpoint, per its OpenAPI spec. Through Jentic the client credentials are stored encrypted by your own Jentic One instance and the token is obtained and injected at call time, so secrets never enter the agent's prompt or logs.
Can I advance a sales opportunity through the pipeline with the PartnerPRO API?
Yes. The opportunity operations create and update a deal, and the pipeline operation updates its stage, so an agent can move a deal forward. Comments and file attachments can be added to the opportunity through their own operations.
What are the rate limits for the PartnerPRO API?
The OpenAPI spec does not specify rate limits. Check the vendor documentation at https://api.partnerpro.com.br for the limits that apply to your account.
How do I manage sales opportunities with the PartnerPRO API through Jentic?
Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import PartnerPRO from the API Directory, and store your client credentials once. Your agent then searches for an intent such as 'create a sales opportunity', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Is there a PartnerPRO MCP server?
You do not need an MCP server to give your agent the PartnerPRO API. Jentic connects it directly from the API Directory: import the API, store your credentials once, and your agent calls the client, opportunity, and finance operations on demand, which keeps your agent's context free of an extra server's tool definitions.
Can I limit what my agent is allowed to do with the PartnerPRO API?
Yes. PartnerPRO has write operations like creating clients and opportunities, so you can allow your agent just the ones a task needs, such as listing opportunities and adding comments, while leaving out creating or updating financial records. Because you run Jentic One yourself, the agent works within the operation set you grant, and every call is logged.
GET STARTED