Skip to main content

Authorization

Follow this guide to create a new Postscript credential that will allow Nexla to authenticate to and exchange data with your Postscript account.
postscript_api_auth.png

Postscript

Prerequisites

Before creating a Postscript credential, you need to obtain your API key from your Postscript account. Postscript uses API key authentication for all API requests, with the API key sent in the X-Postscript-Shop-Token header.

To obtain your Postscript API key, follow these steps:

  1. Sign in to your Postscript account using your administrator credentials.

  2. Navigate to your account settings or API management section in the Postscript interface.

  3. Look for the API or API Keys section in your account settings, or navigate to Settings > API or Integrations > API.

  4. If you don't have an API key yet, look for the option to generate or view your API key.

  5. Click Generate API Key or Create API Key to create a new API key.

  6. Configure your API key settings:

    • Enter a name for the API key (e.g., "Nexla Integration")
    • Review and select the permissions or scopes for the key (if applicable)
  7. Click Generate or Create to create the API key.

  8. Copy the API key immediately after it's generated, as it may not be accessible again after you navigate away from the page.

  9. Store the API key securely, as you will need it to configure your Nexla credential. The API key is sensitive information and should be kept confidential.

The API key is sent in the X-Postscript-Shop-Token header for all API requests to the Postscript API. The API key authenticates your requests and grants access to Postscript resources based on your account permissions. If your API key is compromised, you should immediately revoke it in your Postscript account settings and generate a new one. For detailed information about obtaining API keys, API authentication, and available endpoints, refer to the Postscript API documentation.

Create a Postscript Credential

  • To create a new Postscript credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Postscript

PostscriptCred.png

Credential Name & Description

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

API Key Authentication

Postscript uses API key authentication for all API requests. The API key is sent in the X-Postscript-Shop-Token header to authenticate API requests to the Postscript API.

  1. Enter your Postscript API key in the API Key Value field. This is the API key you obtained from your Postscript account settings (Settings > API or API Keys section). The API key is sent in the X-Postscript-Shop-Token header for all API requests to the Postscript API. The API key is sensitive information and must be kept confidential.

    Your Postscript API key can be found in your Postscript account settings under Settings > API or API Keys section. The API key is sent in the X-Postscript-Shop-Token header for all API requests to the Postscript API.

    If your API key is compromised, you should immediately revoke it in your Postscript account settings and generate a new one. The API key provides access to your Postscript account data and should be treated as sensitive information. Keep your API key secure and do not share it publicly.

    For detailed information about obtaining API keys, API authentication, and available endpoints, see the Postscript API documentation.

Save the Credential

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.