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

WhatsApp OBO Mobility Intent API

APIs for managing On-Behalf-Of mobility intent operations for WhatsApp Business Accounts

WhatsApp OBO Mobility Intent API is one of 74 APIs that WhatsApp publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include OBO Mobility Intent. The published artifact set on APIs.io includes an OpenAPI specification, a GitHub repository, API documentation, and 6 JSON Schemas.

This API exposes 3 operations across 3 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version v23.0.

Requests are made against 4 base URLs: https://graph.facebook.com, https://graph.facebook.com, https://graph.facebook.com, https://graph.facebook.com.

3 operations 3 paths 22 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v23.0
Base URL
https://graph.facebook.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

WhatsApp OBO Mobility Intent API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearerAuth — System user access token with whatsappbusinessmanagement permission. Format: Bearer YOURSYSTEMUSERACCESSTOKEN

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

OBO Mobility Intent 3

APIs for managing On-Behalf-Of mobility intent operations for WhatsApp Business Accounts

GET
/{Version}/{OBO-Mobility-Intent-ID}
Get OBO Mobility Intent Details
getOBOMobilityIntent 5 params → 200400401403404429500
POST
/{Version}/{WABA-ID}/obo_mobility_intent
Create OBO Mobility Intent
createOBOMobilityIntent 4 params body → 200400401403404422429500
POST
/{Version}/{WABA-ID}/set_obo_mobility_intent
Set OBO Mobility Intent
setOBOMobilityIntent 4 params body → 200400401403404422429500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are WhatsAppBusinessAccount (17 properties), OBOMobilityIntentNode (6 properties), OBOMobilityIntentResponse (6 properties), WhatsAppBusinessSolution (6 properties). Each schema is shown below with its type and property counts.

WhatsAppBusinessAccount
object
WhatsApp Business Account details and configuration
17 properties 2 required
OBOMobilityIntentNode
object
WhatsApp Business Account OBO Mobility Intent Node
6 properties 3 required
SetOBOMobilityIntentResponse
object
Response for setting OBO mobility intent
4 properties 1 required
OnBehalfOfBusinessInfo
object
Information about the business on whose behalf the WABA operates
2 properties
BusinessVerificationStatus
string
Verification status of the connected client business
MobilityIntentType
string
Type of mobility intent operation
BusinessSchedule
object
Business hours schedule information
3 properties
SubscribedApp
object
Application subscribed to the WABA
2 properties
WhatsAppBusinessSolutionStatus
string
Current effective status of the Multi-Partner Solution
MessageTemplate
object
Message template information
3 properties
PhoneNumber
object
Phone number associated with the WABA
3 properties
ApplicationNode
object
Meta application that owns the Multi-Partner Solution
2 properties
AccountReviewStatus
string
Review status of the WhatsApp Business Account
SetOBOMobilityIntentRequest
object
Request payload for setting OBO mobility intent
5 properties 1 required
WhatsAppBusinessSolution
object
Multi-Partner Solution details and configuration
6 properties 4 required
OBOMobilityIntentResponse
object
Response for OBO mobility intent operations
6 properties 2 required
OwnershipType
string
Type of ownership for the WhatsApp Business Account
OBOMobilityIntentRequest
object
Request payload for OBO mobility intent operations
6 properties 2 required
GraphAPIError
object
Standard Graph API error response
1 property 1 required
WhatsAppBusinessAccountPermissionTask
string
Granular permission tasks for WhatsApp Business Account access
DCCConfig
object
Data and Content Control configuration
2 properties
WhatsAppBusinessSolutionPendingStatus
string
Status of any pending solution status transition requests

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

whatsapp-obo-mobility-intent-api-openapi.yml Raw ↑

Other APIs WhatsApp publishes across the network.

WhatsApp Flows API
WhatsApp On-Premises API
WhatsApp Analytics API
WhatsApp Assets API
WhatsApp Assigned Users API
WhatsApp Business Accounts API
WhatsApp Business Profile API
WhatsApp Lifecycle API
WhatsApp Media API
WhatsApp Message Templates API
WhatsApp Messages API
WhatsApp Phone Numbers API
Where this information came from

This is an independent, third-party profile of WhatsApp OBO Mobility Intent 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.