Gainsight PX API provides a programmatic (server-based) method to access the users, accounts, and events that have been captured by the Gainsight PX subscription. The Gainsight PX REST APIs can be used to perform most standard CRUD (Create, Read, Update, Delete) operations on entity (e.g. User and Account) objects, create custom events and fetch historical event data.

Data Payload

The API data (and responses) are JSON encoded with UTF-8 as either a single JSON object, or as a list of JSON objects.

Authorization

Authorization and access to the API is managed via API Keys. The API key value is passed on calls by adding a request header with the key X-APTRINSIC-API-KEY.

Generate API Keys

An API Key is required to access the Gainsight PX REST API.

To generate an API key:

  1. Navigate to Administration > REST API to access the API Keys page.

  2. Click New API Key. The New API Key window appears.

  3. Enter the following details:

   A. Name: Enter a name for API Key.

   B. Description: Enter a description.

   C. Permissions: Configure the following permissions.

    a. Read: This allows calls to read PX data via GET API calls.

    b. Write: This allows calls to edit, update and delete PX data via PUT and DELETE API calls.

    c. Production Launch: This access allows calls to launch engagements in production.

  4. Click Generate.

Errors

Errors are returned with error code and JSON response.

HTTP

• Requests are sent using HTTPS.
• Methods exposed are based on HTTP Verbs (GET, POST and DELETE).
• Resources are identified using URI’s.

Rate Limiting

The rate limit for public REST APIs is around 200 requests per second and 1 Million requests per day.

Page Handling

• The default pageSize on list calls (i.e. /users and /accounts) is 25. The pageSize can be changed by adding a pageSize parameter to the URL (i.e. /users?pageSize=100) with a max pageSize=1000.
• Use the returned scrollId to make a request for the next page of results (i.e. /users?pageSize=100&scrollId=XXXXXXX)
• Scroll until the returned result list is less than the requested size. Do not depend on the scrollId becoming null, in some cases it does not be null even though the last page of results is returned.

Historical Date Range Restrictions

• For all calls that return historical event information, the maximum date range is 190 days (~ 6 months).
• If no date range is specified, the last 1 day is the default date window. For quicker response times, it is recommended to use your needed date range and not full 6 months.
• If a date range larger than the maximum is specified, a 400 Bad Request error is thrown, with the message: “Exceeded date range190days”.
• To fetch more than 190 days of data, multiple calls will need to be made for smaller date ranges that are no more than the max allowed.

Case Sensitivity

• Case sensitivity is enforced when making a call to get user/account by id. Therefore, .../users/id=nora@example.com will not find a user whose id is Nora@example.com
• Case sensitivity is not enforced when using filters. For example, .../users/filter=id==nora@example.com; will find a user whose id is Nora@example.com.

Getting Started with Postman

Click here to download a Postman collection file containing sample calls that you can use to query and test the Gainsight PX REST API. The Postman tool is used to test the PX APIs. To use the sample API calls, you must define a Postman variable apiKey. This variable must be set to the PX API key which you have generated. This API key is not the same as your Product API key.

This is version 0.1.6 of this API documentation. Last update on Mar 19, 2026.