Skip to main content

Demandbase 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 Demandbase location.
demandbase_api.png

Demandbase

Create a Demandbase Destination​

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

  2. Select the Demandbase connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Demandbase account, and click Next; or, create a new Demandbase credential for use in this flow.

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

    Demandbase destinations can also be configured manually, allowing you to send data to Demandbase 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 Demandbase API endpoints. Each template is designed specifically for the corresponding Demandbase endpoint, making destination setup easy and efficient.

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

    Match Company and Contact

    Submit company and contact data to the Demandbase real-time match endpoint to identify and enrich records against the Demandbase database. Use this endpoint when you need to match individual records or small batches in near-real time — for example, enriching CRM records as they are created or updated. Each record submitted is matched synchronously, and Demandbase returns enriched profile data including firmographics, contact details, and quality scores.

    • Map the fields in your Nexset to the Demandbase match API request schema. The match endpoint accepts JSON payloads that can include company identifiers (domain, name, location) and/or contact identifiers (email, name, title) for matching. Refer to the Demandbase B2B API endpoint reference for the complete request schema.
    • No additional template parameters are required for this endpoint. The full request payload is derived from the Nexset data mapped to this destination.

    For large volumes of records, consider using the Create Bulk Match Job endpoint instead, which submits an asynchronous job and is optimized for high-volume matching operations. The real-time Match endpoint is best suited for low-latency, record-by-record enrichment scenarios.

    Create Bulk Match Job

    Submit a large batch of company and contact records to Demandbase for asynchronous bulk matching. Use this endpoint for high-volume matching operations — for example, enriching an entire CRM export or a large list of leads. Demandbase processes the records asynchronously and returns a Job ID that can be used to monitor progress via the Get Job Status source endpoint.

    • Map the fields in your Nexset to the Demandbase bulk match job request schema. The request body should contain the array of company and/or contact records to be matched. Refer to the Demandbase B2B API endpoint reference for the complete request body schema.
    • No additional template parameters are required for this endpoint. The full request payload is derived from the Nexset data mapped to this destination.

    After submitting a bulk match job, use the Get Job Status source endpoint with the returned Job ID to monitor processing progress. The Demandbase API returns the Job ID in the response body after the job is created.

    Create Import Job

    Create a new data import job in Demandbase to ingest account, contact, opportunity, or activity records into the Demandbase platform. This endpoint initiates the import workflow — after creating the job, use the Submit Data to Import Job endpoint to submit the actual records for processing. The Demandbase Data Import API can process up to three million records per hour.

    • Map the fields in your Nexset to the Demandbase import job creation request schema. The request body should specify the type of data being imported (account, contact, opportunity, or activity) and any relevant import configuration. Refer to the Demandbase Import API documentation for the complete request body schema.
    • No additional template parameters are required for this endpoint. The full request payload is derived from the Nexset data mapped to this destination.

    Creating an import job returns a Job ID that must be used in the subsequent Submit Data to Import Job call to associate the data with this job. Store or pass along the Job ID using a Nexla flow step or lookup.

    Submit Data to Import Job

    Submit records to an existing Demandbase import job for processing. This endpoint is used after Create Import Job to deliver the actual data payload. Use this endpoint to send the account, contact, opportunity, or activity records that should be ingested into Demandbase as part of the import job.

    • Job ID (Required): Enter the unique ID of the import job to which data will be submitted. This ID is returned by the Create Import Job endpoint when the job is created.
    • Map the record fields in your Nexset to the import data payload schema expected by the Demandbase Import API for the applicable record type (account, contact, opportunity, or activity). Refer to the Demandbase Import API documentation for field requirements and formats.

    Data submitted to import jobs should be structured according to the Demandbase Import API schema for the applicable record type. After submitting data, use the Get Import Job Status source endpoint with the Job ID to monitor ingestion progress.

    Create Activity Type

    Create a new activity type definition in Demandbase. Activity types define the categories of engagement events — such as web visits, form submissions, email opens, or custom interactions — that can subsequently be imported into Demandbase via the Data Import API. Activity types must be created before activity data referencing them can be imported.

    • Map the fields in your Nexset to the Demandbase activity type creation request schema. The request body should include the activity type name, description, and any field schema definitions. Refer to the Demandbase Import API documentation for the complete activity type schema.
    • No additional template parameters are required for this endpoint. The full request payload is derived from the Nexset data mapped to this destination.

    Once created, activity types can be managed using the Update Activity Type endpoint. Use the List Activity Types and Get Activity Type source endpoints to retrieve existing activity type definitions.

    Update Activity Type

    Update an existing activity type definition in Demandbase. Use this endpoint to modify the configuration of an activity type — for example, to add new fields, update the description, or change the schema to accommodate new event data structures.

    • Map the fields in your Nexset to the Demandbase activity type update request schema. The request body should include the activity type ID and the updated field values. Refer to the Demandbase Import API documentation for the complete schema.
    • No additional template parameters are required for this endpoint. The full request payload is derived from the Nexset data mapped to this destination.

    Create User

    Create a new user in the Demandbase admin system. Use this endpoint to provision Demandbase accounts programmatically — for example, as part of an automated onboarding workflow triggered when a new employee is added to your HR system.

    • Map the fields in your Nexset to the Demandbase user creation request schema. The request body should include the user's email address, name, and assigned role. Refer to the Demandbase User Admin API documentation for the complete request schema and available role values.
    • No additional template parameters are required for this endpoint. The full request payload is derived from the Nexset data mapped to this destination.

    Access to user administration endpoints requires that your API Key Set includes Admin API permissions. Ensure the credential used for this destination was created with Admin API access enabled in the Demandbase Settings > APIs > API Key Sets panel.

    Update User

    Update the profile or role of an existing user in the Demandbase admin system. Use this endpoint to synchronize user information with an external identity provider or HR system — for example, updating a user's role when they change teams.

    • Map the fields in your Nexset to the Demandbase user update request schema. The request body should include the user ID and the fields to be updated. Refer to the Demandbase User Admin API documentation for the complete schema and updatable fields.
    • No additional template parameters are required for this endpoint. The full request payload is derived from the Nexset data mapped to this destination.

    Admin API permissions are required for this endpoint. Use the List Users or Get User source endpoints to retrieve the User IDs needed for update operations.

    Delete User

    Delete a user from the Demandbase admin system by their unique User ID. Use this endpoint to deprovision Demandbase accounts — for example, as part of an automated offboarding workflow triggered when an employee leaves your organization.

    • User ID (Required): Enter the unique Demandbase identifier for the user to be deleted. User IDs can be retrieved using the List Users or Get User source endpoints.

    :::warning Important Deleting a user is a permanent action and cannot be undone. Ensure the correct User ID is specified before executing this destination. :::

    Admin API permissions are required for this endpoint.

Configure Manually​

Demandbase destinations can be manually configured to send data to any valid Demandbase API endpoint. This allows you to access write endpoints not covered by the pre-built templates or to apply custom request structures beyond those available in the templates.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Demandbase API after each call to a new Nexla webhook data source — enabling you to capture job IDs, match results, or other response data for downstream processing.

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 Demandbase API from the Method pulldown menu. Common methods for Demandbase destination endpoints include:

    • POST: For creating new resources (match jobs, import jobs, activity types, users).
    • PUT: For updating existing resources (submitting data to import jobs, updating activity types and users).
    • DELETE: For removing resources (deleting users).

Data Format​

  1. Select the format in which the Nexset data will be sent to the Demandbase API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. Demandbase REST API endpoints accept JSON formatted request bodies.

API Endpoint URL​

  1. Enter the URL of the Demandbase API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters.

All Demandbase API endpoints begin with your account's base URL (default: https://uapi.demandbase.com) followed by the endpoint path. For endpoint paths that include resource IDs (such as User ID or Job ID), include the ID directly in the URL path. Refer to the Demandbase B2B API endpoint reference for a complete list of available destination endpoint paths.

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 the Authorization or Content-Type headers — these are automatically managed by Nexla based on your Demandbase credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Demandbase destination, select the attributes from the Exclude Attributes pulldown menu.

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

Response Webhook​

Optional

Nexla can automatically send the response received from the Demandbase API after each call to a new Nexla webhook data source. This option is particularly useful for capturing Job IDs returned by the Create Import Job or Create Bulk Match Job endpoints, enabling you to chain those IDs into subsequent flow steps for status monitoring or downstream processing.

  • 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 Demandbase 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 Demandbase 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 Demandbase API using the current settings.

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 begin sending data to the configured Demandbase endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to Demandbase until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.