Read Contact Data
Contacts
Read Contact Data
Read the stored data for a contact phone number
GET
Read Contact Data
Use this endpoint to retrieve state that Simple or another connected system
previously stored for a caller. This lets a workflow such as Five9 look up
context from an earlier touch using the caller’s phone number.
Data is scoped to your organization. US numbers can be formatted or sent as
digits. Non-US numbers must include the
The response includes the normalized phone number, stored fields at the top
level, revision, and expiration metadata. If a stored key has the same name as
a metadata field, the metadata value shadows the stored value in this response:
Records have no expiry by default. A record with an expired TTL, or a record
that has been deleted, is treated as missing and returns
+ country code. URL-encode the +
when it appears in the path.
Callers that do not have a phone number can be keyed by any other identifier,
such as a chat or SIP identifier, of up to 128 characters. Simple stores those
identifiers as provided and returns them unchanged in phoneNumber.
404.
The endpoint returns 401 when authentication fails, 404 when no current
data exists for the caller identifier, and 422 when the identifier is invalid.Authorizations
Path Parameters
The caller's phone number or other caller identifier. US numbers may be formatted or sent as digits; non-US numbers must include the + country code. Non-phone identifiers (for example chat or SIP identifiers) are accepted verbatim, up to 128 characters.
Response
Current contact data.
The normalized phone number in E.164 format, or the caller identifier as provided when it is not a phone number.
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.