How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
MagicBell

MagicBell user API

The user API from MagicBell — 20 operation(s) for user.

Documentation Provider Profile APIs.io OpenAPI GitHub

MagicBell user API is one of 28 APIs that MagicBell publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 32 operations across 20 paths, and defines 27 schemas. It is described by OpenAPI 3.0.3, at version 2.0.0.

Requests are made against a single base URL, https://api.magicbell.com/v2.

32 operations 20 paths 27 schemas 6 DELETE12 GET14 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0.0
Base URL
https://api.magicbell.com/v2
Contact
MagicBell
Resource Areas
1

Paths & Operations 32

Across 20 paths, the API surfaces 32 operations — 6 DELETE, 12 GET, 14 POST. Each is listed below with its method, path, parameters, and response codes.

user 32
GET
/channels/mobile_push/apns/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_apns_tokens 3 params → 200
POST
/channels/mobile_push/apns/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_apns_token body → 201
DELETE
/channels/mobile_push/apns/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_apns_token 1 param → 200
GET
/channels/mobile_push/apns/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_apns_token 1 param → 200
GET
/channels/mobile_push/expo/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_expo_tokens 3 params → 200
POST
/channels/mobile_push/expo/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_expo_token body → 201
DELETE
/channels/mobile_push/expo/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_expo_token 1 param → 200
GET
/channels/mobile_push/expo/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_expo_token 1 param → 200
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_tokens 3 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_token body → 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_token 1 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_token 1 param → 200
GET
/channels/slack/tokens
Lists all slack tokens belonging to the authenticated user. Returns a paginated list of tokens, including their status, creation dates, and associated metadata.
get_slack_tokens 3 params → 200
POST
/channels/slack/tokens
Saves a slack 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 for…
save_slack_token body → 201
DELETE
/channels/slack/tokens/{token_id}
Revokes one of the authenticated user's slack tokens. This permanently invalidates the specified token, preventing it from being used for future channel access. This action cannot be undone. Users ca…
discard_slack_token 1 param → 200
GET
/channels/slack/tokens/{token_id}
Retrieves details of a specific slack token belonging to the authenticated user. Returns information about the token's status, creation date, and any associated metadata. Users can only access their…
get_slack_token 1 param → 200
GET
/channels/teams/tokens
Lists all teams tokens belonging to the authenticated user. Returns a paginated list of tokens, including their status, creation dates, and associated metadata.
get_teams_tokens 3 params → 200
POST
/channels/teams/tokens
Saves a teams 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 for…
save_teams_token body → 201
DELETE
/channels/teams/tokens/{token_id}
Revokes one of the authenticated user's teams tokens. This permanently invalidates the specified token, preventing it from being used for future channel access. This action cannot be undone. Users ca…
discard_teams_token 1 param → 200
GET
/channels/teams/tokens/{token_id}
Retrieves details of a specific teams token belonging to the authenticated user. Returns information about the token's status, creation date, and any associated metadata. Users can only access their…
get_teams_token 1 param → 200
GET
/channels/web_push/tokens
Lists all webpush tokens belonging to the authenticated user. Returns a paginated list of tokens, including their status, creation dates, and associated metadata.
get_web_push_tokens 3 params → 200
POST
/channels/web_push/tokens
Saves a webpush 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 fo…
save_web_push_token body → 201
DELETE
/channels/web_push/tokens/{token_id}
Revokes one of the authenticated user's webpush tokens. This permanently invalidates the specified token, preventing it from being used for future channel access. This action cannot be undone. Users…
discard_web_push_token 1 param → 200
GET
/channels/web_push/tokens/{token_id}
Retrieves details of a specific webpush token belonging to the authenticated user. Returns information about the token's status, creation date, and any associated metadata. Users can only access thei…
get_web_push_token 1 param → 200
POST
/integrations/inbox/installations
Creates a new installation of a inbox integration for a user. This endpoint is used when an integration needs to be set up with user-specific credentials or configuration.
save_inbox_installation body → 201
POST
/integrations/inbox/installations/start
Initiates the installation flow for a inbox integration. This is the first step in a multi-step installation process where user authorization or external service configuration may be required.
start_inbox_installation → 201
POST
/integrations/slack/installations
Creates a new installation of a slack integration for a user. This endpoint is used when an integration needs to be set up with user-specific credentials or configuration.
save_slack_installation body → 201
POST
/integrations/slack/installations/finish
Completes the installation flow for a slack integration. This endpoint is typically called after the user has completed any required authorization steps with slack.
finish_slack_installation body → 201
POST
/integrations/slack/installations/start
Initiates the installation flow for a slack integration. This is the first step in a multi-step installation process where user authorization or external service configuration may be required.
start_slack_installation body → 201
POST
/integrations/templates/installations
Creates a new installation of a templates integration for a user. This endpoint is used when an integration needs to be set up with user-specific credentials or configuration.
save_templates_installation body → 201
POST
/integrations/web_push/installations
Creates a new installation of a webpush integration for a user. This endpoint is used when an integration needs to be set up with user-specific credentials or configuration.
save_web_push_installation body → 201
POST
/integrations/web_push/installations/start
Initiates the installation flow for a webpush integration. This is the first step in a multi-step installation process where user authorization or external service configuration may be required.
start_web_push_installation → 201

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are SlackInstallation (13 properties), APNSTokenResponse (7 properties), SlackTokenResponse (6 properties), WebPushTokenResponse (6 properties). Each schema is shown below with its type and property counts.

InboxConfig
object
3 properties 3 required
SlackStartInstallResponseContent
object
3 properties
TemplatesInstallation
object
3 properties 2 required
SlackToken
object
2 properties
ArrayOfTeamsTokenResponses
object
2 properties
ExpoTokenResponse
object
5 properties 3 required
SlackFinishInstallResponse
object
3 properties 2 required
FCMTokenResponse
object
6 properties 3 required
ArrayOfAPNSTokenResponses
object
2 properties
TeamsToken
object
1 property
ArrayOfWebPushTokenResponses
object
2 properties
FCMToken
object
2 properties 1 required
ArrayOfSlackTokenResponses
object
2 properties
TeamsTokenResponse
object
5 properties 2 required
ArrayOfFCMTokenResponses
object
2 properties
APNSTokenResponse
object
7 properties 3 required
DiscardResult
object
2 properties
ArrayOfExpoTokenResponses
object
2 properties
ExpoToken
object
1 property 1 required
WebPushToken
object
2 properties 2 required
WebPushStartInstallationResponse
object
2 properties 2 required
SlackStartInstall
object
4 properties 1 required
APNSToken
object
3 properties 1 required
Links
object
3 properties
WebPushTokenResponse
object
6 properties 4 required
SlackInstallation
object
13 properties 4 required
SlackTokenResponse
object
6 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

magicbell-user-api-openapi.yml Raw ↑

Other APIs MagicBell publishes across the network.

MagicBell REST API v1
AE Profile APIs.io
MagicBell apns API
AE Profile APIs.io
MagicBell awssns API
AE Profile APIs.io
MagicBell broadcasts API
AE Profile APIs.io
MagicBell channel/email API
AE Profile APIs.io
MagicBell channel/mobile_push API
AE Profile APIs.io
MagicBell channel/slack API
AE Profile APIs.io
MagicBell channel/sms API
AE Profile APIs.io
MagicBell channel/web_push API
AE Profile APIs.io
MagicBell channels API
AE Profile APIs.io
MagicBell expo API
AE Profile APIs.io
MagicBell fcm API
AE Profile APIs.io
#User
← Back to M APIs
API Details
ID
magicbell:magicbell-user-api
Base URL
https://api.magicbell.com/v2
Docs
https://www.magicbell.com/docs/api
Provider
MagicBell
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=magicbell-user-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/magicbell-user-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 user 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.