1. Service account

Drop service-account.json here, or click to browse.

Sent once per request to sign a short-lived OAuth token, then discarded. Never written to disk, a database, or logs. See the security note below.

Don't have this file? Here's where to get it

Every Firebase project has one of these — download it from the console for the project you want to send test pushes for:

  1. Open the Firebase console and pick your project.
  2. Gear icon next to Project Overview → Project settings.
  3. Open the Service accounts tab.
  4. Leave Firebase Admin SDK selected, click Generate new private key.
  5. Confirm — a .json file downloads. That's the file to drop above.

Only a Google Cloud project (no Firebase)? Use IAM & Admin → Service Accounts in the Cloud console instead, with the Firebase Cloud Messaging API Admin role.

Treat it like a password — it grants permission to send pushes as that project.

2. Device tokens

0 tokens

3. Notification payload

Data payload (key/value — all values sent as strings)

Full control over the FCM v1 message object (minus token, which is injected per recipient). This is independent of the Simple tab — only what you type here is sent when this tab is active. FCM's data payload only accepts string values — a list goes in as a JSON-stringified string, e.g. "tags": "[\"sale\",\"urgent\"]".