get
https://partner.gupshup.io/partner//app-link/partner-link-token
Read-only fetch of the partner's linking-token metadata . Never generates, regenerates, or returns the JWT value.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
API Request:
curl --location --request GET 'https://partner.gupshup.io/partner/{{PARTNER_ID}}/app-link/partner-link-token' \
--header 'token: {{PARTNER_TOKEN}}'Response:
| Status Code | Response | Comments |
|---|---|---|
| 200 | { "partnerId": 8814, "generated": true, "status": "ACTIVE", "issuedAt": 1783053048000, "expiresAt": 1785645048000, "issuedByEmail": "[email protected]" } | Token row exists. status is ACTIVE or EXPIRED. |
| 200 | { "partnerId": 8814, "generated": false, "status": null, "issuedAt": null, "expiresAt": null, "issuedByEmail": null } | No linking-token row exists yet. |
| 401 | { "status": "error", "message": "Unauthorised access to the resource. Please review request parameters and headers and retry" } | Missing/invalid authentication. |
| 403 | { "status": "error", "message": "Forbidden Access" } | Path partnerId mismatch or not PARTNER_ADMIN. |
| 429 | { "status": "error", "message": "Too Many Requests" } | More than 30 requests / 60 seconds. |
| 500 | { "status": "error", "message": "Internal server error. Please try again later and If Issue still persist then contact Gupshup Dev Support" } | Unexpected server failure. |
Request Parameters:
| Key | Description | Values | Data Type | Required / Optional | Constraints |
|---|---|---|---|---|---|
| token | Partner token credential | {{PARTNER_TOKEN}} | String | Required | See §1 auth types. |
| partnerId | Partner ID (path) | e.g. 8814 | Integer | Required | Must match authenticated partner context. |
