1. Pushwoosh Application Code (pushwoosh_app_id)
- Format:
XXXXX-XXXXX. - Log in to the Pushwoosh Control Panel and open your project — the Application Code is shown right below the application name. It is also the last path segment of the project URL.
2. Pushwoosh API Access token (pushwoosh_api_token)
- API tokens belong to the account, not to an individual project: go to Settings → API Access in the Control Panel.
- Pick the right type. A Device token is used by the SDKs and all Device API methods (
registerDevice,setTags,postEvent,registerEmail…); a Server token is used for every other API method. - Make sure the token has access to the project you are integrating: open the token's ⋮ menu → Edit token and select the projects, or use Grant access to all projects. A token without access to the project returns
401 Unauthorized.
3. FCM credentials — a Sender ID is normally not needed
- Pushwoosh configures Android with an FCM v1 service-account JSON. In Firebase go to Project settings → Service accounts → Generate new private key, then in Pushwoosh open Settings → Configure platforms, click Connect in the Android row and upload the file under IMPORT FCM SERVICE ACCOUNT KEY. Also make sure the FCM send API is enabled for the Google Cloud project.
- The legacy FCM Server Key / Sender ID pairing was discontinued by Google in June 2024. The current Android SDK reads the project identifiers from
google-services.json, so you do not enter a Sender ID in Pushwoosh. - If a legacy integration still asks for one, the Sender ID is in the Firebase Console under Project settings → Cloud Messaging → Project credentials.
Comments
0 comments
Please sign in to leave a comment.