Test Connection
GET/api/temu/:integrationInstance/test-connection
Verifies that the stored Temu access token for a given integration instance is still valid by calling Temu's getWarehouses endpoint (the cheapest read with no required parameters).
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Used by the Integration Settings page to render a green/red status pill, and by the new-instance / reconnect flow to confirm the instance can actually talk to Temu before dispatching the initial sync jobs.
This endpoint always returns HTTP 200 — connectivity failures are reported in the data.success flag, not via HTTP status.
Path parameters:
integrationInstance(int, required) — The ID of the TemuIntegrationInstance to test.
Response data:
success(bool) —truewhen the token is valid and Temu responded;falseotherwise.message(string) — Human-readable description of the outcome (e.g.Connection successful,Integration instance is not authenticated,Connection test failed: <upstream-error>).
Authentication: Bearer token (Sanctum).
Request
Responses
- 200
- 401
- 403
- 404
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.