canonical: https://jentic.com/apis/claro.com.br/claro # Claro CPQ Quotes API The Claro CPQ Quotes API retrieves and updates sales quotes tied to a customer or an opportunity inside Claro Brazil's Configure, Price, Quote system. It lists every quote linked to a client or opportunity, returns a single previously created quote, partially updates a quote while its status still allows changes, and advances a quote through its lifecycle status. The operations proxy Claro's CPQ backend through its Apigee gateway, so agents work against a stable quote contract rather than the underlying provisioning system. It is aimed at sales and commercial workflows that need programmatic access to telecom quotes. ## For AI agents Retrieve and update Configure-Price-Quote sales quotes in Claro Brazil's CPQ system: list quotes for a customer or opportunity, fetch a single quote, patch a quote in progress, and change a quote's status. ## Scope Does not handle order fulfillment, billing, or payment collection. Use for retrieving and updating CPQ sales quotes only. ## Capabilities - Retrieve all quotes linked to a specific customer or sales opportunity - Fetch a single previously created quote that was offered to a customer - Partially update a quote while its status still permits modification - Advance a quote through its lifecycle by changing its status - Work against a stable CPQ quote contract proxied through Claro's Apigee gateway ## Use cases ### Agent-assisted quote lookup and update An AI agent handling a sales enquiry can call the Claro CPQ Quotes API through Jentic to pull every quote attached to a customer, retrieve the specific quote under discussion, and patch it when the customer requests a change. Jentic returns the right operation from a natural-language query, so the agent works against the CPQ quote contract without parsing the Apigee proxy documentation. Example prompt: Retrieve all quotes for the given customer, select the one matching the opportunity, and patch its editable fields with the customer's requested change. ### Quote status progression Advance a telecom sales quote through its lifecycle by changing its status from initial to feasibility pending to feasibility concluded as the deal moves forward. The status operation enforces which transitions are allowed, so a workflow tool can drive the quote forward without manually editing backend records. Example prompt: Change the status of the named quote from its initial state to feasibility pending, then confirm the transition was accepted. ### Opportunity-to-quote reconciliation List every quote linked to a sales opportunity to reconcile what has been offered against what is in the pipeline. The retrieve operation returns the detail of any single quote, so a commercial team can audit outstanding offers tied to one opportunity in a single pass. Example prompt: List the quotes for the given opportunity, then retrieve the detail of each one and report which quotes are still editable. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/cpq/quotes` | Retrieve all quotes for a customer or opportunity | | PATCH | `/cpq/quotes` | Partially update a previously created quote | | GET | `/cpq/quotes/retrieve` | Retrieve a single previously created quote | | PATCH | `/cpq/quotes/states` | Change the status of a quote | ## Key resources - **Quotes** — List, retrieve, update, and re-status CPQ sales quotes for a customer or opportunity ## 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:** 60 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 63 / 100 - Developer Experience & Jentic Compatibility: 76 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 94 / 100 - Security: 51 / 100 - AI Discoverability: 59 / 100 - **View full report:** https://jentic.com/apis/claro.com.br/claro/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 ``` ## Why Jentic - **Setup:** Wiring the Claro CPQ Quotes API by hand means picking among its basic, bearer, apiKey, and OAuth2 schemes, targeting the right Apigee host for your environment, and coding each quote call yourself. Through Jentic you install once, import the API from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** The quote identifier travels in the request body and query, not as an id in the URL path, so bound your agent to the operations it needs, such as listing and retrieving quotes. You choose which operations it may call, so the update and status operations are not included unless you add them. - **Credential handling:** Your Claro credential 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 'retrieve a sales quote' or 'change a quote status', and Jentic returns the matching Claro CPQ operation with its input schema so the agent calls the right endpoint without reading the proxy docs. ## Related APIs - **HubSpot Quotes** — CRM-native quotes object for creating and sending sales quotes - **Pipedrive API** — Sales CRM with deals, pipelines, and quote-adjacent workflows - **Deals** — CRM deals object that tracks the opportunity behind a quote ## FAQ ### Is there a Claro CPQ Quotes API MCP server? You do not need an MCP server to give your agent the Claro CPQ Quotes API. Jentic connects it directly from the API Directory: import the API, store your credential once, and your agent calls the quote retrieve, update, and status operations. Operations are discovered on demand, so no extra server definitions load into the agent's context. ### What authentication does the Claro CPQ Quotes API use? The API accepts several schemes per its OpenAPI spec: HTTP basic, a bearer token, an apiKey sent in the X-API-Key header, and OAuth2 client credentials. Through Jentic the credential you choose is stored encrypted in your own Jentic One instance and supplied only when an allowed call runs, so it never reaches the agent's context. ### Can I update a quote that has already been created with the Claro CPQ Quotes API? Yes, as long as the quote's status still permits changes, such as initial or feasibility pending. The update operation partially modifies the quote, and a separate status operation advances it once feasibility is concluded. ### What are the rate limits for the Claro CPQ Quotes API? The OpenAPI spec does not specify rate limits. Because the operations are proxied through Claro's Apigee gateway, limits are set per credential on the gateway, so confirm the quota that applies to your keys in the Claro developer documentation at https://developers.claro.com.br. ### Can I limit what my agent is allowed to do with the Claro CPQ Quotes API? Yes. Write a rule that permits only the read operations, listing and retrieving quotes, when the agent should report on the pipeline, and add the update and status operations only for workflows that must change a quote, with every call logged. ### How do I retrieve a customer's quotes with the Claro CPQ Quotes API through Jentic? Search Jentic for 'retrieve a sales quote' to surface the quote operations, load the input schema, pass the customer or opportunity identifier, and execute. To run it on your own infrastructure, install Jentic One from its GitHub repo.