Trustpilot is automatable through its API

Trustpilot is automatable today through its APIs. Public APIs take the API key, which Trustpilot also calls the client ID, in an apikey header. Private APIs use OAuth 2.0. The authentication overview documents authorization-code, implicit, and client-credentials grants. Access tokens expire after 100 hours and refresh tokens after 30 days. Private calls send Authorization Bearer. The password grant is still listed and is marked deprecated. The same page says password, authorization-code, and implicit grants do not support multi-factor authentication. Refreshing too often returns 429. The developer home and the authentication navigation list invitations, business units, locations, product reviews, service reviews, and a Data Solutions API for business profiles and consumer reviews. This pass did not open each module reference, so coverage is partial. No Trustpilot MCP server was established from the pages opened here. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 6 because the grants and resource families are documented and MFA and module details remain limited.

Best path today: api · Overall automatability: 6/10