Replace Contact Data
Contacts
Replace Contact Data
Replace the stored data for a contact phone number
PUT
Replace Contact Data
Use this endpoint to store the complete state that another system should find
the next time the caller contacts you. For example, Five9 can save a
conversation ID, routing status, or handoff details against the caller’s phone
number.
The data is scoped to your organization and the phone number. If the number
does not belong to a contact yet, Simple creates a contact so the stored state
is visible in the dashboard.
US numbers can be formatted or sent as digits. Non-US numbers must include the
The response contains the normalized phone number, the stored object, its
revision, and expiration metadata:
Data does not expire unless you provide
+ country code. URL-encode the + when it appears in the path.
ttlSeconds. When supplied, it must
be an integer from 60 seconds through 90 days. The serialized data object
may be at most 64 KiB.
The endpoint returns 401 when authentication fails and 422 when the phone
number or request body is invalid.Authorizations
Path Parameters
The caller's phone number. US numbers may be formatted or sent as digits; non-US numbers must include the + country code.
Body
application/json
Response
Contact data replaced.
The normalized phone number in E.164 format.
The stored JSON object.
The revision number of this value.
Required range:
x >= 1Remaining TTL in seconds, or null when the record has no expiry.
Expiration timestamp in UTC, or null when the record has no expiry.