PushWaveAdministrators
Manage PushWave sites, keys, and origins
Keep subscriber and broadcast data separated by site and use the correct Public or Secret Key.
In the app→PushWave → Sites and Settings
Site isolation
Each PushWave site keeps its own Public Key, Secret Key, subscribers, broadcasts, segments, settings, and timezone. Switch the active site before reviewing or changing site-specific data.
Security settings
- Allowed origin
- Restricts site requests to an exact domain or approved wildcard subdomains.
- Public Key
- Begins with pk_ and authenticates the WordPress browser integration, configuration, subscription, prompt, and tracking endpoints.
- Secret Key
- Begins with sk_, must remain server-side, and authenticates broadcast list, create, update, delete, schedule, send, and test operations.
- Regenerate a key
- Invalidates that key immediately with no grace period. Update only the integrations that use the regenerated credential.
- Rate limit
- Controls accepted API requests per minute for the site.
- VAPID keys
- Browser push identity keys required for subscriptions and delivery.
Keep the two credentials separate
The WordPress browser integration uses the Public Key. Server-side broadcast automation uses the Secret Key. Never substitute one for the other.
Developer reference
Open the complete API reference
Review authentication, parameters, rate limits, cURL requests, and example responses.
Was this guide enough?
Contact support if your screen or result is different.