API Setup

Choose your Host Region to have the documentation adapt to your use case.

Host Region

Business Use Case

You can use this API to create or update a single Account in CustomerGauge. By supplying your Accounts with rich information, you can get much more granular Account filtering in your reports.

Our PUT Records API has a wide variety of applications. The API allows you to create or update a single record into any of the following objects:

Good to Know

Changes to Import Configurations

If a change happens to the implementation of the API (for example a field name change), that should be reflected in the used Inbound Mapping as well. Ignoring to do so will cause the API to silently fail for the fields involved.

Required Fields

The following fields are required in your Inbound Mapping:

Data TypeRequired Fields
  • Account Name


An Inbound Mapping reference is required to make requests to this API, all your mapping references can be found in Data → Rest APIs → Inbound Mapping.

Setting New Inbound Mapping

1. Go to Data → Rest APIs.

2. Select Inbound Mapping in the menu.

3. Click on +New Mapping button.

4. On Data type choose Account and fill the Configuration name field.

5. On Field Mapping choose all the fields you want to import into the system and their Field Heading.

6. Click on the Save button to finish the mapping creation.


OAuth2 Authentication is used to connect to this API. Once you've created your Connected App, you can acquire a Bearer Access Token by calling our OAuth2/Token API:

curl -X POST -H "Content-Type: application/x-www-form-urlencoded"
-d "grant_type=client_credentials&client_id={{ Client ID }}&client_secret={{ Client Secret }}"
https://auth.{{ apiRegion }}.customergauge.com/oauth2/token

The acquired Bearer Access Token is used in the Authorization header in your API request.


Endpoint URL
https://imports.api.{{ apiRegion }}.customergauge.com/records/



Use these parameters in the API request to pass the relevant information to the API.

ParameterDescriptionRulesExample Values

Configuration reference for data type and mapping.

You can find it in Data → Rest APIs → Inbound Mapping, under the Reference column.

  • Required
record[]An array for all the fields to be imported.

The values in the array must be the same set up in the API mapping referenced in the configuration parameter.

  • Required

Supported Formats

JSON (raw request body)

Data can be passed to this API using the JSON format in the body of the request.

Example parameters:

"configuration": "53505294-0b20-2509-b15d-c8e377701d66",
"record": {
"Account Name": "ACME",
"First Name": "Joe",
"Last Name": "Doe",
"Email": "joe.doe@example.com"

x-www-form-urlencoded (body)

Data can be passed to this API using the x-www-form-urlencoded format in the body of the request.

Example parameters:

configuration: "12305294-0b20-4009-b95d-c8123301d66"
record[Account Name]: "ACME"
record[First Name]: "Joe"
record[Last Name]: "Doe"
record[Email]: "joe.doe@example.com"


HTTP Status CodeDescription
200OK - everything worked as expected.

Example Response Body
An empty Response Body will be returned when successful.
422An issue occurred - this usually means one of the required fields is missing.

Example Response Body
"message": "The given data was invalid.",
"errors": {
"configuration": [
"The configuration field is required."


Postman example

Download Postman example

After importing the Postman example, make sure to change the Host Region and Authentication accordingly.

Not the API you're looking for?

Get an overview of our APIs here.