canonical: https://jentic.com/apis/partnerpro.com.br/partnerpro

# PartnerPRO API

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.

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

## Scope

Does not handle payment processing, email campaigns, or document signing. Use for client, opportunity, and sales pipeline management only.

## Capabilities

- 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

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

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

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

Example prompt: Call POST `/api/financeiro/conta-receber` to record an accounts-receivable entry

## Key endpoints

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

## Key resources

- **Clients and Partners** — Clients, partners, and affiliates with lookups by ID and CNPJ
- **Opportunities** — Sales opportunities, pipeline stages, comments, and attachments
- **Finance** — Accounts-receivable entries and their status
- **Products** — Products, categories, and brands
- **Configuration** — Users and sales funnels

## AI readiness

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.

- **Score:** 58 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 66 / 100
  - Developer Experience & Jentic Compatibility: 64 / 100
  - AI-Readiness & Agent Experience: 36 / 100
  - Agent Usability: 93 / 100
  - Security: 85 / 100
  - AI Discoverability: 60 / 100
- **View full report:** https://jentic.com/apis/partnerpro.com.br/partnerpro/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Pipedrive** — Sales CRM built around a visual deal pipeline
- **HubSpot Deals** — Deal and pipeline management within the HubSpot CRM
- **Salesloft** — Sales engagement and outreach cadences

## FAQ

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