---
title: "Create OBO Mobility Intent"
method: POST
path: "/{Version}/{WABA-ID}/obo_mobility_intent"
tags: ["OBO Mobility Intent"]
---

# Create OBO Mobility Intent

`POST /{Version}/{WABA-ID}/obo_mobility_intent`

## Request

- Base URL: `https://graph.facebook.com`
- URL: `https://graph.facebook.com/{Version}/{WABA-ID}/obo_mobility_intent`
- Auth: HTTP bearer

Create a new On-Behalf-Of mobility intent for a WhatsApp Business Account.
This endpoint allows authorized solution providers to initiate mobility operations
on behalf of business accounts, facilitating transfers and handovers between
different solution providers.


**Use Cases:**
- Initiate account mobility process between solution providers
- Request handover of account management
- Schedule mobility operations for future execution
- Coordinate multi-partner solution transitions


**Rate Limiting:**
Standard Graph API rate limits apply. Use appropriate retry logic with exponential backoff.


**Mobility Process:**
1. Create mobility intent with appropriate intent type
2. System validates mobility eligibility and permissions
3. Intent enters PENDING status awaiting approvals
4. Partner notifications and approval workflows are triggered
5. Upon approval, mobility operation is scheduled or executed
6. Status updates are provided throughout the process

## Path parameters

- `Version` string, required
- `WABA-ID` string, required

## Headers

- `User-Agent` string
- `Authorization` string, required

## Request body

- OBOMobilityIntentRequest: Request payload for OBO mobility intent operations
  - `solution_id` string, required: Unique identifier for the WhatsApp Business Solution
  - `intent_type` 'INITIATE_TRANSFER' | 'CONFIRM_TRANSFER' | 'CANCEL_TRANSFER' | 'REQUEST_HANDOVER' | 'APPROVE_HANDOVER' | 'REJECT_HANDOVER', required: Type of mobility intent operation
  - `target_solution_id` string: Target solution ID for mobility operations (required for transfers)
  - `mobility_reason` string: Reason for the mobility intent
  - `scheduled_execution_time` string, date-time: Scheduled time for mobility execution (ISO 8601 format)
  - `metadata` object: Additional metadata for the mobility operation

## Response `200`

Successfully created OBO mobility intent

- OBOMobilityIntentResponse: Response for OBO mobility intent operations
  - `success` boolean, required: Indicates if the mobility intent operation was successful
  - `mobility_intent_id` string, required: Unique identifier for the mobility intent request
  - `status` 'PENDING' | 'APPROVED' | 'REJECTED' | 'SCHEDULED' | 'IN_PROGRESS' | 'COMPLETED' | 'FAILED': Current status of the mobility intent
  - `estimated_completion_time` string, date-time: Estimated completion time for the mobility operation (ISO 8601 format)
  - `approval_required` boolean: Indicates if additional approval is required for the operation
  - `next_steps` string[]: List of next steps required to complete the mobility operation

## Other responses

- `400`: Bad Request - Invalid parameters or malformed request
- `401`: Unauthorized - Invalid or missing access token
- `403`: Forbidden - Insufficient permissions or access denied
- `404`: Not Found - WABA ID or Solution ID does not exist or is not accessible
- `422`: Unprocessable Entity - Request parameters are valid but cannot be processed
- `429`: Too Many Requests - Rate limit exceeded
- `500`: Internal Server Error - Unexpected server error

---

[API](https://skmtc.dev/meta/apis/whatsapp-business-messaging.md) - [All operations](https://skmtc.dev/meta/apis/whatsapp-business-messaging/llms.txt) - [OpenAPI document](https://skmtc.dev/meta/apis/whatsapp-business-messaging/revisions/5c1973265369?raw)