List Contacts

List Lifecycle Manager contacts for accessible clients. Supports optional client, integration-lineage, hidden-status, email-presence, assigned-license, and name/email search filters, cursor pagination, Core record lineage, license assignment details, and SaaS-derived MFA/activity posture.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string
^(eq):.+$

Limits the result set to contacts belonging to the specified Lifecycle Manager client. Omit this filter to return contacts for every client the caller can access.

string
^(eq):.+$

Controls whether hidden Lifecycle Manager contact records are included. Omit this filter to return visible contacts only.

string
^(eq):.+$

Controls whether results have a non-empty email address. Omit this filter to return contacts regardless of email availability.

string
^(eq|in):.+$

Limits results to contacts with lineage from the specified integration configuration. Use eq:id for one configuration or in:id1,id2 to match contacts with lineage from any of several configurations.

string
^(eq):.+$

Controls whether results hold at least one assigned license. Use eq:true for contacts with any license or eq:false for contacts with none. Omit this filter to return contacts regardless of licenses.

string
^(eq|in|nin):.+$

Limits results by assigned license name, matched without regard to case. Use eq:name or in:name1,name2 for contacts holding at least one of the licenses, or nin:name1,name2 for contacts holding none of them, including contacts with no license. In in: and nin: lists, enclose names containing commas in double quotes and escape double quotes and backslashes with a backslash.

Searches contact first name, last name, and email address.

string
^[+-]?[a-z][a-z0-9_]*(\.[a-z][a-z0-9_]*)*(,[+-]?[a-z][a-z0-9_]*(\.[a-z][a-z0-9_]*)*)*$

One or more sortable fields, separated by commas. Prefix with '+' to sort ascending or '-' to sort descending.

int32

The number of records to be returned in a single page

string

Opaque cursor of the page to return. Omit this value for the first
page, then pass the next_cursor value from the previous response.

  • Cursor pagination cannot guarantee atomicity.
  • Endpoints may skip new records inserted between paginated reads.
  • Endpoints may occasionally return duplicate records.
Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json