Skip to main content

Clazar Data Source

The Clazar connector enables you to ingest cloud marketplace data—including buyers, listings, contracts, private offers, co-sell opportunities, and revenue analytics from the AWS, Azure, and GCP marketplaces—directly into Nexla. This connector is particularly useful for consolidating multi-cloud marketplace reporting, syncing offer and contract data into a data warehouse, and powering revenue and co-sell analytics. Follow the instructions below to create a new data flow that ingests data from a Clazar source in Nexla.
clazar_api.png

Clazar

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Clazar connector tile from the list of available connectors. 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.

  3. In Nexla, Clazar data sources can be created using pre-built endpoint templates, which expedite source setup for common Clazar endpoints. Each template is designed specifically for the corresponding Clazar endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Clazar sources can also be configured manually, allowing you to ingest data from Clazar endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Clazar endpoints. Each template is designed specifically for the corresponding Clazar endpoint, making data source setup easy and efficient.

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.

Endpoint Settings​

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

    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.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Clazar data sources can be manually configured to ingest data from any valid Clazar API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations, such as applying query-parameter filters to a list endpoint.

With manual configuration, you can also create more complex Clazar sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Clazar API from the Method pulldown menu. Clazar data-retrieval endpoints use the following method:

    • GET: For retrieving data from the API

API Endpoint URL​

  1. Enter the URL of the Clazar API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. 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.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL.

Date/Time Macros (API URL)​

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements. This is useful for Clazar analytics endpoints when filtering by date ranges.

Macros are particularly useful for APIs that require date ranges, pagination parameters, or other dynamic values that change between data ingestion runs.

  1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

    • {now} – The current datetime
    • {now-1} – The datetime one time unit before the current datetime
    • {now+1} – The datetime one time unit after the current datetime
    • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

  2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

  3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Path to Data​

Optional

If only a subset of the data that will be returned by the API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain metadata, pagination information, or other data that you don't need for your analysis.

For Clazar, list endpoints (such as buyers, listings, contracts, opportunities, and private offers) return their records under a top-level results array, while analytics endpoints return their records under a top-level data array.

Path to Data is essential when API responses have nested structures. Without specifying the correct path, Nexla might not be able to properly parse and organize your data into usable records.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For Clazar list endpoints, enter $.results[*] to treat each element of the returned results array as a record.

    • For Clazar analytics endpoints, enter $.data[*] to treat each element of the returned data array as a record.

    Path to Data Example:

    If the API response is in JSON format and includes a top-level array named data that contains the relevant data, the path to the response would be entered as $.data[*].

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

    PathSuggestions.png

Metadata​

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records but isn't part of the main data array.

For Clazar list endpoints, the response includes pagination metadata (such as total count and page links) alongside the results array. You can preserve this context by specifying a path to it.

Metadata paths are particularly useful for preserving API response context like total counts, pagination information, or request timestamps that apply to all records in the response.

  • To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

    • For responses in JSON format, enter the JSON path to the object or array that contains the metadata, and for responses in XML format, enter the XPath.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers are often required for API versioning, content type specifications, or custom request requirements.

    You do not need to include any headers already present in the credentials. The Authorization header carrying the OAuth2 access token is handled automatically by Nexla based on your credential configuration.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, 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.