Browse the Help Center for platform guides or API & Developers for integration docs.
curl --request DELETE \
--url https://open.beatpass.ca/api/v1/fcm-tokens \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"token": "<string>"
}
'{
"status": "ok"
}Remove an FCM device token for the authenticated user. This endpoint currently expects the token in a JSON request body. Some HTTP clients or intermediaries may drop bodies on DELETE requests, so clients should ensure their stack preserves the payload. Keeping the token out of the URL avoids encoding and length issues with long FCM tokens.
curl --request DELETE \
--url https://open.beatpass.ca/api/v1/fcm-tokens \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"token": "<string>"
}
'{
"status": "ok"
}Documentation Index
Fetch the complete documentation index at: https://docs.beatpass.ca/llms.txt
Use this file to discover all available pages before exploring further.
API access is invite-only. Contact contact@beatpass.ca to request access. Once approved, generate tokens from Account Settings → Developers. Include as: Authorization: Bearer {token}. Tokens expire after 90 days.
FCM registration token to remove.
500FCM token removed
"ok"
Was this page helpful?