Authentication
Learn how to authenticate your requests to the SMS API.
The SMS API uses token-based authentication to secure API requests. All API requests must include an authentication token in the header.
API Keys
Obtain API keys from us contact us for generate API keys.
Access Tokens
Generate temporary access tokens using your API keys.
Security
Follow best practices to keep your API credentials secure.
Using Access Tokens
Include the access token in the Authorization header of all API requests:
Authorization: Bearer YOUR_ACCESS_TOKENExample Request with Authentication
curl -X GET "https://sms.747sandbox.com/api/v1/message/custom" \
-H "Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..." \
-H "Content-Type: application/json"Security Best Practices
- Never share your API keys or access tokens
- Store API keys and tokens securely, never in client-side code
- Use environment variables to store API keys in your applications
- Implement proper error handling for authentication failures
- Monitor API usage for suspicious activity
Warning
If you suspect your API keys have been compromised, contact us for regenerate them immediately.
Error Handling
Common authentication errors you might encounter:
| Status Code | Error | Description |
|---|---|---|
| 401 | Unauthorized | Invalid or missing authentication token |
| 403 | Forbidden | Valid token but insufficient permissions |
| 400 | Bad Request | Invalid API key or secret format |