Track PMS
Track PMS is a property management platform for vacation rental and hospitality operators, covering reservations, contacts, accounting, and housekeeping and maintenance operations. Its REST API exposes this data for integration and automation. Nexla connects to the Track API using HTTP Basic authentication to read operational and accounting records and to create reservations, contacts, and charges.
Power end-to-end data operations for your Track PMS API with Nexla. Our bi-directional Track PMS connector is purpose-built for Track PMS, 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 Track PMS or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Track PMS workflows fast, secure, and fully governed.
Features
Type: API
- 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 Track PMS credential, you need an API Key and API Secret from your Track account, along with the base URL for your Track environment. The Track API uses HTTP Basic authentication, sending the API Key as the username and the API Secret as the password on every request.
To obtain your credentials, follow these steps:
-
Sign in to your Track account with an administrator user.
-
Navigate to Configuration > Company Setup > API Keys.
-
Click the + Server Key button to generate a new key. Track will display a Server API Key and a corresponding Secret.
-
Copy the API Key and Secret and store them securely. The Secret is sensitive and may not be retrievable again after you leave the page.
-
Determine your base URL. Track API requests are made against your account's domain with the
/apipath appended, for examplehttps://your-domain.trackhs.com/api.
If you do not have access to generate keys yourself, contact your Track administrator or Track support to request API credentials. For more detail, see the Track API documentation.
Authenticate
Credentials required
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key | Yes | No | Track PMS API key (used as the Basic auth username). |
| API Secret | Yes | Yes | Track PMS API secret (used as the Basic auth password). |
| Base URL | Yes | No | API base URL including the /api path, e.g. https://your-domain.trackhs.com/api |
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
Enter your Track PMS API Key and API Secret in the corresponding fields. These are used as the username and password for HTTP Basic authentication against the Track API.
-
Enter your Base URL, including the
/apipath, in the Base URL field, for examplehttps://your-domain.trackhs.com/api.The API Secret is sensitive information and should be kept confidential. If it is compromised, generate a new server key in your Track account under Configuration > Company Setup > API Keys and update your Nexla credential.
-
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 Track PMS connector tile, then select the credential that will be used to connect to Track PMS, and click Next; or, create a new Track PMS 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 Track PMS 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.
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
Track PMS data sources can also be manually configured to ingest data from any valid Track 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.
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 Track PMS 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 Track PMS destination, and select the Send to Destination option from the menu. Select the Track PMS connector from the list of available destination connectors, then select the credential that will be used to connect to Track PMS, and click Next; or, create a new Track PMS 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 Track PMS 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.
Manual configuration
Track PMS destinations can also be manually configured to send data to any valid Track 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.
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 Track PMS endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Track PMS endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.