Skip to main content

Thanx (API Key Access)

Thanx is a customer engagement and loyalty platform for restaurants and retailers that helps brands acquire, engage, and retain customers through personalized rewards, offers, and marketing. The Thanx (API Key Access) connector is a source-only ELT connector that extracts data such as guests, transactions, and visits from the Thanx REST API using API key authentication. Select from pre-built feeds — guest IDs, per-guest visits, transactions, and visits — and Nexla ingests each selected feed on a schedule.

Thanx (API Key Access) icon

Power end-to-end data operations for your Thanx (API Key Access) API with Nexla. Our bi-directional Thanx (API Key Access) connector is purpose-built for Thanx (API Key Access), 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 Thanx (API Key Access) or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Thanx (API Key Access) 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​

The Thanx (API Key Access) connector authenticates with a Thanx API access token. Thanx sends the token as a bearer credential in the Authorization header (Authorization: Bearer <access token>) on every request to the Thanx REST API at https://api.thanx.com/v1.

Before creating a credential in Nexla, obtain a Thanx API access token:

  1. Contact your Thanx account team or partner support to request API access for your Thanx account. Thanx provisions API access tokens for approved integrations rather than exposing self-service key generation.

  2. Confirm which data your token is authorized to read — for example, guests, transactions, and visits — so the feeds you configure in Nexla match the token's granted access.

  3. Store the access token securely, and treat it as a sensitive secret. Rotate the token if it is exposed, and request a replacement from Thanx if it is lost.

For details about the Thanx REST API and available data, see the Thanx developer documentation.

Authenticate​

Credentials required​

Use your Thanx API access token.

FieldRequiredSecretDescription
Access TokenYesYesYour Thanx API access token

Create a credential in Nexla​

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

  2. 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. Use them to identify the Thanx account or access level represented by this credential.

  3. Enter your Thanx API access token in the Access Token field. Nexla sends this token to Thanx as a bearer token in the Authorization header when reading data, and stores it securely as a secret.

  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 creation and can be selected for use with Thanx (API Key Access) flows.

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 Thanx (API Key Access) connector tile, then select the credential that will be used to connect to your Thanx account, and click Next; or, create a new Thanx credential for use in this flow. Thanx data sources are configured using pre-built feed templates, with each feed corresponding to a Thanx object type; sources can also be configured manually to ingest data from any valid Thanx REST API endpoint.

Endpoint templates​

Select the Thanx feed from which this source will fetch data from the Endpoint pulldown menu. Available feed templates are listed in the expandable sections below. Click on a feed to view details and configuration instructions.

Get Guest IDs

Returns the list of available Guest IDs from your Thanx account. This is a discovery feed used to enumerate the guests you can query, and it supplies the Guest ID values consumed by the Guest Visits by ID feed.

  • Select Get Guest IDs from the Endpoint pulldown menu.
  • No additional configuration is required. The feed returns the Guest IDs accessible to the token used in the Nexla credential.

Guest Visits by ID

Fetches the visits recorded for a specific guest, using that guest's identifier. Use this feed when you need visit history scoped to an individual guest rather than the full account-wide visits feed.

  • Select Guest Visits by ID from the Endpoint pulldown menu.
  • Enter the Guest ID to fetch visits for in the Guest ID field. This value is required and identifies the guest whose visits are retrieved. Guest IDs can be obtained from the Get Guest IDs feed.
  • Set the Sync Schedule field to control how often the sync runs. This value is a cron expression, and the default is 0 * * * * (hourly).

Transactions

Fetches all transactions from your Thanx account. Use this feed to ingest transaction records for reporting, analytics, or downstream integration.

  • Select Transactions from the Endpoint pulldown menu.
  • Set the Sync Schedule field to control how often the sync runs. This value is a cron expression, and the default is 0 * * * * (hourly).

Visits

Fetches all visits from your Thanx account. Use this feed to ingest account-wide visit records across all guests.

  • Select Visits from the Endpoint pulldown menu.
  • Set the Sync Schedule field to control how often the sync runs. This value is a cron expression, and the default is 0 * * * * (hourly).

Once the selected feed 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​

Thanx data sources can also be manually configured to ingest data from any valid Thanx REST API endpoint, including endpoints not covered by the pre-built feed templates. 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.

The Thanx REST API base URL is https://api.thanx.com/v1 (for example, https://api.thanx.com/v1/transactions). Nexla sends the API access token as a bearer token in the Authorization header on each request.

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 Thanx data source. Nexla will now begin ingesting data from the configured Thanx feeds and will organize any data that it finds into one or more Nexsets.