After the user successfully connects their account via the Meta Embedded Signup flow, execute the claim number process to link the verified Meta phone number to the corresponding Wabpo project workspace.
Endpoint: Claim Existing WhatsApp Number
Use this endpoint when a customer connects their WhatsApp number to the WABPO Meta app outside the standard dashboard popup (e.g., via your custom CRM, POS, or ERP interface).
This process uses a two-step verification flow:
Send OTP: Validates that the customer owns and controls the phone number.
Verify OTP: Confirms ownership and returns a projectId for managing subsequent API actions (templates, messages, groups, and reports).
Request Rules & Project Reuse Order
To prevent duplicate workspaces, WABPO evaluates incoming requests against your API key using the following priority order:
idempotencyKey Match: If this key was used before, WABPO reuses that exact project.
customerId Match: If the CRM customer ID already exists under your account, WABPO reuses their project.
Verified Phone Match: If your account has already verified this exact phone number, WABPO reuses the project.
Create New: If no matches are found, WABPO creates a new project.
⚠️ Conflict Warning (409): If the phone number is already claimed by a project belonging to another WABPO user, the API returns 409 NUMBER_ALREADY_CONNECTED. You must instruct the customer to log into their original account or contact support.
Step 1: Send OTP
Requests an verification code to be sent directly to the customer's WhatsApp number.
Required Action: Direct the customer to connect the number to the WABPO Meta app, then trigger the Retry Endpoint below.
Step 3: Retry Meta Match (If Required)
If verification returned a verified_waiting_for_meta_connection status, call this endpoint once the customer finishes their Meta app setup to refresh the connection status.
