# About the Contacts API

The Contacts API allows you to manage contact information for your site's customer database. Create, update, and organize contact records with intelligent duplicate detection, member integration, and comprehensive contact data management. Use this API to build CRM systems, manage customer relationships, and synchronize contact data across multiple platforms.

With the Contacts API, you can:

+ **Manage Contact Information**: Create and manage contact records with names, emails, phones, and addresses.
+ **Handle Contact Deduplication**: Automatically detect and prevent duplicate contacts using intelligent matching logic.
+ **Integrate with Site Members**: Integrate with [site member](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/member-management/members/introduction) accounts for unified user management.
+ **Manage Contact Organization**: Organize contacts using tags and custom extended fields.
+ **Process Bulk Operations**: Perform bulk operations for efficient data processing and imports.
+ **Manage Marketing Subscription Status**: Track and manage contacts subscription preferences to marketing campaigns.
+ **Handle Image Uploads**: Handle contact images with asynchronous upload processing.
+ **Restore Deleted Contacts**: Restore deleted contacts from a 90-day trash bin recovery system.

**Important information:** The Contacts API uses matching logic to prevent duplicates based on the `externalId`, `email`, and `phone` identifiers. Site member contacts have special restrictions for certain operations. All contact deletions are soft deletes with a 90-day recovery period.

## Before you begin

It's important to note the following points before starting to code:

+ **Required Fields**: At least one of name (first/last), email, or phone is required when creating contacts.
+ **External IDs**: `externalId` can be set only once during creation and can't be changed afterward.
+ **Site Member Emails**: The main email of a contact that is a site member can't be changed through the Contacts API. Update it through the Members API instead.
+ **Contact Matching**: The API uses matching logic based on the `externalId`, `email`, and `phone` identifiers to prevent duplicates. Understanding the [matching rules](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/matching-contacts) is important for proper contact management.
+ **Rate Limits**: Wix API rate limits allow an app to perform up to 200 requests per minute, per instance. If this limit is exceeded, the app may be throttled.
+ **Bulk Limits**: Synchronous bulk operations are limited to 100 items per request and up to 50 requests per minute. Asynchronous bulk operations by filter are limited to 10 requests per minute. Ensure your app handles these limits gracefully.
+ **Asynchronous Operations**: The by-filter bulk endpoints (such as Bulk Delete Contacts By Filter, Bulk Update Contact Tags By Filter, Bulk Update Phone Country Code By Filter, and Bulk Update Contact Subscriptions) run asynchronously and return a `jobId`. Pass this ID to [Get Async Job](fallback::https://dev.wix.com/docs/api-reference/business-management/async-job/get-async-job) to track the operation's progress and results.
+ **Image Processing**: Contact images are processed asynchronously. Use the image upload status endpoints to track processing progress.
+ **Soft Deletes**: Deleted contacts are moved to a trash bin and can be restored within 90 days.
+ **Member Operations**: Operations on member contacts require the [Members Area](fallback::https://www.wix.com/app-market/web-solution/members-area) to be installed, and managing members is done through the [Members API](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/member-management/members/introduction).
+ **Eventually Consistent Fields**: The `memberInfo`, `email.subscriptionStatus`, and `phone.subscriptionStatus` fields are read-only and materialized from other systems. Changes to the underlying member or marketing consent are reflected after the relevant events are processed, so these values can briefly lag.

## Use cases

- [Import contacts from external systems](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/sample-flows#import-contacts-from-external-systems)
- [Manage site member contact integration](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/sample-flows#manage-site-member-contact-integration)
- [Process bulk contact operations](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/sample-flows#process-bulk-contact-operations)
- [Organize contacts with tags and custom data](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/sample-flows#organize-contacts-with-tags-and-custom-data)
- [Handle contact matching and deduplication](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/sample-flows#handle-contact-matching-and-deduplication)

## Terminology

- **Contact**: A person in a site's contact list, storing profile information such as name, email addresses, phone numbers, and addresses. A contact can optionally be linked to a site member.
- **Contact matching**: The logic that identifies potential duplicate contacts using the `externalId`, `email`, and `phone` identifiers, with priority-based ranking.
- **External ID**: A unique identifier from an external system, used for contact matching and import synchronization. It can be set only once and can't be changed.
- **Site member contact**: A contact that is also a registered site member with login credentials. Site member contacts have restrictions on updates and deletion.
- **Upsert**: An operation that creates a contact when no match is found, or updates an existing contact when a match is found based on the matching logic.
- **Subscription status**: A contact's opt-in or opt-out preference for email and SMS marketing communications.
- **Member info**: Additional information available when a contact is also a site member, including member status, login activity, and group memberships.
- **Tags**: Private labels assigned to contacts for organization and filtering. Tags are visible only to site collaborators.
- **Segments**: Groups of contacts based on specific criteria, managed through the site dashboard.
- **Extended fields**: Custom fields for storing business-specific contact data beyond the standard fields. Defined and validated using the [Data Extension Schema API](fallback::https://dev.wix.com/docs/api-reference/business-management/data-extension-schema/introduction).
- **Trash bin**: Temporary storage for deleted contacts that allows restoration within 90 days before permanent deletion.

@sdk_package_setup

# Contacts API: Sample Flows

This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation.

## Import contacts from external systems

Your app needs to synchronize customer data from an external CRM system while preventing duplicate contacts and maintaining data integrity. This is common when migrating from legacy systems or integrating with third-party platforms.

To import contacts from external systems:

1. Prepare contact data with `externalId` values from your source system. If there is no `externalId`, the email and phone are used to check for matching contacts.
2. Call [Create Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/create-contact) with `allowDuplicates=false` to leverage automatic duplicate detection.
3. Handle `DUPLICATE_CONTACT_EXISTS` errors by using [Find Matching Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/find-matching-contacts) to identify existing records.
4. Use [Upsert Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/upsert-contact) with appropriate upsert mode (`OVERWRITE`, `APPEND`, or `OVERWRITE_APPEND_ARRAYS`) to update existing contacts.
5. For large datasets, use [Bulk Create Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-create-contacts) or [Bulk Upsert Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-upsert-contacts) with batches of up to 100 contacts.
6. Monitor bulk operation results and handle individual failures appropriately.

## Manage site member contact integration

Your app manages contacts that are also registered site members, requiring special permissions, and deletion restrictions.

To manage site member contact integration:

1. Identify member contacts by checking the `memberInfo` field in contact records.
2. For updates to member contacts, set `updateMember=true` in [Upsert Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/upsert-contact) requests.
3. Don't update the main email field for member contacts. It's managed through the [Members API](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/member-management/members/introduction).
4. When deleting member contacts, set `deleteMember=true` in [Delete Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/delete-contact) to remove both contact and member records.
5. Handle permission errors for member operations by ensuring your app has `CONTACTS.CONTACT_MEMBER_UPDATE` and `MEMBERS.MEMBER_DELETE` permissions.
6. Note that site owners and contributors can't be deleted even with proper permissions.

## Process bulk contact operations

Your app needs to efficiently handle large volumes of contact data for imports, updates, or cleanup operations while respecting rate limits and handling failures.

To process bulk contact operations:

1. Organize contact data into batches of maximum 100 items per request.
2. Use appropriate bulk endpoints: [Bulk Create Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-create-contacts), [Bulk Update Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-update-contacts), or [Bulk Delete Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-delete-contacts).
3. Set `returnEntity=true` if you need the full contact data in responses.
4. Process the `bulkActionMetadata` to understand success/failure counts.
5. Handle individual item failures using the `itemMetadata` in results array.
6. For filter-based operations, use [Bulk Delete Contacts By Filter](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-delete-contacts-by-filter) or [Bulk Update Contact Tags By Filter](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-update-contact-tags-by-filter) for asynchronous processing.
7. Respect rate limits of 50 requests per minute for bulk operations and 10 requests per minute for bulk operations with a filter.

## Organize contacts with tags and custom data

Your app categorizes contacts for marketing campaigns and stores industry-specific information using tags and extended fields.

To organize contacts with tags and custom data:

1. Create private tags for internal organization using the tags system.
2. Use [Update Contact Tags](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/update-contact-tags) to assign or remove tags from individual contacts.
3. For bulk tag operations, use [Bulk Update Contact Tags](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-update-contact-tags) with contact IDs or [Bulk Update Contact Tags By Filter](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-update-contact-tags-by-filter) for filter-based updates.
4. Store custom business data using the `extendedFields` property when creating or updating contacts.
5. Query contacts by tags using `tags.privateTags.tagIds` in filter expressions with `HAS_SOME` or `HAS_ALL` operators.
6. Use extended fields in queries to filter contacts by custom properties.

## Handle contact matching and deduplication

Your app implements intelligent contact deduplication to maintain clean customer data and merge duplicate records when necessary.

To handle contact matching and deduplication:

1. Use [Find Matching Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/find-matching-contacts) with `externalId`, `email`, or `phone` to identify potential duplicates before creating contacts.
2. Understand the matching priority: `externalId` (highest), `email`, then `phone` (lowest priority). See [Matching & Duplicate Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/matching-contacts).
3. Review matching results ordered by strength: multiple identifier matches first, then single identifier matches.
4. Use [Merge Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/merge-contacts) to combine duplicate records, specifying up to 5 source contacts to merge into a target.
5. Set `preview=true` to review merge results before committing the operation.
6. Handle merge restrictions: source contacts can't be site members, and target contact must remain valid after merge.
7. Use `allowDuplicates=true` in create operations only when intentionally creating duplicate contacts.

# Matching and Duplicate Contacts

When you create, update, or upsert a contact, the same person might already exist in the contact list. For example, a visitor could subscribe to a newsletter and later register as a site member using the same email. This guide explains how the Contacts API detects these cases and what happens when it finds a match.

## Contact identifiers

The Contacts API matches contacts using only 3 fields, called identifiers:

- `externalId`
- `email.email`
- `phone.phone`

Additional emails and additional phones aren't identifiers and aren't used for matching.

## Matching contacts and the duplicate contact

- **Matching contacts**: All existing contacts that share at least 1 identifier with the identifiers you provide.
- **Duplicate contact**: The single best match among the matching contacts. When more than 1 contact matches, the Contacts API chooses the duplicate contact using the priority rules described in [How the Contacts API chooses the duplicate contact](fallback::#how-the-contacts-api-chooses-the-duplicate-contact).

## Which contacts match

Which contacts count as a match depends on which identifiers you provide:

| Identifiers you provide | Matching contacts |
|---|---|
| `externalId` only | All contacts with the same `externalId`. |
| `email.email` only | All contacts with the same email. |
| `phone.phone` only | All contacts with the same phone. |
| `externalId` and `email.email` | All contacts with the same `externalId`, plus contacts with the same email that don't have a different `externalId`. |
| `externalId` and `phone.phone` | All contacts with the same `externalId`, plus contacts with the same phone that don't have a different `externalId`. |
| `email.email` and `phone.phone` | All contacts with the same email or the same phone. |
| `externalId`, `email.email`, and `phone.phone` | All contacts with the same `externalId`, plus contacts with the same email or phone that don't have a different `externalId`. |

When you provide both an email and a phone, with or without an `externalId`, a contact needs to match only one of them to count as a match. For example, if you provide `email = a@example.com` and `phone = +1 111`, a contact with `email = a@example.com` but a different phone number still counts as a match, and so does a contact with `phone = +1 111` but a different email address.

The Contacts API fetches up to 100 matching contacts for a single request.

## How the Contacts API chooses the duplicate contact

When more than 1 contact matches, the Contacts API chooses a single duplicate contact based on how many, and which, identifiers each match shares with the ones you provided. Matches with more identifiers, or with higher-priority identifiers, rank higher. Identifier priority, from highest to lowest, is `externalId`, then `email.email`, then `phone.phone`.

For example, if you provide all 3 identifiers, matches rank in this order:

1. `externalId`, `email.email`, and `phone.phone`.
1. `externalId` and `email.email`.
1. `externalId` and `phone.phone`.
1. `externalId` only.
1. `email.email` and `phone.phone`.
1. `email.email` only.
1. `phone.phone` only.

## Effects on each method

- [Create Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/create-contact): By default, creation fails if a contact with the same identifiers already exists. Set `allowDuplicates` to `true` to bypass the duplicate check.
- [Update Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/update-contact): The update fails if it would make the contact a duplicate of another contact. Set `allowDuplicates` to `true` to allow the update even if it creates a duplicate.
- [Upsert Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/upsert-contact): Uses the identifiers to decide whether to create a contact or update an existing one. If more than 1 contact matches, the duplicate contact is the one that gets updated.
- [Find Matching Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/find-matching-contacts): Returns the matching contacts for the identifiers you provide, up to 100, ordered by match strength.

## Examples

The following examples use this contact list:

- Contact A: `externalId = E1`, `email = a@example.com`, `phone = +1 111`
- Contact B: no `externalId`, `email = a@example.com`, `phone = +1 111`
- Contact C: `externalId = E2`, `email = a@example.com`, no phone
- Contact D: no `externalId`, `email = a@example.com`, `phone = +1 999`
- Contact E: no `externalId`, `email = z@example.com`, `phone = +1 111`

### Higher-priority matches win

If you call [Create Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/create-contact) with `externalId = E1`, `email = a@example.com`, and `phone = +1 111`:

- Both Contact A and Contact B match. Contact A matches on `externalId`, `email.email`, and `phone.phone`. Contact B has no `externalId` to conflict with the request, so it matches on `email.email` and `phone.phone`.
- Contact A is the duplicate contact, since a match on all 3 identifiers outranks a match on email and phone alone.
- Creation fails with a duplicate contact error unless you set `allowDuplicates` to `true`.

If you instead call [Upsert Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/upsert-contact) with the same identifiers, the Contacts API updates Contact A instead of creating a new contact.

### A different externalId excludes a contact

If you call [Find Matching Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/find-matching-contacts) with `externalId = E1` and `email = a@example.com`:

- Contact A matches, since it has the same `externalId`.
- Contact C doesn't match, even though it has the same email, because its `externalId` is different: `E2` instead of `E1`.
- Contact B matches, since it has the same email and no `externalId` to conflict with the request.

### Either email or phone can match

If you call [Find Matching Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/find-matching-contacts) with `email = a@example.com` and `phone = +1 111`, without an `externalId`:

- Contact D matches because its email matches, even though its phone is different.
- Contact E matches because its phone matches, even though its email is different.
- The Contacts API also returns Contact A and Contact B, which match on both identifiers.

## See also

- [Find Matching Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/find-matching-contacts)
- [Upsert Contact](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/upsert-contact)

# Contacts API: Supported Filters and Sorting

## Fields supported by Query Contacts

The following table shows field support for filters and sorting for the [Query Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/query-contacts) method:

| Field           | Supported filters                   | Sortable |
|-----------------|-------------------------------------|----------|
| `id`            | `$eq`, `$in`                        |          |
| `createdDate`   | `$eq`, `$gt`, `$lt`, `$gte`, `$lte`  | Sortable |
| `updatedDate`   | `$eq`, `$gt`, `$lt`, `$gte`, `$lte`  | Sortable |
| `email.email`   | `$eq`, `$in`, `$exists`              |          |
| `phone.phone`   | `$eq`, `$in`, `$exists`              |          |
| `externalId`    | `$eq`, `$in`, `$exists`              |          |

## Methods that use the search object

The following table shows field support for filters, sorting, and search for methods that use the search object:

- [Search Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/search-contacts)
- [Count Contacts](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/count-contacts)
- [Bulk Update Contact Tags By Filter](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-update-contact-tags-by-filter)
- [Bulk Delete Contacts By Filter](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-delete-contacts-by-filter)
- [Bulk Update Phone Country Code By Filter](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/contacts-v5/bulk-update-phone-country-code-by-filter)

| Field                                     | Supported filters                                 | Sortable | Searchable |
|--------------------------------------------|----------------------------------------------------|----------|------------|
| `id`                                        | `$eq`, `$ne`, `$in`, `$nin`                        |          |            |
| `createdDate`                               | `$eq`, `$ne`, `$gt`, `$lt`, `$gte`, `$lte`         | Sortable |            |
| `updatedDate`                               | `$eq`, `$ne`, `$gt`, `$lt`, `$gte`, `$lte`         | Sortable |            |
| `email.email`                               | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  | Sortable | Searchable |
| `phone.phone`                               | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  | Sortable | Searchable |
| `phone.e164`                                 | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  |          |            |
| `externalId`                                | `$eq`, `$in`, `$exists`                            |          |            |
| `source.userId`                             | `$eq`, `$ne`, `$in`, `$nin`, `$exists`             |          |            |
| `source.appId`                              | `$eq`, `$ne`, `$in`, `$nin`, `$exists`             |          |            |
| `source.additionalInfo`                     | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  |          |            |
| `assigneeId`                                | `$eq`, `$ne`, `$in`, `$nin`, `$exists`             |          |            |
| `timeZone`                                  | `$eq`, `$ne`, `$in`, `$nin`, `$exists`             |          |            |
| `locale`                                    | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  |          |            |
| `birthdate`                                 | `$eq`, `$ne`, `$gt`, `$lt`, `$gte`, `$lte`         | Sortable |            |
| `name.first`                                | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  | Sortable |            |
| `name.last`                                 | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  | Sortable |            |
| `name.full`                                 |                                                     |          | Searchable |
| `company.name`                               | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  | Sortable | Searchable |
| `company.jobTitle`                          | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  | Sortable | Searchable |
| `email.subscriptionStatus.status`           | `$eq`, `$ne`, `$in`, `$nin`                        |          |            |
| `email.deliverabilityStatus`                | `$eq`, `$ne`, `$in`, `$nin`                        |          |            |
| `phone.subscriptionStatus.status`           | `$eq`, `$ne`, `$in`, `$nin`                        |          |            |
| `phone.deliverabilityStatus`                | `$eq`, `$ne`, `$in`, `$nin`                        |          |            |
| `locationIds`                               | `$hasSome`, `$hasAll`, `$empty`, `$exists`         |          |            |
| `segmentIds`                                | `$hasSome`, `$hasAll`, `$empty`, `$exists`         |          |            |
| `tags.privateTags.tagIds`                   | `$hasSome`, `$hasAll`, `$empty`, `$exists`         |          |            |
| `lastActivity.date`                         | `$eq`, `$ne`, `$gt`, `$lt`, `$gte`, `$lte`         | Sortable |            |
| `memberInfo.memberId`                       | `$eq`, `$ne`, `$in`, `$nin`, `$exists`             |          |            |
| `memberInfo.status`                         | `$eq`, `$ne`, `$in`, `$nin`, `$exists`             | Sortable |            |
| `memberInfo.email`                          | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  | Sortable | Searchable |
| `memberInfo.emailVerified`                  | `$eq`, `$ne`                                       |          |            |
| `memberInfo.emailVerificationRequired`      | `$eq`, `$ne`                                       |          |            |
| `memberInfo.signupDate`                     | `$eq`, `$ne`, `$gt`, `$lt`, `$gte`, `$lte`         | Sortable |            |
| `memberInfo.profileInfo.nickname`           | `$eq`, `$ne`, `$in`, `$nin`, `$exists`, `$begins`  | Sortable | Searchable |
| `memberInfo.profileInfo.privacyStatus`      | `$eq`, `$ne`, `$in`, `$nin`, `$exists`             | Sortable |            |
| `memberInfo.profileInfo.reported`           | `$eq`, `$ne`                                       |          |            |
| `memberInfo.profileInfo.muted`              | `$eq`, `$ne`                                       |          |            |
| `memberInfo.userInfo.role`                  | `$eq`, `$ne`, `$in`, `$nin`, `$exists`             | Sortable |            |
| `memberInfo.sessionInfo.lastWebLogin`       | `$eq`, `$ne`, `$gt`, `$lt`, `$gte`, `$lte`         | Sortable |            |
| `memberInfo.sessionInfo.lastMobileLogin`    | `$eq`, `$ne`, `$gt`, `$lt`, `$gte`, `$lte`         | Sortable |            |
| `memberInfo.sessionInfo.mobileAppNames`     | `$hasSome`, `$hasAll`, `$empty`, `$exists`         |          |            |
| `memberInfo.groupInfo.groupIds`             | `$hasSome`, `$hasAll`, `$empty`, `$exists`         |          |            |
| `additionalEmails.email`                    | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `additionalPhones.phone`                    | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `additionalPhones.e164`                     | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.address.country`                 | `$hasSome`, `$hasAll`, `$exists`                   |          |            |
| `addresses.address.subdivision`             | `$hasSome`, `$hasAll`, `$exists`                   |          |            |
| `addresses.address.city`                    | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.address.postalCode`              | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.address.addressLine`             | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.address.streetAddress.name`      | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.address.subdivisionFullname`     | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.recipient.firstName`             | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.recipient.lastName`              | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.recipient.company`               | `$hasSome`, `$hasAll`, `$exists`, `$begins`        |          |            |
| `addresses.recipient.phone`                 | `$hasSome`, `$hasAll`, `$exists`                   |          |            |

__Related content:__
- [API Query Language](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::a6026c51-be14-4ea6-a108-dcbc36b074fa*fallback::https://dev.wix.com/api/rest/getting-started/api-query-language)

Generate Contact Image Upload Url