Clazar is a cloud sales acceleration platform that helps software companies list, sell, and manage their products across the AWS, Microsoft Azure, and Google Cloud (GCP) marketplaces from a single interface. The Clazar API provides programmatic access to marketplace listings, buyers, contracts, private offers, co-sell opportunities, and analytics data, enabling automated workflows for offer management, co-sell synchronization, and revenue reporting.
Power end-to-end data operations for your Clazar API with Nexla. Our bi-directional Clazar connector is purpose-built for Clazar, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Clazar or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Clazar workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The Clazar connector authenticates using the OAuth2 client credentials flow (also known as the two-legged or server-to-server flow). In this flow, Nexla exchanges a Client ID and Client Secret for a short-lived access token, which is then used to authorize API requests. No interactive user sign-in is required, making this flow well suited for automated, machine-to-machine data integrations.
Before creating a credential, ensure that you have the following.
You must have an active Clazar account with permission to manage API credentials. API access is configured within your Clazar workspace, and the ability to generate API keys is typically reserved for administrators. For complete details about Clazar's API capabilities, refer to the Clazar developer documentation.
Open the Settings area of the application, and navigate to the API Keys (developer credentials) section.
Click the option to create a new API key or credential.
Provide a descriptive name for the credential (for example, "Nexla Integration") so that it can be easily identified later.
Generate the credential. Clazar will display a Client ID and a Client Secret for the new key.
Copy the Client Secret immediately and store it securely. For security reasons, Clazar does not display the secret again after the key is created. If the secret is lost, you must generate a new API key.
Record both the Client ID and Client Secret for use when creating the Nexla credential below.
API keys grant access to your marketplace data, listings, contracts, and offers. Treat the Client Secret like a password, restrict access to authorized team members, and rotate keys periodically in accordance with your organization's security policies.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter the Client ID generated in your Clazar account in the Client ID field. This is the unique public identifier assigned to your application and is used to identify Nexla to the Clazar API.
Enter the Client Secret generated in your Clazar account in the Client Secret field. This is the confidential password provided alongside the Client ID and is used together with it to obtain an access token.
The Client Secret is stored securely and is never displayed after the credential is saved. To update an expired or rotated secret, generate a new API key in Clazar and edit the credential with the new values.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Clazar connector tile, then select the credential that will be used to connect to the Clazar instance, and click Next; or, create a new Clazar credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Clazar endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below; click on an endpoint to see more information about it and how to configure your data source for this endpoint.
The Clazar API uses consistent conventions across its resources: list endpoints return paginated results under a $.results[*] array and accept page and page_size query parameters, which Nexla handles automatically; single-record endpoints retrieve one object by its ID; and analytics endpoints return marketplace reporting data under a $.data[*] array.
List Buyers
This endpoint returns a list of all buyers in your Clazar account. Use it to ingest the complete set of marketplace buyers for customer reporting, segmentation, or syncing buyer records into a data warehouse.
This endpoint automatically retrieves all buyers accessible to your account. No additional configuration is required beyond selecting this endpoint template.
Results are paginated, and Nexla automatically iterates through all pages until no additional data is returned.
Buyer records returned by this endpoint can be joined with contract and private offer data to build a complete view of each customer's marketplace activity.
List Listings
This endpoint returns a list of all marketplace listings across your connected AWS, Azure, and GCP marketplaces. Use it to track which products are published and to monitor listing status across clouds.
This endpoint automatically retrieves all listings accessible to your account. No additional configuration is required beyond selecting this endpoint template.
Results are paginated, and Nexla automatically iterates through all pages until no additional data is returned.
To retrieve the full detail of an individual listing, use the "Get Listing" endpoint with the listing's ID.
List Contracts
This endpoint returns a list of all buyer contracts. Use it to track active and historical agreements, monitor contract terms, and reconcile committed revenue across marketplaces.
This endpoint automatically retrieves all contracts accessible to your account. No additional configuration is required beyond selecting this endpoint template.
Results are paginated, and Nexla automatically iterates through all pages until no additional data is returned.
To retrieve the full detail of an individual contract, use the "Get Contract" endpoint with the contract's ID.
List Opportunities
This endpoint returns a list of all co-sell opportunities. Use it to monitor co-sell deals that are synced with the AWS, Azure, and GCP partner portals and to report on co-sell pipeline activity.
This endpoint automatically retrieves all opportunities accessible to your account. No additional configuration is required beyond selecting this endpoint template.
Results are paginated, and Nexla automatically iterates through all pages until no additional data is returned.
Opportunities can be created and updated through the Clazar destination connector, allowing you to manage co-sell deals programmatically from Nexla.
List Private Offers
This endpoint returns a list of all private offers. Use it to track private, renewal, and agreement-based offers extended to buyers across your connected marketplaces.
This endpoint automatically retrieves all private offers accessible to your account. No additional configuration is required beyond selecting this endpoint template.
Results are paginated, and Nexla automatically iterates through all pages until no additional data is returned.
To retrieve the full detail of an individual private offer, use the "Get Private Offer" endpoint with the offer's ID.
Get Listing
This endpoint retrieves a single marketplace listing by its ID. Use it when you need the complete detail of one specific listing rather than the summary returned by "List Listings".
Enter the listing identifier in the Listing ID field. You can find this ID by first using the "List Listings" endpoint to retrieve available listings and their corresponding IDs.
The endpoint returns the full record for the specified listing, including its marketplace, status, and configuration details.
The Listing ID is required for this endpoint. Ensure you have the correct ID before configuring the source.
Get Contract
This endpoint retrieves a single contract by its ID. Use it when you need the complete detail of one specific buyer contract.
Enter the contract identifier in the Contract ID field. You can find this ID by first using the "List Contracts" endpoint to retrieve available contracts and their corresponding IDs.
The endpoint returns the full record for the specified contract, including buyer, terms, and status information.
The Contract ID is required for this endpoint. Ensure you have the correct ID before configuring the source.
Get Private Offer
This endpoint retrieves a single private offer by its ID. Use it when you need the complete detail of one specific private offer.
Enter the private offer identifier in the Private Offer ID field. You can find this ID by first using the "List Private Offers" endpoint to retrieve available offers and their corresponding IDs.
The endpoint returns the full record for the specified private offer, including pricing, terms, and current status.
The Private Offer ID is required for this endpoint. Ensure you have the correct ID before configuring the source.
Get AWS Marketplace Orders Analytics
This endpoint returns AWS Marketplace orders analytics data. Use it to analyze order-level activity and bookings originating from the AWS Marketplace.
This endpoint automatically retrieves the AWS Marketplace orders dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Analytics datasets are well suited for scheduled, recurring ingestion into a data warehouse for combined cross-cloud reporting.
Get AWS Marketplace Disbursements Analytics
This endpoint returns AWS Marketplace disbursement analytics data. Use it to track payouts disbursed by AWS for marketplace transactions and to reconcile expected versus received funds.
This endpoint automatically retrieves the AWS Marketplace disbursements dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Disbursement data is commonly combined with revenue and orders data to build a complete picture of AWS Marketplace cash flow.
Get AWS Marketplace Revenue Analytics
This endpoint returns AWS Marketplace revenue analytics data. Use it to report on recognized and billed revenue from your AWS Marketplace listings.
This endpoint automatically retrieves the AWS Marketplace revenue dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Revenue analytics provide the basis for marketplace bookings and billings dashboards across your cloud go-to-market motion.
Get AWS Co-Sell Opportunities Analytics
This endpoint returns AWS co-sell opportunities analytics data. Use it to analyze co-sell engagement and pipeline activity reported through AWS Partner Central.
This endpoint automatically retrieves the AWS co-sell opportunities dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Co-sell analytics help measure the impact of partner-sourced and partner-influenced deals on your marketplace revenue.
Get Azure Marketplace Revenue Analytics
This endpoint returns Azure Marketplace revenue analytics data. Use it to report on revenue generated from your Microsoft Azure Marketplace listings.
This endpoint automatically retrieves the Azure Marketplace revenue dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Combine Azure revenue data with AWS and GCP revenue datasets to produce a unified multi-cloud revenue report.
Get Azure Marketplace Customers Analytics
This endpoint returns Azure Marketplace customer analytics data. Use it to analyze customer acquisition and activity within the Azure Marketplace.
This endpoint automatically retrieves the Azure Marketplace customers dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Customer analytics can be joined with revenue and orders data to understand spend and retention by customer.
Get Azure Marketplace Orders
This endpoint retrieves analytics data for Azure Marketplace orders. Use it to analyze order-level transactions and bookings within the Azure Marketplace.
This endpoint automatically retrieves the Azure Marketplace orders dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Orders data is commonly used alongside metered usage data to reconcile usage-based and committed Azure revenue.
Get Azure Marketplace Metered Usage
This endpoint retrieves analytics data for Azure Marketplace metered usage. Use it to track consumption-based billing and usage metering for your Azure Marketplace offerings.
This endpoint automatically retrieves the Azure Marketplace metered usage dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Metered usage data is essential for products that bill on consumption, enabling accurate usage-based revenue reporting.
Get Azure Co-Sell Opportunities
This endpoint retrieves analytics data for Azure co-sell opportunities. Use it to analyze co-sell engagement reported through the Microsoft partner portal.
This endpoint automatically retrieves the Azure co-sell opportunities dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Use this dataset alongside the AWS co-sell analytics endpoint to compare co-sell performance across cloud providers.
Get GCP Marketplace Disbursements
This endpoint retrieves analytics data for Google Cloud (GCP) Marketplace disbursements. Use it to track payouts disbursed by Google for marketplace transactions.
This endpoint automatically retrieves the GCP Marketplace disbursements dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
For an aggregated view of GCP payouts, use the "Get GCP Marketplace Disbursements Summary" endpoint instead.
Get GCP Marketplace Disbursements Summary
This endpoint retrieves summarized analytics data for GCP Marketplace disbursements. Use it when you need aggregated payout totals rather than individual disbursement records.
This endpoint automatically retrieves the GCP Marketplace disbursements summary dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Summary data reduces record volume and is convenient for high-level financial dashboards and period-over-period comparisons.
Get GCP Marketplace Charges and Usage
This endpoint retrieves analytics data for GCP Marketplace charges and usage. Use it to analyze billed charges and consumption for your Google Cloud Marketplace offerings.
This endpoint automatically retrieves the GCP Marketplace charges and usage dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Charges and usage data is the GCP equivalent of consumption-based billing reporting and supports accurate usage-based revenue analysis.
Get GCP Marketplace Daily Insights
This endpoint retrieves daily insights analytics data for the GCP Marketplace. Use it to monitor day-level marketplace performance and trends.
This endpoint automatically retrieves the GCP Marketplace daily insights dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
For incremental ingestion that fetches only newly added daily records, use the "Get GCP Marketplace Incremental Daily Insights" endpoint.
Get GCP Marketplace Incremental Daily Insights
This endpoint retrieves incremental daily insights analytics data for the GCP Marketplace. Use it for recurring ingestion that focuses on the most recent daily records rather than the full history.
This endpoint automatically retrieves the GCP Marketplace incremental daily insights dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Incremental endpoints are well suited for scheduled flows, reducing the volume of data transferred on each run.
Get GCP Marketplace Monthly Insights
This endpoint retrieves monthly insights analytics data for the GCP Marketplace. Use it to monitor month-level marketplace performance for trend and period reporting.
This endpoint automatically retrieves the GCP Marketplace monthly insights dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
For recurring flows that fetch only the most recent monthly records, use the "Get GCP Marketplace Incremental Monthly Insights" endpoint.
Get GCP Marketplace Incremental Monthly Insights
This endpoint retrieves incremental monthly insights analytics data for the GCP Marketplace. Use it for recurring ingestion that focuses on the most recent monthly records rather than the full history.
This endpoint automatically retrieves the GCP Marketplace incremental monthly insights dataset. No additional configuration is required beyond selecting this endpoint template.
Analytics records are returned under the response's data array, which Nexla organizes into individual records.
Incremental endpoints minimize redundant data transfer and are recommended for scheduled, ongoing analytics pipelines.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Clazar data sources can also be manually configured to ingest data from any valid Clazar API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters such as query-parameter filters on a list endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Clazar API endpoints are served from the https://api.clazar.io base URL—for example, https://api.clazar.io/contracts to list contracts, or https://api.clazar.io/listings/{'{listing_id}'} to retrieve a single listing by ID. Clazar data-retrieval endpoints use the GET method.
For Clazar list endpoints (buyers, listings, contracts, opportunities, private offers), enter $.results[*] as the path to data; for analytics endpoints, enter $.data[*]. List endpoint responses also include pagination metadata (such as total count and page links) alongside the results array, which can be preserved as common metadata for each record by specifying its path in the Path to Metadata in Response field.
You do not need to include the Authorization header in Request Headers—the OAuth2 access token is attached automatically by Nexla based on your credential configuration.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Clazar data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Clazar destination, and select the Send to Destination option from the menu. Select the Clazar connector from the list of available destination connectors, then select the credential that will be used to connect to the Clazar organization, and click Next; or, create a new Clazar credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Clazar endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each record in the Nexset is sent to the Clazar API as a JSON request body. The endpoint templates that update, publish, or delete an existing object require an object ID, which you provide as a configuration parameter. For complete details about the request fields expected by each endpoint, refer to the Clazar developer documentation.
Create Listing
This endpoint creates a new marketplace listing in Clazar. Use it to programmatically publish new product listings to your connected AWS, Azure, or GCP marketplaces.
Each record in the Nexset is sent as the JSON body of a POST request to the Clazar listings endpoint. No additional parameters are required for this template.
Ensure each record contains the fields required by the Clazar API to create a listing. Use the Sample Payload panel to verify the request body before activating the destination.
Confirm that your Nexset fields map to the listing attributes expected by Clazar. Refer to the Clazar API reference for the complete list of required and optional fields.
Update Listing
This endpoint updates an existing marketplace listing by its ID. Use it to modify the details of a listing that has already been created in Clazar.
Enter the listing identifier in the Listing ID field. This identifies the specific listing that will be updated and can be obtained from the "List Listings" or "Get Listing" data source endpoints.
Each record in the Nexset is sent as the JSON body of a PUT request to update the specified listing.
The Listing ID is required for this endpoint. Verify the ID corresponds to the listing you intend to update before activating the destination.
Create Opportunity
This endpoint creates a co-sell opportunity in Clazar, which is synced to the AWS and Azure partner portals. Use it to automate the creation of co-sell deals from your CRM or pipeline data.
Each record in the Nexset is sent as the JSON body of a POST request to the Clazar opportunities endpoint. No additional parameters are required for this template.
Ensure each record contains the fields required by the Clazar API to create a co-sell opportunity, such as customer and deal details.
Co-sell opportunities created through this endpoint are synchronized with the relevant cloud partner portals, so confirm that records contain accurate, complete deal information.
Update Opportunity
This endpoint updates an existing co-sell opportunity by its ID. Use it to keep co-sell deal records in sync as deals progress through your pipeline.
Enter the opportunity identifier in the Opportunity ID field. This identifies the specific opportunity that will be updated and can be obtained from the "List Opportunities" data source endpoint.
Each record in the Nexset is sent as the JSON body of a PUT request to update the specified opportunity.
The Opportunity ID is required for this endpoint. Updates are synced to the relevant cloud partner portal, so verify the ID and deal details before activating the destination.
Create Private Offer
This endpoint creates a new private offer for a buyer. Use it to automate the drafting of private, renewal, or agreement-based offers across your connected marketplaces.
Each record in the Nexset is sent as the JSON body of a POST request to the Clazar private offers endpoint. No additional parameters are required for this template.
Ensure each record contains the fields required by the Clazar API to create a private offer, such as the buyer, pricing, and terms.
Creating a private offer drafts the offer. To send the offer to the buyer, use the "Publish Private Offer" endpoint with the resulting offer ID.
Update Private Offer
This endpoint updates or extends an existing private offer by its ID. Use it to revise the terms or pricing of a drafted private offer before it is published.
Enter the private offer identifier in the Private Offer ID field. This identifies the specific offer that will be updated and can be obtained from the "List Private Offers" or "Get Private Offer" data source endpoints.
Each record in the Nexset is sent as the JSON body of a PUT request to update the specified private offer.
The Private Offer ID is required for this endpoint. Verify the ID corresponds to the offer you intend to update before activating the destination.
Publish Private Offer
This endpoint publishes (sends) a drafted private offer to the buyer. Use it to release a private offer once its terms have been finalized.
Enter the private offer identifier in the Private Offer ID field. This identifies the drafted offer that will be published.
Each record in the Nexset is sent as the JSON body of a POST request to the publish endpoint for the specified offer.
Publishing a private offer sends it to the buyer and cannot be undone in the same way as editing a draft. Confirm that the offer details are correct before activating this destination.
Delete Private Offer
This endpoint cancels or deletes an existing private offer by its ID. Use it to remove a private offer that is no longer needed.
Enter the private offer identifier in the Private Offer ID field. This identifies the offer that will be deleted or cancelled.
This endpoint issues a DELETE request for the specified offer and does not require a request body.
Deleting or cancelling a private offer is a significant action. Verify the Private Offer ID before activating this destination to avoid removing the wrong offer.
Clazar destinations can also be manually configured to send data to any valid Clazar API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Clazar API endpoints are served from the https://api.clazar.io base URL—for example, https://api.clazar.io/opportunities to create an opportunity. For update, publish, or delete operations, include the ID of the object at the end of the URL, such as https://api.clazar.io/private_offers/{'{private_offer_id}'}. Clazar write endpoints commonly use POST (creating new objects or triggering actions such as publishing an offer), PUT (updating an existing object by its ID), and DELETE (cancelling or removing an existing object by its ID). The Clazar API expects JSON request bodies, so select the JSON content format.
You do not need to include the Authorization header in Request Headers—the OAuth2 access token and the Content-Type header are handled automatically by Nexla. The Clazar create, update, publish, and delete endpoints operate on a single object per request, so use record batching only when the target endpoint accepts multiple records in one request body.
Nexla can automatically send the response received from the Clazar API after each call to a new Nexla webhook data source, which is useful for tracking the status of each call and capturing information such as the ID of a newly created listing or private offer.
Sending test data to the create, update, publish, or delete endpoints performs a real operation against your Clazar account. Use test records carefully, particularly for the publish and delete private offer endpoints.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Clazar endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Clazar until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
