Skip to main content
POST
Verify my current contact

Path Parameters

contactChangeId
string
required

The unique, opaque system identifier for a resource. This case-sensitive ID is also used as path parameters in URLs or in other properties or parameters that reference a resource by ID rather than URL.

Body

application/json

The properties required to verify the current contact destination and start verification of the new one.

currentCode
string
required

The one-time passcode delivered to the current contact destination.

Required string length: 6
Pattern: ^[0-9]{6}$
emailAddress
string<email>

The new email address. Required when changing email and omitted when changing phone.

Required string length: 6 - 255
Pattern: ^[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}$
phoneNumber
string<phone>

The new phone number. Required when changing phone and omitted when changing email.

Required string length: 6 - 20
Pattern: ^\+?[0-9]{1,3}?[ -]?\(?[0-9]{1,4}?\)?[ -]?[0-9]{1,4}?[ -]?[0-9]{1,4}?[ -]?[0-9]{1,9}$

Response

Ok. The operation succeeded.

A customer contact change awaiting verification.

id
string
required

The unique identifier of the customer contact change.

type
enum<string>
required

The contact destination being changed.

Available options:
email,
phone
currentChallenge
object
required

The challenge delivered to the customer's current contact destination.

expiresAt
string<date-time>
required

The expiration date-time for the contact change, in [RFC 3339] date-time YYYY-MM-DDThh:mm:ss.sssZ format, UTC.

newChallenge
object

The challenge delivered to the customer's new contact destination after the current destination verifies.