Across 6 paths, the API surfaces 11 operations — 4 DELETE, 5 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
fcm 11
GET
/channels/mobile_push/fcm/tokens
Lists all mobilepush tokens belonging to the authenticated user. Returns a paginated list of tokens, including their status, creation dates, and associated metadata.
get_mobile_push_fcm_tokens3 params→ 200
POST
/channels/mobile_push/fcm/tokens
Saves a mobilepush token for the authenticated user. This token serves as a credential for accessing channel-specific functionality. Each token is unique to the user and channel combination, allowing…
save_mobile_push_fcm_tokenbody→ 201
DELETE
/channels/mobile_push/fcm/tokens/{token_id}
Revokes one of the authenticated user's mobilepush tokens. This permanently invalidates the specified token, preventing it from being used for future channel access. This action cannot be undone. Use…
discard_mobile_push_fcm_token1 param→ 200
GET
/channels/mobile_push/fcm/tokens/{token_id}
Retrieves details of a specific mobilepush token belonging to the authenticated user. Returns information about the token's status, creation date, and any associated metadata. Users can only access t…
get_mobile_push_fcm_token1 param→ 200
DELETE
/integrations/fcm
Removes a fcm integration configuration from the project. This will disable the integration's functionality within the project.
delete_fcm_integration→ 204
GET
/integrations/fcm
Retrieves the current fcm integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_fcm_integration→ 200
PUT
/integrations/fcm
Creates or updates a fcm integration for the project. Only administrators can configure integrations.
save_fcm_integrationbody→ 200
DELETE
/integrations/fcm/{id}
Removes a specific fcm integration instance by ID from the project.
delete_fcm_integration_by_id1 param→ 204
GET
/users/{user_id}/channels/mobile_push/fcm/tokens
Lists all mobilepush tokens associated with a specific user. This endpoint is available to project administrators and returns a paginated list of tokens, including both active and revoked tokens.
Revokes a specific user's mobilepush token. This endpoint is available to project administrators and permanently invalidates the specified token. Once revoked, the token can no longer be used to acce…
Retrieves a specific mobilepush token by its ID for a given user. This endpoint is available to project administrators and requires project-level authentication. Use this to inspect token details inc…
get_mobile_push_fcm_user_token2 params→ 200
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are FCMConfig (11 properties), FCMTokenResponse (6 properties), Links (3 properties), FCMConfigObject (3 properties). Each schema is shown below with its type and property counts.
FCMToken
object
2 properties1 required
FCMConfig
object
11 properties11 required
FCMConfigObject
object
3 properties3 required
ArrayOfFCMTokenResponses
object
2 properties
DiscardResult
object
2 properties
Links
object
3 properties
FCMTokenResponse
object
6 properties3 required
ArrayOfFCMConfigObjects
object
2 properties
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of MagicBell fcm API, published by
API Evangelist. We do not operate, host, resell, or
support these APIs, and we are not affiliated with or endorsed by the company unless stated above.
Everything here is built from publicly available information — the company's own site,
developer portal, documentation, public repositories, and the specifications it publishes for public use.
Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's
public API artifacts, scored against a published rubric. They are not certifications,
endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and
you do not need to justify the request. A removed company is recorded as unrated, never scored
zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy → On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.