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

MagicBell channel/mobile_push API

The channel/mobile_push API from MagicBell — 6 operation(s) for channel/mobile_push.

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

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

This API exposes 12 operations across 6 paths, and defines 10 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.

12 operations 6 paths 10 schemas 6 DELETE3 GET3 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
Resource Areas
1

Paths & Operations 12

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

channel/mobile_push 12
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/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

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are FCMConfig (11 properties), APNSConfig (6 properties), ExpoConfigObject (3 properties), Links (3 properties). Each schema is shown below with its type and property counts.

APNSConfig
object
6 properties 5 required
ArrayOfAPNSConfigObjects
object
2 properties
ArrayOfExpoConfigObjects
object
2 properties
ExpoConfig
object
1 property 1 required
FCMConfig
object
11 properties 11 required
FCMConfigObject
object
3 properties 3 required
ExpoConfigObject
object
3 properties 3 required
APNSConfigObject
object
3 properties 3 required
Links
object
3 properties
ArrayOfFCMConfigObjects
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

magicbell-channel-mobile-push-api-openapi.yml Raw ↑

Other APIs MagicBell publishes across the network.

MagicBell REST API v1
MagicBell apns API
MagicBell awssns API
MagicBell broadcasts API
MagicBell channel/email API
MagicBell channel/slack API
MagicBell channel/sms API
MagicBell channel/web_push API
MagicBell channels API
MagicBell expo API
MagicBell fcm API
MagicBell github API
Where this information came from

This is an independent, third-party profile of MagicBell channel/mobile_push 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.