Skip to main content
POST
Remote pairing (connection link)

Authorizations

x-api-key
string
header
required

Your ps_ API key

Body

application/json
provider
string

Link kind (default PILOT_STATUS).

Example:

"PILOT_STATUS"

name
string

Required for PILOT_STATUS; ignored for META.

Example:

"Cliente Acme"

number
string

Required for PILOT_STATUS; ignored for META.

Example:

"5511988887777"

sendViaWhatsApp
boolean

Send the link over WhatsApp (PILOT_STATUS). Default false.

Example:

"false"

redirectUrl
string

Redirect URL after completion (META).

Example:

"https://app.acme.com/done"

externalRef
string

Optional external reference for correlation (META).

Example:

"customer-42"

Deprecated: accepted and ignored. No API key is touched and linkedApiKeyId is always null.

Example:

"true"

metaFlow
enum<string>

META only: embedded (default) runs Meta Embedded Signup on the hosted page; credentials collects an existing WABA's credentials.

Available options:
embedded,
credentials
Example:

"embedded"

settings
object

Per-number settings the number is BORN with — the same block as PATCH /v1/numbers/{id}. Applies to both providers: for META it is written on the placeholder the connection lands on. This is the moment to decide history: settings.historyImportEnabled defaults to true, the provider hands the device history over once, right after the person connects, and changing the flag afterwards cannot bring it back or undo it. Invalid values answer 400 INVALID_SETTINGS and nothing is created.

Response

Pairing link created. META answers with the placeholder numberId, the link, its expiresAt (30 min) and the settings the placeholder was created with.