Trustpilot
Trustpilot is a consumer review platform where businesses collect, manage, and respond to customer reviews and ratings. Nexla connects to the Trustpilot API to ingest data such as business unit profiles, service and product reviews, review summaries, and conversations, and to push records back to Trustpilot to send review invitations and manage review conversations.
Power end-to-end data operations for your Trustpilot API with Nexla. Our bi-directional Trustpilot connector is purpose-built for Trustpilot, 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 Trustpilot or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Trustpilot 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
Nexla can authenticate to Trustpilot using either an API key or an OAuth 2.0 client-credentials flow. Both methods rely on the API key and API secret that Trustpilot issues when you register an application in your Trustpilot Business account. Public Trustpilot endpoints accept the API key directly, sent in the apikey request header, while private endpoints that expose customer data require an OAuth 2.0 access token obtained with your client credentials.
To obtain your Trustpilot API credentials:
-
Sign in to your Trustpilot Business account. Registering applications and managing API access requires a Trustpilot Business plan with API access enabled.
-
Register a new application through the Trustpilot Business portal. When the application is created, Trustpilot provides an API Key, which serves as your Client ID, and an API Secret, which serves as your Client Secret.
-
Copy the API key and API secret and store them securely. The API secret is shown so that you can use it to request OAuth access tokens for private endpoints, and it should be kept confidential.
-
Note which endpoints you plan to use. Public endpoints authenticate with the API key alone, while private endpoints (for example, private reviews or conversation management) require the OAuth 2.0 client-credentials flow using your client ID and client secret.
For detailed information about registering an application, authentication grant types, and available endpoints, see the Trustpilot API documentation.
Authenticate
Credentials required
- OAuth 2.0
- Api Key
A direct authentication flow between a client application and server using client credentials
| Field | Required | Secret | Description |
|---|---|---|---|
| Client ID | Yes | No | A unique public identifier assigned to your application |
| Client Secret | Yes | Yes | A confidential password provided alongside the client ID |
An authentication method that requires sending a unique secret token with each API request
| Field | Required | Secret | Description |
|---|---|---|---|
| API Key Value | Yes | Yes | An encoded string value used as a secret token to authenticate API requests |
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.
-
Provide the authentication details for your chosen method. For API key authentication, enter your Trustpilot API key in the API Key Value field. For OAuth 2.0, enter your Trustpilot API key in the Client ID field and your API secret in the Client Secret field.
Your Trustpilot API secret grants access to private endpoints and customer data. Keep it confidential, and if it is compromised, regenerate your application credentials in the Trustpilot Business portal.
For detailed information about Trustpilot authentication, grant types, and available endpoints, see the Trustpilot API documentation.
-
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 Trustpilot connector tile, then select the credential that will be used to connect to Trustpilot, and click Next; or, create a new Trustpilot 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 Trustpilot 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
Trustpilot data sources can also be manually configured to ingest data from any valid Trustpilot 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 Trustpilot 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 Trustpilot destination, and select the Send to Destination option from the menu. Select the Trustpilot connector from the list of available destination connectors, then select the credential that will be used to connect to Trustpilot, and click Next; or, create a new Trustpilot 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 Trustpilot 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
Trustpilot destinations can also be manually configured to send data to any valid Trustpilot 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.
Trustpilot APIs expect JSON format for most operations. For update operations, include the identifier of the resource to be updated in the request.
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 Trustpilot endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Trustpilot endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.