Skip to main content

Clazar Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Clazar location. With the Clazar destination connector, you can automate the creation and management of marketplace listings, co-sell opportunities, and private offers across the AWS, Azure, and GCP marketplaces directly from your Nexla flows.
clazar_api.png

Clazar

Create a Clazar Destination​

  1. Click the + icon on the Nexset that will be sent to the Clazar destination, and select the Send to Destination option from the menu.

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

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

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

Configure Using a Template​

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

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.

  • To configure this destination using a template, 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.

    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.

Configure Manually​

Clazar destinations can be manually configured to send data to any valid Clazar API endpoint. Manual configuration provides maximum flexibility for sending data to endpoints not covered by pre-built templates or when you need custom request configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Clazar API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, 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 write endpoints commonly use the following methods:

    • POST: For creating new objects (such as listings, opportunities, and private offers) or triggering actions (such as publishing an offer)
    • PUT: For updating an existing object by its ID
    • DELETE: For cancelling or removing an existing object by its ID

Data Format​

  1. Select the format in which the Nexset data will be sent to the Clazar API from the Content Format pulldown menu. The Clazar API expects JSON request bodies, so select the JSON format. Nexla will automatically convert the data to the selected format for each API call.

API Endpoint URL​

  1. Enter the URL of the Clazar API endpoint to which you want to send the Nexset data in the URL field. 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}'}.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. The Authorization header carrying the OAuth2 access token and the Content-Type header are handled automatically by Nexla.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Clazar destination, select the attributes from the Exclude Attributes pulldown menu. This is useful for removing internal or derived fields that should not be included in the Clazar request body.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

    Property Inside JSON Object

    1. Enter the name of the JSON property that should contain the batched records in the Property Name field.
    2. If any additional properties should be included in the request, enter the properties in the Other Props field in JSON format.

    Code

    1. Enter the code that will be used to create the batched request in the code editor below the Grouping Algorithm field.

    The Clazar create, update, publish, and delete endpoints operate on a single object per request. Use batching only when the target endpoint accepts multiple records in one request body.

Response Webhook​

Optional

Nexla can automatically send the response received from the Clazar API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call, such as the ID of a newly created listing or private offer.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Clazar API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Clazar API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Clazar API using the current settings.

    Sending test data to 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.

Save & Activate the Destination​

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