magicbell-api

name	magicbell-api
description	MagicBell API skill. Use when working with MagicBell for broadcasts, channels, events. Covers 126 endpoints.
version	1.0.0
generator	lapsh

MagicBell API

API version: 2.0.0

Auth

Requires API key (key parameter)

Base URL

https://api.magicbell.com/v2

Setup

1. Include your API key via the key parameter
2. GET /broadcasts -- verify access
3. POST /broadcasts -- create first broadcasts

Endpoints

126 endpoints across 6 groups. See references/api-spec.lap for full details.

broadcasts

Method	Path	Description
GET	/broadcasts	Retrieves a paginated list of broadcasts for the project. Returns basic information about each broadcast including its creation time and status.
POST	/broadcasts	Creates a new broadcast message. When a broadcast is created, it generates individual notifications for relevant users within the project. Only administrators can create broadcasts.
GET	/broadcasts/{broadcast_id}	Retrieves detailed information about a specific broadcast by its ID. Includes the broadcast's configuration and current status.

channels

Method	Path	Description
GET	/channels/deliveryconfig
PUT	/channels/deliveryconfig
GET	/channels/mobile_push/apns/tokens	Lists all mobile_push tokens belonging to the authenticated user. Returns a paginated list of tokens, including their status, creation dates, and associated metadata.
POST	/channels/mobile_push/apns/tokens	Saves a mobile_push 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 direct communication with the user via the channel.
DELETE	/channels/mobile_push/apns/tokens/{token_id}	Revokes one of the authenticated user's mobile_push tokens. This permanently invalidates the specified token, preventing it from being used for future channel access. This action cannot be undone. Users can only revoke their own tokens.
GET	/channels/mobile_push/apns/tokens/{token_id}	Retrieves details of a specific mobile_push token belonging to the authenticated user. Returns information about the token's status, creation date, and any associated metadata. Users can only access their own tokens.
GET	/channels/mobile_push/expo/tokens	Lists all mobile_push tokens belonging to the authenticated user. Returns a paginated list of tokens, including their status, creation dates, and associated metadata.
POST	/channels/mobile_push/expo/tokens	Saves a mobile_push 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 direct communication with the user via the channel.
DELETE	/channels/mobile_push/expo/tokens/{token_id}	Revokes one of the authenticated user's mobile_push tokens. This permanently invalidates the specified token, preventing it from being used for future channel access. This action cannot be undone. Users can only revoke their own tokens.
GET	/channels/mobile_push/expo/tokens/{token_id}	Retrieves details of a specific mobile_push token belonging to the authenticated user. Returns information about the token's status, creation date, and any associated metadata. Users can only access their own tokens.
GET	/channels/mobile_push/fcm/tokens	Lists all mobile_push tokens belonging to the authenticated user. Returns a paginated list of tokens, including their status, creation dates, and associated metadata.

events

Method	Path	Description
GET	/events	Retrieves a paginated list of events for the project.

integrations

Method	Path	Description
GET	/integrations	List Integrations
DELETE	/integrations/apns	Removes a apns integration configuration from the project. This will disable the integration's functionality within the project.
GET	/integrations/apns	Retrieves the current apns integration configurations for a specific integration type in the project. Returns configuration details and status information.
PUT	/integrations/apns	Creates or updates a apns integration for the project. Only administrators can configure integrations.
DELETE	/integrations/apns/{id}	Removes a specific apns integration instance by ID from the project.
DELETE	/integrations/awssns	Removes a awssns integration configuration from the project. This will disable the integration's functionality within the project.
GET	/integrations/awssns	Retrieves the current awssns integration configurations for a specific integration type in the project. Returns configuration details and status information.
PUT	/integrations/awssns	Creates or updates a awssns integration for the project. Only administrators can configure integrations.
POST	/integrations/awssns/webhooks/incoming/{id}	Receives and processes incoming webhook events from the awssns integration. Each integration can define its own webhook payload format and handling logic.
DELETE	/integrations/awssns/{id}	Removes a specific awssns integration instance by ID from the project.
DELETE	/integrations/expo	Removes a expo integration configuration from the project. This will disable the integration's functionality within the project.
GET	/integrations/expo	Retrieves the current expo integration configurations for a specific integration type in the project. Returns configuration details and status information.
PUT	/integrations/expo	Creates or updates a expo integration for the project. Only administrators can configure integrations.
DELETE	/integrations/expo/{id}	Removes a specific expo integration instance by ID from the project.
DELETE	/integrations/fcm

jwt

Method	Path	Description
GET	/jwt/project	Retrieves a list of all active project-level JWT tokens. Returns a paginated list showing token metadata including creation date, last used date, and expiration time. For security reasons, the actual token values are not included in the response.
POST	/jwt/project	Creates a new project-level JWT token. These tokens provide project-wide access and should be carefully managed. Only administrators can create project tokens. The returned token should be securely stored as it cannot be retrieved again after creation.
DELETE	/jwt/project/{token_id}	Immediately revokes a project-level JWT token. Once revoked, any requests using this token will be rejected. This action is immediate and cannot be undone. Active sessions using this token will be terminated.
POST	/jwt/user	Issues a new user-specific JWT token. These tokens are scoped to individual user permissions and access levels. Only administrators can create user tokens. The token is returned only once at creation time and cannot be retrieved later.
DELETE	/jwt/user/{token_id}	Revokes a specific user's JWT token. This immediately invalidates the token and terminates any active sessions using it. This action cannot be undone. Administrators should use this to revoke access when needed for security purposes.
GET	/jwt/user/{user_id}	Lists all JWT tokens associated with a specific user. Returns token metadata including creation time, last access time, and expiration date. Administrators can use this to audit user token usage and manage active sessions. Token values are not included in the response for security reasons.

users

Method	Path	Description
GET	/users/{user_id}/channels/mobile_push/apns/tokens	Lists all mobile_push 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.
DELETE	/users/{user_id}/channels/mobile_push/apns/tokens/{token_id}	Revokes a specific user's mobile_push token. This endpoint is available to project administrators and permanently invalidates the specified token. Once revoked, the token can no longer be used to access channel features. This action cannot be undone.
GET	/users/{user_id}/channels/mobile_push/apns/tokens/{token_id}	Retrieves a specific mobile_push 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 including its status, creation date, and associated metadata.
GET	/users/{user_id}/channels/mobile_push/expo/tokens	Lists all mobile_push 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.
DELETE	/users/{user_id}/channels/mobile_push/expo/tokens/{token_id}	Revokes a specific user's mobile_push token. This endpoint is available to project administrators and permanently invalidates the specified token. Once revoked, the token can no longer be used to access channel features. This action cannot be undone.
GET	/users/{user_id}/channels/mobile_push/expo/tokens/{token_id}	Retrieves a specific mobile_push 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 including its status, creation date, and associated metadata.
GET	/users/{user_id}/channels/mobile_push/fcm/tokens	Lists all mobile_push 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.
DELETE	/users/{user_id}/channels/mobile_push/fcm/tokens/{token_id}	Revokes a specific user's mobile_push token. This endpoint is available to project administrators and permanently invalidates the specified token. Once revoked, the token can no longer be used to access channel features. This action cannot be undone.
GET	/users/{user_id}/channels/mobile_push/fcm/tokens/{token_id}

Common Questions

Match user requests to endpoints in references/api-spec.lap. Key patterns:

• "List all broadcasts?" -> GET /broadcasts
• "Create a broadcast?" -> POST /broadcasts
• "Get broadcast details?" -> GET /broadcasts/{broadcast_id}
• "List all deliveryconfig?" -> GET /channels/deliveryconfig
• "List all tokens?" -> GET /channels/mobile_push/apns/tokens
• "Create a token?" -> POST /channels/mobile_push/apns/tokens
• "Delete a token?" -> DELETE /channels/mobile_push/apns/tokens/{token_id}
• "Get token details?" -> GET /channels/mobile_push/apns/tokens/{token_id}
• "List all tokens?" -> GET /channels/mobile_push/expo/tokens
• "Create a token?" -> POST /channels/mobile_push/expo/tokens
• "Delete a token?" -> DELETE /channels/mobile_push/expo/tokens/{token_id}
• "Get token details?" -> GET /channels/mobile_push/expo/tokens/{token_id}
• "List all tokens?" -> GET /channels/mobile_push/fcm/tokens
• "Create a token?" -> POST /channels/mobile_push/fcm/tokens
• "Delete a token?" -> DELETE /channels/mobile_push/fcm/tokens/{token_id}
• "Get token details?" -> GET /channels/mobile_push/fcm/tokens/{token_id}
• "List all tokens?" -> GET /channels/slack/tokens
• "Create a token?" -> POST /channels/slack/tokens
• "Delete a token?" -> DELETE /channels/slack/tokens/{token_id}
• "Get token details?" -> GET /channels/slack/tokens/{token_id}
• "List all tokens?" -> GET /channels/teams/tokens
• "Create a token?" -> POST /channels/teams/tokens
• "Delete a token?" -> DELETE /channels/teams/tokens/{token_id}
• "Get token details?" -> GET /channels/teams/tokens/{token_id}
• "List all tokens?" -> GET /channels/web_push/tokens
• "Create a token?" -> POST /channels/web_push/tokens
• "Delete a token?" -> DELETE /channels/web_push/tokens/{token_id}
• "Get token details?" -> GET /channels/web_push/tokens/{token_id}
• "List all events?" -> GET /events
• "List all integrations?" -> GET /integrations
• "List all apns?" -> GET /integrations/apns
• "Delete a apn?" -> DELETE /integrations/apns/{id}
• "List all awssns?" -> GET /integrations/awssns
• "Delete a awssn?" -> DELETE /integrations/awssns/{id}
• "List all expo?" -> GET /integrations/expo
• "Delete a expo?" -> DELETE /integrations/expo/{id}
• "List all fcm?" -> GET /integrations/fcm
• "Delete a fcm?" -> DELETE /integrations/fcm/{id}
• "List all github?" -> GET /integrations/github
• "Delete a github?" -> DELETE /integrations/github/{id}
• "List all inbox?" -> GET /integrations/inbox

Response Tips

• Check response schemas in references/api-spec.lap for field details
• Create/update endpoints typically return the created/updated object

References

• Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas

Generated from the official API spec by LAP