What Are Push Tokens?
Push tokens are unique identifiers assigned by Apple Push Notification service (APNS) or Firebase Cloud Messaging (FCM) to each app installation on a device. These tokens are essential for sending targeted push notifications to mobile applications.
Types of Push Tokens
APNS (Apple Push Notification Service) iOS push tokens are 64-byte hexadecimal strings generated by Apple's servers. Each token is unique to a combination of app, device, and environment (sandbox/production).
FCM (Firebase Cloud Messaging) Android push tokens (also called registration tokens) are generated by Google's Firebase infrastructure. They typically look like long alphanumeric strings.
VoIP Push Tokens Special tokens used by iOS calling applications (like WhatsApp, Telegram) for high-priority push notifications that wake the app instantly for incoming calls.
Why Do You Need a Push Token API?
Generating push tokens at scale requires actual device interactions — you cannot simply create them programmatically. A Push Token API service like REGHelp handles the complex infrastructure:
- Real device management — maintaining pools of iOS and Android devices
- Token freshness — tokens expire and must be regularly refreshed
- High availability — sub-2-second response time with 99.9% uptime
- Bulk generation — generate hundreds of tokens per minute
How REGHelp Push Token API Works
All REGHelp API requests use the GET method with the apiKey passed as a query parameter:
Step 1 — Create a task:
GET https://api.reghelp.net/push/getToken?apiKey=YOUR_KEY&appName=tgiOS&appDevice=iOS
Response:
{
"id": "664462c0f45c5b1b760b7c3e",
"service": "tg",
"product": "push",
"price": 0.75,
"balance": 122.50,
"status": "success"
}
Step 2 — Poll for result:
GET https://api.reghelp.net/push/getStatus?apiKey=YOUR_KEY&id=664462c0f45c5b1b760b7c3e
Response (when done):
{
"id": "664462c0f45c5b1b760b7c3e",
"status": "done",
"token": "1673463060517848736:APA91b...",
"message": "OK"
}
For VoIP Push tokens, use /pushVoip/getToken with the same pattern.
Integration Best Practices
- Cache tokens — store received tokens and use them until they expire
- Handle errors — implement retry logic with exponential backoff
- Monitor usage — track your API consumption via the dashboard
- Use webhooks — add
webHookparameter to receive results via POST callback - Rate limiting — respect the API rate limits per key
Push Token Security
Push tokens should be treated as sensitive data. Never expose them in client-side code or public repositories. Always transmit tokens over HTTPS and store them encrypted at rest.
Pricing
REGHelp uses a pay-per-use model. Each successful push token generation costs a small fee debited from your balance. See our pricing page for current rates.