Trengo API explorer
Build a Trengo REST API request to read tickets, inspect the required headers and generate cURL or JavaScript.
By the Apideck team · Independent of Trengo · Sources reviewedList your tickets
Read tickets accessible to your Trengo user. Start with page 1; the example only reads data and does not send messages or change tickets.
Use a Trengo personal access token in the Authorization: Bearer header, with Accept and Content-Type set to application/json. Requests act on behalf of the token owner. Keep the token private; these REST credentials do not establish MCP authentication.
Endpoint reference ↗ · Authentication reference ↗Trengo cURL example
curl --request GET \ --url 'https://app.trengo.com/api/v2/tickets?page=1' \ --header 'accept: application/json' \ --header 'authorization: Bearer YOUR_TRENGO_TOKEN' \ --header 'content-type: application/json'
JavaScript fetch example
const response = await fetch("https://app.trengo.com/api/v2/tickets?page=1", {
"method": "GET",
"headers": {
"accept": "application/json",
"authorization": "Bearer YOUR_TRENGO_TOKEN",
"content-type": "application/json"
},
"credentials": "omit",
"redirect": "error",
"referrerPolicy": "no-referrer"
});
console.log(response.status);
console.log(await response.text());Credential values are placeholders. This is request code, not a recorded API response.
Trengo API request questions
How do I test Trengo API calls?
Read tickets accessible to your Trengo user. Start with page 1; the example only reads data and does not send messages or change tickets. Load the request in the explorer, supply any required credentials, and select Send. Browser execution depends on the provider's CORS policy; use the generated cURL locally when browser access is blocked.
What authentication does the Trengo example require?
Use a Trengo personal access token in the Authorization: Bearer header, with Accept and Content-Type set to application/json. Requests act on behalf of the token owner. Keep the token private; these REST credentials do not establish MCP authentication.
Can I generate Trengo cURL and JavaScript examples?
Yes. Configure the request URL, method, headers and body, then select cURL or JavaScript in the code panel. Generated code includes any credentials you entered. Nothing runs automatically, and closing the modal clears its working state.
What the explorer does
Requests go directly from your browser to the provider. It supports manual HTTPS requests and a subset of OpenAPI 3.x / Swagger 2.0 request generation. External schema references need a bundled file; complex parameter formats and OAuth sign-in require your own tooling. A failed browser request may still have reached the API, so check before retrying a change.
API Tracker is an independent request-building tool, not the provider’s official playground. Source review is not a live connection test.