Postscript

Postscript is a SMS marketing platform that enables businesses to engage customers through text messaging, providing tools for automated campaigns, customer segmentation, and conversational commerce to drive sales and retention.

Power end-to-end data operations for your Postscript API with Nexla. Our bi-directional Postscript connector is purpose-built for Postscript, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Postscript or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Postscript workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

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.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes	Account required to get Api key

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Postscript

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

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

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Postscript connector tile, then select the credential that will be used to connect to your Postscript account, and click Next; or, create a new Postscript credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Postscript endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Get message request by id

This endpoint template retrieves a message request by its ID from your Postscript account. Use this template when you need to retrieve information about a specific message request, including message status, content, and other message metadata.

• Enter the message request ID in the Message request Id field. This should be the unique identifier of the message request you want to retrieve. The message request ID determines which message request's information will be retrieved.

This endpoint returns a message request by its ID from your Postscript account, including message status, content, and other message metadata. The endpoint returns a single message request's information.

For detailed information about message requests, API response structures, and available message data, see the Postscript API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Postscript data sources can also be manually configured to ingest data from any valid Postscript API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Postscript API typically uses the GET method for retrieving data, with endpoint URLs following the pattern https://api.postscript.io/api/v2/{resource} (e.g., https://api.postscript.io/api/v2/message_requests/{id}). For the Response Data Path, use $ to extract the entire response for single-record endpoints, or $.items[*] to extract all items from the items array for list endpoints, depending on the endpoint. For detailed information about available endpoints, see the Postscript API documentation.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Postscript data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Postscript destination, and select the Send to Destination option from the menu. Select the Postscript connector from the list of available destination connectors, then select the credential that will be used to connect to your Postscript account, and click Next; or, create a new Postscript credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Postscript endpoints. 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.

post_message_request

This endpoint template sends message requests to your Postscript account using records from a Nexset. Use this template when you need to send SMS messages to customers through Postscript. Messages that are sent via the API still have to obey text messaging rules and regulations, which means Postscript has guardrails in place for all messages sent through the API.

• This endpoint automatically sends message requests from your data. No additional configuration is required beyond selecting this endpoint template. The request body should contain the message request data in JSON format matching the Postscript API structure.

This endpoint sends data as JSON in the request body to create message requests in your Postscript account. Each record from your Nexset will be sent as a separate API request to send a message in Postscript. The request body should contain the message request data in the format required by the Postscript API.

Messages sent via the API must comply with text messaging rules and regulations. Postscript has guardrails in place for all messages sent through the API to ensure compliance. The message structure must match the Postscript API's expected format. For detailed information about message creation, request body formats, available message properties, and messaging compliance, see the Postscript API documentation.

Manual configuration

Postscript destinations can also be manually configured to send data to any valid Postscript API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Postscript API typically uses the POST method with JSON format for creating message requests, sent to an endpoint URL such as https://api.postscript.io/api/v2/message_requests. The request body is typically {message.json} to send the entire Nexset data as JSON. Messages sent via the API must comply with text messaging rules and regulations — Postscript enforces guardrails on all messages sent through the API. For detailed information about request body formats and available endpoints, see the Postscript API documentation.

Save & activate

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

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