CRM · Beta

Clazar
API integration

Ship CRM features without building the integration. Full Clazar API access via Proxy and 20+ MCP-ready tools for AI agents — extend models and mappings to fit your product.

Built for specific customer use cases. Issues are resolved quickly.

Talk to us

Use Cases

Why integrate with Clazar

Common scenarios for SaaS companies building Clazar integrations for their customers.

Sync Marketplace Deals with Your CRM

Let your users mirror Clazar Opportunities, Private Offers, and Buyers into your CRM so cloud co-sell pipeline stays aligned with their core sales workflow. Push stage updates back to Clazar to keep AWS, Azure, and GCP partner portals in sync.

Automate Usage-Based Marketplace Billing

If you're a billing or metering platform, let customers report consumption directly against Clazar Contracts so buyers get invoiced accurately on their AWS, Azure, or GCP bill — no manual CSV uploads required.

Trigger Entitlements from Marketplace Contracts

PLG and customer success platforms can listen for activated Clazar Contracts to provision licenses, enable features, or spin up environments the moment a buyer transacts on a cloud marketplace.

Calculate Commissions on Cloud Revenue

Sales compensation tools can pull Contracts, Reseller Offers, and normalized Analytics datasets from Clazar to accurately compute net marketplace revenue and rep payouts across clouds.

Power Co-Sell Workflows in Partner Platforms

PRMs and partner ecosystem tools can read and write Clazar Opportunities and Buyers so channel managers manage the entire co-sell motion in one place instead of swivel-chairing between portals.

What You Can Build

Ship these features with Truto + Clazar

Concrete product features your team can ship faster by leveraging Truto’s Clazar integration instead of building from scratch.

Two-Way Opportunity Sync

Mirror Clazar Opportunities into your app and push stage, status, and cloud updates back using the opportunities update endpoint.

Private Offer Status Monitoring

Poll private offers to detect acceptance events and trigger downstream workflows like contract creation, provisioning, or CRM stage changes.

Contract Activation Automation

Fetch pending Contracts, verify provisioning on your side, then call the Clazar contract activation endpoint to move them into an active state.

Bulk Usage Metering Pipeline

Submit arrays of metering events against a contract_id and dimension on an hourly or billing-cycle cadence so marketplace buyers are charged for actual consumption.

External ID Mapping Layer

Use external_object_associations on Contracts, Opportunities, and Private Offers to permanently link your internal record IDs (e.g., Salesforce Opportunity ID) to Clazar objects.

Marketplace Revenue Analytics

Pull normalized datasets like aws_marketplace_revenue, aws_cosell_opportunities, or gcp_marketplace_monthly_insights to power dashboards without parsing raw contracts.

SuperAI

Clazar AI agent tools

Comprehensive AI agent toolset with fine-grained control. Integrates with MCP clients like Cursor and Claude, or frameworks like LangChain.

create_a_clazar_authenticate

Create an access token in Clazar by exchanging client credentials. Returns the access_token used as the Bearer credential for subsequent Clazar API requests. Requires client_id and client_secret.

list_all_clazar_analytics_datasets

List records from a Clazar analytics dataset. Returns a paginated collection of dataset rows in results; the row fields are specific to the dataset selected. Required: dataset_name (e.g. aws_cosell_opportunities, aws_marketplace_revenue, gcp_marketplace_monthly_insights). Supports ordering and search; page and page_size are handled automatically.

get_single_clazar_buyer_by_id

Get a Clazar buyer by id. Returns the buyer record including id, cloud, cloud_identifiers, status, and custom_properties. Required: id.

list_all_clazar_buyers

List Clazar buyers for your cloud marketplace agreements. Returns buyer records including id, cloud, cloud_identifiers, status, and custom_properties.

update_a_clazar_buyer_by_id

Update a Clazar buyer by id (partial update) — set the buyer's custom_properties or external_object_associations. Returns the updated buyer record including id, custom_properties, and external_object_associations. Required: id.

create_a_clazar_contact

Create a contact in Clazar. Returns the created contact record including its uuid, email, full_name, and phone_number.

delete_a_clazar_contact_by_id

Delete a contact in Clazar by id (contact UUID). Returns an empty 204 response on success. Required: id.

get_single_clazar_contact_by_id

Get a single contact in Clazar by id (contact UUID). Returns the contact record including its uuid, email, full_name, and phone_number. Required: id.

list_all_clazar_contacts

List contacts in Clazar. Returns: uuid, email, full_name, phone_number.

update_a_clazar_contact_by_id

Partially update a contact in Clazar by id (contact UUID). Returns the updated contact record including its uuid, email, full_name, and phone_number. Required: id.

clazar_contracts_activate

Activate a contract in Clazar by its id. Returns an empty response body on success. Required: contract_id.

get_single_clazar_contract_by_id

Get a single Clazar contract by id. Returns the contract record including id, cloud, cloud_id, status, buyer_id, listing_id, accepted_at, start_at, end_at, and custom_properties. Required: id.

list_all_clazar_contracts

List Clazar marketplace contracts with filters for cloud (aws, azure, gcp), status (active, inactive, pending), buyer_id, listing_id, date ranges, and cloud-specific identifiers. Returns contract records including id, cloud, cloud_id, status, accepted_at, start_at, and end_at.

update_a_clazar_contract_by_id

Update a Clazar contract by id, setting custom_properties (custom property API names and values in key-value format) and external_object_associations (Salesforce, Hubspot, Orb, etc.). Returns the updated contract record including id, cloud, cloud_id, status, and custom_properties. Required: id.

get_single_clazar_listing_by_id

Get a single Clazar marketplace listing by id. Returns the listing record including its id, cloud, cloud_id, status, and last_modified_at. Required: id.

list_all_clazar_listings

List Clazar marketplace listings. Returns each listing with id, cloud, cloud_id, status, and last_modified_at. Filter by cloud, cloud_id, status, or last_modified_at_before/after; use ordering to sort results.

create_a_clazar_metering

Create metering records in Clazar in bulk. Returns the created metering record including its id, cloud, contract_id, dimension, and status. Required: request (array of metering record objects).

get_single_clazar_metering_by_id

Get a single Clazar metering record by id. Returns: id, cloud, contract_id, dimension, status, custom_properties, created_at, updated_at. Required: id.

list_all_clazar_metering

List Clazar metering records. Returns: id, cloud, contract_id, dimension, status, custom_properties, created_at, updated_at. Filter by cloud, contract_id, dimension, or status; sort with ordering.

update_a_clazar_metering_by_id

Update a Clazar metering record by id. Returns the updated record including its id, cloud, contract_id, dimension, and custom_properties. Required: id.

get_single_clazar_opportunity_by_id

Get a single Clazar opportunity by its UUID id. Returns: id, cloud, cloud_id, stage, status, accept_by, target_close_date, created_at, last_modified_at, metadata. Required: id.

list_all_clazar_opportunities

List Clazar opportunities, filterable by cloud, cloud_id, stage, status, and created/last-modified/target-close/accept-by date ranges. Returns: id, cloud, cloud_id, stage, status, accept_by, target_close_date, created_at, last_modified_at, metadata.

update_a_clazar_opportunity_by_id

Update a Clazar opportunity by id, e.g. its custom_properties or external_object_associations with external systems like Salesforce, Hubspot, or Orb. Returns: id, cloud, cloud_id, stage, status, accept_by, target_close_date, created_at, last_modified_at, metadata. Required: id.

get_single_clazar_private_offer_by_id

Get a Clazar Private Offer by id. Returns the Private Offer record including id, cloud, cloud_id, status, accepted_at, and expiration_at. Required: id (UUID of the Private Offer).

list_all_clazar_private_offers

List Clazar Private Offers, filterable by cloud, cloud_id, status, and accepted_at/published_at/expiration_at date ranges. Returns Private Offer records including id, cloud, cloud_id, status, and accepted_at.

update_a_clazar_private_offer_by_id

Update a Clazar Private Offer by id, setting its custom properties and associations with external systems (Salesforce, Hubspot, Orb, etc.). Returns the updated Private Offer record including id, cloud, cloud_id, status, and accepted_at. Required: id.

get_single_clazar_reseller_offer_by_id

Get a single Clazar reseller offer by id. Returns the reseller offer including its id, cloud, cloud_id, status, custom_properties, and external_object_associations. Required: id.

list_all_clazar_reseller_offers

List Clazar reseller offers, filterable by accepted, published, and expiration date ranges, cloud, cloud_id, and status. Returns reseller offer records including id, cloud, cloud_id, status, and custom_properties.

update_a_clazar_reseller_offer_by_id

Update a Clazar reseller offer by id, setting its custom_properties and/or external_object_associations. Returns the updated reseller offer including id, cloud, cloud_id, status, and custom_properties. Required: id.

Why Truto

Why use Truto’s MCP server for Clazar

Other MCP servers give you a static tool list for one app. Truto gives you a managed, multi-tenant MCP infrastructure across 800+ integrations.

Auto-generated, always up to date

Tools are dynamically generated from curated documentation — not hand-coded. As integrations evolve, tools stay current without manual maintenance.

Fine-grained access control

Scope each MCP server to read-only, write-only, specific methods, or tagged tool groups. Expose only what your AI agent needs — nothing more.

Multi-tenant by design

Each MCP server is scoped to a single connected account with its own credentials. The URL itself is the auth token — no shared secrets, no credential leaking across tenants.

Works with every MCP client

Standard JSON-RPC 2.0 protocol. Paste the URL into Claude, ChatGPT, Cursor, or any MCP-compatible agent framework — tools are discovered automatically.

Built-in auth, rate limits, and error handling

Tool calls execute through Truto’s proxy layer with automatic OAuth refresh, rate-limit handling, and normalized error responses. No raw API plumbing in your agent.

Expiring and auditable servers

Create time-limited MCP servers for contractors or automated workflows. Optional dual-auth requires both the URL and a Truto API token for high-security environments.

How It Works

From zero to integrated

Go live with Clazar in under an hour. No boilerplate, no maintenance burden.

Link your customer’s Clazar account

Use Truto’s frontend SDK to connect your customer’s Clazar account. We handle all OAuth and API key flows — you don’t need to create the OAuth app.

We handle authentication

Don’t spend time refreshing access tokens or figuring out secure storage. We handle it and inject credentials into every API request.

Call our API, we call Clazar

Truto’s Proxy API is a 1-to-1 mapping of the Clazar API. You call us, we call Clazar, and pass the response back in the same cycle.

Unified response format

Every response follows a single format across all integrations. We translate Clazar’s pagination into unified cursor-based pagination. Data is always in the result attribute.

FAQs

Common questions about Clazar on Truto

Authentication, rate limits, data freshness, and everything else you need to know before you integrate.

How do end users authenticate their Clazar account?

Users connect via Clazar's authentication flow, which Truto handles through the authenticate endpoint. You don't need to manage credential storage, token refresh, or auth edge cases — Truto brokers the connection and exposes a consistent interface for all downstream API calls.

Can we map our internal record IDs to Clazar objects?

Yes. Clazar natively supports external_object_associations on Contracts, Opportunities, and Private Offers via their respective update endpoints. This lets you permanently link your internal IDs (e.g., Salesforce Opportunity ID, subscription IDs) to Clazar records without maintaining a separate mapping table.

What CRM-style objects are available through this integration?

Buyers, Contacts, Opportunities, Private Offers, Reseller Offers, Contracts, Listings, Metering, and Analytics datasets are all accessible. Most support list, get, and update operations; Contacts and Metering additionally support create, and Contacts support delete.

How do we report usage data for consumption-based pricing?

Use the create metering endpoint to submit usage events tied to a specific contract_id and dimension. The endpoint accepts bulk payloads, so you can batch events on an hourly or billing-cycle cadence rather than firing one request per event.

How fresh is data pulled from Clazar?

Data is fetched on-demand from Clazar's live API, so reads reflect current state. For event-driven workflows like detecting accepted Private Offers or activated Contracts, you can poll the list endpoints with filters and use Truto's scheduling to normalize data freshness across tenants.

Can we filter the co-sell pipeline by cloud or stage?

Yes. The list opportunities endpoint supports filtering by cloud (AWS, Azure, GCP), stage, and status, so you can scope syncs to specific pipelines or build cloud-specific views inside your product.

Clazar

Get Clazar integrated into your app

Our team understands what it takes to make a Clazar integration successful. A short, crisp 30 minute call with folks who understand the problem.