Refresh access token

Developing

POST

/customer/v2/auth/refresh

Extends your active session by issuing a brand-new access token in exchange for your current valid token, removing the need to re-transmit confidential primary credentials.

Important Notes

The newly generated token resets the lifecycle back to a full 24-hour lifetime boundary (expires_in: 86400).

Always cache and swap the old token out immediately across your integrations to prevent sudden 401 authorization rejections.

Request

Header Params

Responses

🟢201Success

application/json

Bodyapplication/json

🟠401Unauthorized

Request Example

Shell

JavaScript

Java

Swift

curl --location --request POST 'https://prod.your-api-server.com/customer/v2/auth/refresh' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {{token}}'

Response Example

201 - 201 Created

{
    "data": {
        "token_type": "Bearer",
        "expires_in": 86400,
        "access_token": "<access-token>"
    },
    "meta": {
        "message": "Token refreshed successfully"
    }
}

Modified at 2026-06-23 14:23:15

Get token information

Request access token

Refresh access token

Important Notes#

Request

Responses

Important Notes