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 integrations API

The integrations API from MagicBell — 42 operation(s) for integrations.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 72 operations across 42 paths, and defines 59 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.

72 operations 42 paths 59 schemas 30 DELETE16 GET11 POST15 PUT

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 72

Across 42 paths, the API surfaces 72 operations — 30 DELETE, 16 GET, 11 POST, 15 PUT. Each is listed below with its method, path, parameters, and response codes.

integrations 72
GET
/integrations
List Integrations
list_integrations 3 params → 200
DELETE
/integrations/apns
Removes a apns integration configuration from the project. This will disable the integration's functionality within the project.
delete_apns_integration → 204
GET
/integrations/apns
Retrieves the current apns integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_apns_integration → 200
PUT
/integrations/apns
Creates or updates a apns integration for the project. Only administrators can configure integrations.
save_apns_integration body → 200
DELETE
/integrations/apns/{id}
Removes a specific apns integration instance by ID from the project.
delete_apns_integration_by_id 1 param → 204
DELETE
/integrations/awssns
Removes a awssns integration configuration from the project. This will disable the integration's functionality within the project.
delete_awssns_integration → 204
GET
/integrations/awssns
Retrieves the current awssns integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_awssns_integration → 200
PUT
/integrations/awssns
Creates or updates a awssns integration for the project. Only administrators can configure integrations.
save_awssns_integration body → 200
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.
handle_awssns_webhook 1 param body → 201
DELETE
/integrations/awssns/{id}
Removes a specific awssns integration instance by ID from the project.
delete_awssns_integration_by_id 1 param → 204
DELETE
/integrations/expo
Removes a expo integration configuration from the project. This will disable the integration's functionality within the project.
delete_expo_integration → 204
GET
/integrations/expo
Retrieves the current expo integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_expo_integration → 200
PUT
/integrations/expo
Creates or updates a expo integration for the project. Only administrators can configure integrations.
save_expo_integration body → 200
DELETE
/integrations/expo/{id}
Removes a specific expo integration instance by ID from the project.
delete_expo_integration_by_id 1 param → 204
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_integration body → 200
DELETE
/integrations/fcm/{id}
Removes a specific fcm integration instance by ID from the project.
delete_fcm_integration_by_id 1 param → 204
DELETE
/integrations/github
Removes a github integration configuration from the project. This will disable the integration's functionality within the project.
delete_github_integration → 204
GET
/integrations/github
Retrieves the current github integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_github_integration → 200
PUT
/integrations/github
Creates or updates a github integration for the project. Only administrators can configure integrations.
save_github_integration body → 200
POST
/integrations/github/webhooks/incoming/{id}
Receives and processes incoming webhook events from the github integration. Each integration can define its own webhook payload format and handling logic.
handle_github_webhook 1 param body → 201
DELETE
/integrations/github/{id}
Removes a specific github integration instance by ID from the project.
delete_github_integration_by_id 1 param → 204
DELETE
/integrations/inbox
Removes a inbox integration configuration from the project. This will disable the integration's functionality within the project.
delete_inbox_integration → 204
GET
/integrations/inbox
Retrieves the current inbox integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_inbox_integration → 200
PUT
/integrations/inbox
Creates or updates a inbox integration for the project. Only administrators can configure integrations.
save_inbox_integration body → 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
DELETE
/integrations/inbox/{id}
Removes a specific inbox integration instance by ID from the project.
delete_inbox_integration_by_id 1 param → 204
DELETE
/integrations/mailgun
Removes a mailgun integration configuration from the project. This will disable the integration's functionality within the project.
delete_mailgun_integration → 204
GET
/integrations/mailgun
Retrieves the current mailgun integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_mailgun_integration → 200
PUT
/integrations/mailgun
Creates or updates a mailgun integration for the project. Only administrators can configure integrations.
save_mailgun_integration body → 200
DELETE
/integrations/mailgun/{id}
Removes a specific mailgun integration instance by ID from the project.
delete_mailgun_integration_by_id 1 param → 204
DELETE
/integrations/ping_email
Removes a pingemail integration configuration from the project. This will disable the integration's functionality within the project.
delete_ping_email_integration → 204
GET
/integrations/ping_email
Retrieves the current pingemail integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_ping_email_integration → 200
PUT
/integrations/ping_email
Creates or updates a pingemail integration for the project. Only administrators can configure integrations.
save_ping_email_integration body → 200
DELETE
/integrations/ping_email/{id}
Removes a specific pingemail integration instance by ID from the project.
delete_ping_email_integration_by_id 1 param → 204
DELETE
/integrations/sendgrid
Removes a sendgrid integration configuration from the project. This will disable the integration's functionality within the project.
delete_sendgrid_integration → 204
GET
/integrations/sendgrid
Retrieves the current sendgrid integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_sendgrid_integration → 200
PUT
/integrations/sendgrid
Creates or updates a sendgrid integration for the project. Only administrators can configure integrations.
save_sendgrid_integration body → 200
DELETE
/integrations/sendgrid/{id}
Removes a specific sendgrid integration instance by ID from the project.
delete_sendgrid_integration_by_id 1 param → 204
DELETE
/integrations/ses
Removes a ses integration configuration from the project. This will disable the integration's functionality within the project.
delete_ses_integration → 204
GET
/integrations/ses
Retrieves the current ses integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_ses_integration → 200
PUT
/integrations/ses
Creates or updates a ses integration for the project. Only administrators can configure integrations.
save_ses_integration body → 200
DELETE
/integrations/ses/{id}
Removes a specific ses integration instance by ID from the project.
delete_ses_integration_by_id 1 param → 204
DELETE
/integrations/slack
Removes a slack integration configuration from the project. This will disable the integration's functionality within the project.
delete_slack_integration → 204
GET
/integrations/slack
Retrieves the current slack integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_slack_integration → 200
PUT
/integrations/slack
Creates or updates a slack integration for the project. Only administrators can configure integrations.
save_slack_integration body → 200
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
DELETE
/integrations/slack/{id}
Removes a specific slack integration instance by ID from the project.
delete_slack_integration_by_id 1 param → 204
DELETE
/integrations/stripe
Removes a stripe integration configuration from the project. This will disable the integration's functionality within the project.
delete_stripe_integration → 204
GET
/integrations/stripe
Retrieves the current stripe integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_stripe_integration → 200
PUT
/integrations/stripe
Creates or updates a stripe integration for the project. Only administrators can configure integrations.
save_stripe_integration body → 200
POST
/integrations/stripe/webhooks/incoming/{id}
Receives and processes incoming webhook events from the stripe integration. Each integration can define its own webhook payload format and handling logic.
handle_stripe_webhook 1 param body → 201
DELETE
/integrations/stripe/{id}
Removes a specific stripe integration instance by ID from the project.
delete_stripe_integration_by_id 1 param → 204
DELETE
/integrations/templates
Removes a templates integration configuration from the project. This will disable the integration's functionality within the project.
delete_templates_integration → 204
GET
/integrations/templates
Retrieves the current templates integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_templates_integration → 200
PUT
/integrations/templates
Creates or updates a templates integration for the project. Only administrators can configure integrations.
save_templates_integration body → 200
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
DELETE
/integrations/templates/{id}
Removes a specific templates integration instance by ID from the project.
delete_templates_integration_by_id 1 param → 204
DELETE
/integrations/twilio
Removes a twilio integration configuration from the project. This will disable the integration's functionality within the project.
delete_twilio_integration → 204
GET
/integrations/twilio
Retrieves the current twilio integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_twilio_integration → 200
PUT
/integrations/twilio
Creates or updates a twilio integration for the project. Only administrators can configure integrations.
save_twilio_integration body → 200
DELETE
/integrations/twilio/{id}
Removes a specific twilio integration instance by ID from the project.
delete_twilio_integration_by_id 1 param → 204
DELETE
/integrations/web_push
Removes a webpush integration configuration from the project. This will disable the integration's functionality within the project.
delete_web_push_integration → 204
GET
/integrations/web_push
Retrieves the current webpush integration configurations for a specific integration type in the project. Returns configuration details and status information.
get_web_push_integration → 200
PUT
/integrations/web_push
Creates or updates a webpush integration for the project. Only administrators can configure integrations.
save_web_push_integration body → 200
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
DELETE
/integrations/web_push/{id}
Removes a specific webpush integration instance by ID from the project.
delete_web_push_integration_by_id 1 param → 204

Schemas 59

The contract defines 59 schemas that model the data the API accepts and returns. The most detailed are SlackInstallation (13 properties), FCMConfig (11 properties), APNSConfig (6 properties), TwilioConfig (5 properties). Each schema is shown below with its type and property counts.

IntegrationObject
object
3 properties 3 required
InboxConfig
object
3 properties 3 required
StripeConfig
object
1 property 1 required
ArrayOfTemplatesConfigObjects
object
2 properties
SlackStartInstallResponseContent
object
3 properties
TemplatesInstallation
object
3 properties 2 required
ExpoConfig
object
1 property 1 required
PingConfigObject
object
3 properties 3 required
FCMConfigObject
object
3 properties 3 required
GithubWebhookEvent
object
3 properties
AWSSNSConfig
object
1 property 1 required
APNSConfigObject
object
3 properties 3 required
SlackConfigObject
object
3 properties 3 required
SendgridConfigObject
object
3 properties 3 required
ArrayOfSendgridConfigObjects
object
2 properties
ArrayOfTwilioConfigObjects
object
2 properties
SlackFinishInstallResponse
object
3 properties 2 required
TwilioConfigObject
object
3 properties 3 required
ArrayOfInboxConfigObjects
object
2 properties
TemplatesConfigObject
object
3 properties 3 required
SlackConfig
object
4 properties 4 required
Integration
object
PingConfig
object
1 property 1 required
AWSSNSConfigObject
object
3 properties 3 required
ArrayOfSESConfigObjects
object
2 properties
ArrayOfStripeConfigObjects
object
2 properties
ArrayOfMailgunConfigObjects
object
2 properties
MailgunConfigObject
object
3 properties 3 required
SendgridConfig
object
3 properties 1 required
WebpushConfig
object
2 properties 2 required
InboxConfigObject
object
3 properties 3 required
GithubConfigObject
object
3 properties 3 required
APNSConfig
object
6 properties 5 required
MailgunConfig
object
3 properties 3 required
SESConfig
object
4 properties 3 required
FCMConfig
object
11 properties 11 required
ExpoConfigObject
object
3 properties 3 required
TemplatesConfig
object
ArrayOfSlackConfigObjects
object
2 properties
ArrayOfGithubConfigObjects
object
2 properties
ArrayOfWebpushConfigObjects
object
2 properties
WebPushToken
object
2 properties 2 required
ArrayOfPingConfigObjects
object
2 properties
ArrayOfIntegrationObjects
object
2 properties
AWSSNSWebhookEvent
object
3 properties
WebPushStartInstallationResponse
object
2 properties 2 required
StripeWebhookEvent
object
2 properties 2 required
SlackStartInstall
object
4 properties 1 required
ArrayOfAPNSConfigObjects
object
2 properties
ArrayOfExpoConfigObjects
object
2 properties
WebpushConfigObject
object
3 properties 3 required
StripeConfigObject
object
3 properties 3 required
ArrayOfAWSSNSConfigObjects
object
2 properties
TwilioConfig
object
5 properties 4 required
GithubConfig
object
1 property 1 required
Links
object
3 properties
SESConfigObject
object
3 properties 3 required
SlackInstallation
object
13 properties 4 required
ArrayOfFCMConfigObjects
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

magicbell-integrations-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
#Integration
← Back to M APIs
API Details
ID
magicbell:magicbell-integrations-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-integrations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/magicbell-integrations-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 integrations 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.