Test Push Notification Online – Verify and Preview Messages

Send a real push notification to one or more device tokens through Firebase Cloud Messaging, and see exactly what FCM says back about each one.

1 · Firebase project

Get one with gcloud auth print-access-token. It lasts about an hour.

2 · Devices

Each is sent separately, so one bad token cannot mask a good one.

3 · Message

Your project ID, access token and device tokens are sent from your browser straight to Google. They never reach a2z.tools, and nothing is stored.

    0Accepted
    0Rejected

    This uses the FCM HTTP v1 API. The old server key (Authorization: key=...) and the fcm.googleapis.com/fcm/send endpoint were shut down by Google in June 2024 and no longer work anywhere.

    Related Tools

    More tools in the same category

    Other Tools

    Popular tools from across A2Z



    About our Push Notification Tester

    The Push Notification Tester sends a real notification through Firebase Cloud Messaging (FCM) to the device tokens you enter, so you can check that your app receives it and see exactly what FCM says back about each token. It uses the FCM HTTP v1 API. The legacy server key and the fcm/send endpoint were shut down by Google in June 2024 and no longer work.

    Android, iOS and web apps that use the Firebase SDK all receive FCM messages through a device registration token, so the same test works for each of them. On iOS, FCM delivers through Apple's push service (APNs), which needs your APNs key uploaded to the Firebase project.

    How to use the Push Notification Tester

    • Enter your Firebase project ID.
    • Paste an OAuth2 access token. Running gcloud auth print-access-token gives one; it lasts about an hour.
    • Paste one or more device tokens, one per line or comma separated.
    • Add an optional title and the message, then click "Send notification".

    Each token is sent separately and gets its own result, so one bad token cannot hide a good one. Your project ID, access token and device tokens go from your browser straight to Google; they never reach a2z.tools and nothing is stored.

    Your computer has a secret life. New comedy every day: Inside Your Computer by A2Z Tools. Watch free.

    Rate this tool

    Was this tool useful? Your feedback helps us improve it.

    No ratings yet — be the first to rate this tool.
    Your rating (required)
    0 / 2000

    Please do not include passwords, payment details or other sensitive information.

    Your feedback is sent privately to the A2Z.Tools team and will not be posted publicly.

    Push notification tester - Other Tools on a2z.tools

    Quick answer

    Enter your Firebase project ID, a short-lived OAuth2 access token (for example from gcloud auth print-access-token), one or more device tokens and a message; the tool sends each token a real notification through the FCM HTTP v1 API and reports what Google returned.

    Key facts

    • Uses the FCM HTTP v1 API (https://fcm.googleapis.com/v1/projects/PROJECT_ID/messages:send)
    • Authenticates with a short-lived OAuth2 access token, not the legacy server key Google shut down in June 2024
    • Sends each device token separately, so one bad token cannot hide a good one
    • Your project ID, access token and device tokens go from your browser straight to Google and are never sent to or stored by A2Z Tools
    • Free to use, no signup required

    What is this tool?

    This tool lets developers send a real test push notification through Firebase Cloud Messaging using the HTTP v1 API, their own project ID and access token, and one or more device tokens, and see exactly what FCM says back about each token.

    How to use it

    Enter your Firebase project ID and an OAuth2 access token, paste one or more device tokens, write an optional title and the message, then click Send notification. Each token gets its own result.
    1. Enter your Firebase project ID.
    2. Paste an OAuth2 access token for the project (gcloud auth print-access-token gives one; it lasts about an hour).
    3. Paste one or more device registration tokens, one per line or comma separated.
    4. Add an optional title and the message body.
    5. Click Send notification and read the accepted or rejected result for each token.

    Example

    Example: with project ID my-app-123, a token from gcloud auth print-access-token and two device tokens, sending the message "Hello from A2Z Tools" shows one row per token: Accepted by FCM, or the reason Google rejected it.

    How it works

    For each device token the page sends an HTTPS POST from your browser to https://fcm.googleapis.com/v1/projects/PROJECT_ID/messages:send, with an Authorization: Bearer header carrying your access token and a JSON body of the form {"message":{"token":"...","notification":{"title":"...","body":"..."}}}. The response status and Google's error details are shown per token. A2Z Tools' server is not involved in the request.

    Common use cases

    • Testing push notification delivery during mobile or web app development.
    • Verifying that a device token is valid and receiving notifications.
    • Debugging notification formatting before deploying to production.
    • Quickly sending a one-off test notification without writing code.

    Benefits

    Free, direct, and lets developers test real FCM delivery without writing a backend script.

    Limitations

    You need your own Firebase project, an access token and device tokens; the tool does not create them. Access tokens expire after about an hour. It sends a notification message (title and body) to device tokens only; it does not send data-only messages, platform-specific overrides, topics or condition targets. It does not accept the legacy FCM server key, which Google switched off in June 2024.

    Privacy & your data

    Your project ID, access token and device tokens are sent from your browser directly to Google's FCM API, the token as the request's Authorization header. They are not sent to, logged or stored by A2Z Tools. The access token field is masked on screen.

    Frequently asked questions

    Do I need my own Firebase project to use this?
    Yes. You need your Firebase project ID, an OAuth2 access token for that project and a device token from your app. The tool does not create or provide any of these.
    Is my access token sent to A2Z Tools' server?
    No. The access token, project ID and device tokens go from your browser directly to Google's FCM API. They are not sent to or stored on the A2Z Tools server.
    Why did my notification fail to send?
    The result row shows Google's reason. A 401 or 403 usually means the access token has expired (they last about an hour) or lacks permission for the project; a 404 usually means a wrong project ID or a device token from another project; a 400 is usually a malformed device token.
    Is this tool free to use?
    Yes, it's free with no signup required.
    Can I still use my FCM server key?
    No. Google shut down the legacy FCM API and its server keys in June 2024, so requests to fcm.googleapis.com/fcm/send no longer work. This tool uses the HTTP v1 API, which needs a short-lived OAuth2 access token instead; gcloud auth print-access-token is the quickest way to get one for testing.

    Related tools

    Last reviewed:

    Advertisement