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

# Gestorasmart CRM Smart API

The CRM Smart API runs the sales back office for a telecom reseller, centred on client records and the contracts, orders, and stock that hang off them. Clients can be created, updated, and imported in bulk, contracts move through status changes, and orders are placed and then fulfilled by linking SIM cards and IMEIs from inventory. It also tracks sellers and their referrers, client addresses, and product and device stock, with per-referrer listings of the clients, contracts, and orders tied to each.

## For AI agents

Manage clients, contracts, and orders in the CRM Smart sales system, and link SIM cards and IMEIs from stock to an order. Authenticates with a JWT held in a cookie.

## Scope

Does not process payments, run marketing campaigns, or provision telecom network service. Use for managing clients, contracts, orders, and device stock in CRM Smart only.

## Capabilities

- Create and update client records and import clients in bulk
- Open contracts for a client and move them through status changes
- Place orders and link SIM cards and IMEIs from stock to an order
- Track SIM card and IMEI stock by operator and by model
- Register sellers and the referrers that bring in clients
- Record client addresses and contract representatives

## Use cases

### Agent-Managed Sales Intake

An AI agent connected through Jentic creates a client, opens a contract for them, and places the first order in one flow, so a new sale is captured without a back-office operator keying it in. Because the agent works against the same client, contract, and order records the CRM Smart app uses, the sale is visible to the team at once.

Example prompt: Create a client, open a contract for them, and place an order, returning the new order id

### Order Fulfilment with SIM and IMEI Stock

A fulfilment workflow places an order and then links the SIM cards and IMEIs it needs from inventory, drawing on the stock-by-operator and stock-by-model counts to pick available devices. This keeps the order and the devices assigned to it in one system rather than a separate inventory tool.

Example prompt: Place an order, then link the required SIM cards and IMEIs from stock to that order

### Bulk Client Import

A migration or onboarding job imports a batch of clients in one call rather than creating them one at a time, so moving an existing book of business into CRM Smart is a single step. The imported clients then carry the contracts and orders created against them.

Example prompt: Import this batch of client records in a single bulk call and report how many were created

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/cliente` | List clients |
| POST | `/cliente` | Create a client |
| POST | `/cliente/importar-massa` | Import clients in bulk |
| GET | `/contratos/list` | List contracts |
| POST | `/contratos` | Create a contract |
| POST | `/pedidos` | Create an order |
| POST | `/simcards/vincular-simcards-pedido/{pedidoId}` | Link SIM cards to an order |
| GET | `/produtos` | List products |

## Key resources

- **Clients** — Client records with single and bulk creation, updates, and per-referrer listing
- **Contracts** — Contracts opened for a client and moved through status and detail changes
- **Orders** — Sales orders placed, tracked, and fulfilled with linked devices
- **Stock** — Products, SIM cards, and IMEIs tracked by operator and by model
- **Sellers** — Sellers and the referrers that bring in clients and contracts

## 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:** 43 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 58 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 21 / 100
  - Agent Usability: 87 / 100
  - Security: 50 / 100
  - AI Discoverability: 68 / 100
- **View full report:** https://jentic.com/apis/gestorasmart.com.br/gestorasmart/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 CRM Smart API by hand means logging in to obtain a JSON Web Token, carrying it in a cookie on each call, and sequencing clients, contracts, orders, and device stock yourself. Through Jentic you install once, import CRM Smart from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** You choose which operations your agent may call, so you can allow listing and creating clients, contracts, and orders while leaving stock edits and deletions out. The record ids travel in the URL path or body, so your rules bound which operations run, and destructive ones like deleting a client or a contract are not included unless you add them.
- **Credential handling:** Your CRM Smart token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a client and open a contract' or 'link SIM cards to an order', and Jentic returns the matching CRM Smart operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Copper API** — CRM for managing contacts, pipeline, and customer records
- **Keap API** — Small-business CRM with contacts, orders, and invoicing in one platform
- **Stripe API** — Payment processing for charging a customer behind an order

## FAQ

### Is there a CRM Smart MCP server?

You don't need an MCP server to give your agent the CRM Smart API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent can create clients, open contracts, and place orders straight away, with no extra server to run and no tool definitions to load into the agent's context.

### Can I limit what my agent is allowed to do with the CRM Smart API?

Yes. Write a rule that allows only the operations the agent needs, such as listing and creating clients and orders, so it can handle sales intake without deleting contracts or editing stock. Destructive operations like deleting a client or a contract are not included unless you add them, and every call the agent makes is logged.

### What authentication does the CRM Smart API use?

The CRM Smart API authenticates with a JSON Web Token held in an httpOnly cookie named `token`, which you obtain by logging in, per its OpenAPI spec. Through Jentic the token is stored encrypted by your own instance and injected at call time, so it never appears in the agent's prompt or logs.

### Can I import clients in bulk with the CRM Smart API?

Yes. There is a bulk client import operation that creates a batch of clients in a single call, which is how you migrate an existing customer list rather than creating each client one at a time. The imported clients then carry the contracts and orders you create against them.

### Can I link SIM cards and IMEIs to an order with the CRM Smart API?

Yes. After placing an order you call the operations that link SIM cards and IMEIs from stock to that order, and you can look up stock quantities by operator and by model to pick available devices. This keeps the order and its assigned devices in one system.

### How do I capture a sale through Jentic?

Import the CRM Smart API from the Jentic API Directory, then have your agent issue a request such as 'create a client, open a contract, and place an order'. Jentic matches the intent to the create-client, create-contract, and create-order operations and returns their input schema so the agent fills the right fields, with your stored token injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.