TABLE OF CONTENTS

• API Setup
• Business Use Case
• Good to Know
• Authentication
• Endpoint
• Request
  • Payload
• Response
• Not the API you're looking for?

API Setup

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

Business Use Case

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:

• Account
• Contact
• Survey Record (Response only, no update supported)

After a successful request, the data will be uploaded/updated in the system and a survey response will be recorded under the contact referenced.

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.

Touchpoints

When importing Touchpoints, only Touchpoints that exist in your CustomerGauge system will be accepted. Touchpoints can be managed in System Settings by System Administrators.

Authentication

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.

Note: The Access Token is only valid for up to 1 hour. Save the Access Token temporarily when calling the API multiple times in a row, or obtain a fresh Access Token before calling the API.

If you can not use OAuth2 Authentication, you can use our Incoming Webhook functionality.

Endpoint

Endpoint URL

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

Request

Payload

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

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",
        "Sent Date": "2023-05-10 11:34:56",
        "Survey Completed Date": "2022-05-10 12:34:56",
        "NPS Score": "10"
     }
}

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"
record[Sent Date]: "2023-05-10 11:34:56"
record[Survey Completed Date]: "2022-05-10 12:34:56"
record[NPS Score]: "10"

{
    "message": "The given data was invalid.",
    "errors": {
        "configuration": [
            "The configuration field is required."
        ]
    }
}