Skip to main content
The Phonovation SMS API v2 uses OAuth 2.0 password grant to issue short-lived JWT access tokens. Every API request must include a valid token in the Authorization header.

Step 1: Obtain a token

Send a POST request to the auth server with your credentials:
Successful response:
Token response
Access tokens expire after 120 seconds. Refresh tokens expire after 1200 seconds. Build token refresh logic into your integration.

Step 2: Use the token

Pass the access_token as a Bearer token in all API requests:

Token expiry & refresh strategy

Because tokens are short-lived, the recommended approach is to re-authenticate before each request or implement proactive refresh. The safest pattern is to catch a 401 Unauthorized response and immediately re-authenticate with your credentials before retrying the request.
Never hardcode credentials in your source code. Use environment variables or a secrets manager.

No sandbox environment

There is currently no sandbox or test environment. All API calls run against the live production system and will consume message credits. Test with a small number of your own numbers to verify your integration before going live.

Credentials

Your username and password are available from your Phonovation account. Contact support@phonovation.com if you need access.
Last modified on July 16, 2026