Search for Customer Profiles

With customer profiles stored in a Square account, you have several options to find them and view detailed customer information using the Customers API. These options involve calling the ListCustomers, RetrieveCustomer, and SearchCustomers.

In this topic, you learn how to use the Customers API to search for customer profiles using one or more of the supported query filters.

To search for customer profiles, You must have created at least one customer profile in a targeted Square seller account. To use the API to create customer profiles, see Use the Customers API.

Use the Customers API to search for customers

Using the Square Customers API to search for customer profiles involves supplying supported filters to match one or more of the following Customer attributes against specified query expressions:

• Creation source (creation_source) of the customer profile.

• Creation or last-update timestamps (created_at or updated_at) of the customer profile.

• Group membership (group_ids) of the customer.

• Customer email addresses (email_address) that the seller has collected in or imported into the seller's Customer Directory.

• Customer phone numbers (phone_number) that the seller has collected in or imported into the seller's Customer Directory.

• Customer reference ID (reference_id) set to cross reference an external system entity.

Each time you call a SearchCustomers endpoint, you can use multiple supported filters in any combination. The search result contains customer profiles that have all the specified query conditions matched. To search for customers that meet at least one of the specified query conditions, you can simply issue multiple single-filter searches and then join the result sets.

Exact and fuzzy search

With search by email addresses, phone numbers, and reference IDs, the API lets you search for targeted customer profiles with an exact or fuzzy match of the specified customer attributes against a query expression. With an exact search, a query expression is compared literally against the targeted customer attribute value. With a fuzzy match, the query expression is tokenized and each resulting token is compared against targeted attribute values. Customer profiles are returned if their targeted attribute values match all the tokens in any order.

Search result sorting

For search results, you can choose a specific attribute (such as, created_at or email_address) to sort the results. By default, customers are sorted alphanumerically by concatenating given_name and family_name. When the names are not set, string comparison is performed using one of the remaining attributes in the order of company_name, email_address, and phone_number in default sorting.

Newly created and updated profiles

Under normal operating conditions, newly created or updated customer profiles become available in SearchCustomers and ListCustomers endpoints in less than 30 seconds after they are created or updated. Some updates can take up to 1 minute to propagate. Occasionally, extraordinary network conditions (such as, incidents or outages) can slow the propagation even further. Under such circumstances, newly created or updated profiles might not be included in your search result. When this happens, wait a short time and then retry your search request.

Search result pagination

If your search returns more than 100 records, the endpoint paginates your results. For more information, see Pagination.

Search by creation source

You can use the Square Seller Dashboard, a Square Point of Sale application, or the Square Customers API to create customer profiles in a seller account. Customer profiles created using the Seller Dashboard or a Square Point of Sale application have the Customer creation_source attribute set to the value of DIRECTORY. Profiles created using an application calling the Customers API have the creation_source attribute set to the value of THIRD_PARTY. When duplicate customer profiles are merged manually or automatically into a new and updated profile, the new customer profile's creation_source is set to MERGE.

To search customer profiles by creation source, submit a request with the creation_source filter specified in the request body. The following example shows how to search for customer profiles created by the Square Directory service, namely, through the Seller Dashboard or a Square Point of Sale application:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "creation_source": {
          "values": [
            "DIRECTORY"
          ]
        }
      }
    }
  }'

To search for customer profiles created by third-party applications, change the creation_source filter in the previous example to use THIRD_PARTY in place of DIRECTORY:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "creation_source": {
          "values": [
            "THIRD_PARTY"
          ]
        }
      }
    }
  }'

To search for customer profiles created by the Directory service or a third-party application, use the following filter in the request body:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "creation_source": {
          "values": [
            "DIRECTORY",
            "THIRD_PARTY"
          ]
        }
      }
    }
  }'

Search by creation or update time

You can call the SearchCustomers endpoint with the created_at or updated_at filter to search for customer profiles based on their creation time or the last-update time, respectively. Such filters are useful to synchronize customer data by polling. For example, you can issue a search by update time request in a given time interval and then determine subsequent actions to take on the updated customer in the search result.

The created_at and updated_at filters are identical in structure. They both require that you specify a start_at and end_at time to specify a time interval in which the targeted customer profiles were created or updated. For example, the following created_at filter defines the time interval when targeted customer profiles were created:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "created_at": {
          "end_at": "2020-04-30T00:00:00.001Z",
          "start_at": "2020-03-30T00:00:00.001Z"
        }
      }
    }
  }'

The timestamp format must be RFC-3339 compliant.

To search for a customer profile created or updated at a specific point of time, set the start_at value slightly smaller than the end_at value. The following updated_at filter shows an example of how to specify a specific time when a customer profile was updated:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "created_at": {
          "end_at": "2020-04-15T00:19:28.6Z",
          "start_at": "2020-04-15T00:19:28Z"
        }
      }
    }
  }'

Search by email address

You can search customer profiles by email addresses with an exact or fuzzy filter. In any particular search, you can use either an exact filter or a fuzzy filter, but not both.

Exact search by email address

To search for customer profiles by email address with an exact match, use the email_address filter as shown in the following search request example:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "email_address": {
          "exact": "johndoe@hotmail.com"
        }
      }
    }
  }'

This returns all customer profiles whose email_address attribute holds the value of "johndoe@hotmail.com".

If you make an error in your query expression (for example, enter "johndoe@hotmail.com" as "johndoe@hotmail.co"), none of the previous results are returned. As shown in the following example, this behavior differs from the fuzzy search.

Fuzzy search by email address

To search for customer profiles by email address with a fuzzy match, use the email_address filter as shown in the following search request example:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "email_address": {
          "fuzzy": "john.doe"
        }
      }
    }
  }'

The query expression of john.doe is first tokenized into two tokens of john and doe. The customer profile containing the email address of johndoe@hotmail.com matches both tokens and is therefore returned in the search result.

A fuzzy search also serves as a partial search. For example, if you typed johndoe@hotmail.co by mistake in the fuzzy query filter, you still get customer profiles containing the email address johndoe@hotmail.com.

A fuzzy search provides you with great flexibility. For example, you can obtain the customer profiles containing johndoe@hotmail.com even with the following fuzzy filter:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "email_address": {
          "fuzzy": "doe.john #com"
        }
      }
    }
  }'

Tokenization of the query expression of doe.john #com turns it into a three-token (john, doe, and com) query. The fuzzy search then selects customers profiles whose email addresses are john*doe@*.com or doe*john@*.com, where * stands for any valid email-address characters that can include, for example, ., _, or even a middle of name like joe.

Fuzzy search by email addresses can be a powerful option when used in a simple partial match or more advanced type-ahead user interfaces or embedded search experiences.

Search by phone number

As with search by email address, you can search for customer profiles by phone number with an exact or fuzzy query filter. For a particular search, you can use either an exact filter or a fuzzy filter, but not both.

Searches by phone number are applicable only to customers whose phone numbers are stored in or imported into the seller's Customer Directory.

Exact search by phone number

To conduct an exact search by phone number for customer profiles, you must specify in the search query a phone number in the E.164 format. The E.164 phone number format starts with a + (plus sign), followed by a country code and then a subscriber number. Spaces, dashes, or periods can be present in the phone number.

For example, a US phone number can use the following formats for the domestic version:

• +12345678901

• +1 234.567.8901

• +1 (234) 567-8901

In these examples, the leading 1 after + is the national version of the North American country code. The international version is 001.

As an example, the following request shows an exact search by phone number for the US customer whose phone number is (234) 567-8901:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "phone_number": {
          "exact": "+1 (234) 567-8901"
        }
      }
    }
  }'

The request can also take any other E.164 standard form.

If your seller account is outside the US, you might need to use international versions of an E.164-compliant phone number. In such cases, you can replace the phone number in the previous request body with any of the following formats:

• +0012345678901

• +001 234.567.8901

• +001 (234) 567-8901

The leading numbers 001 after the + (plus sign) is the international version of the North American country code.

As part of the exact search operation, a match is performed after non-numeric characters other than the + (plus sign). For example, ., (, ), or - are removed from the provided query expression and the stored phone_number attribute value of the Customer object. Furthermore, the stored phone numbers are converted to the E.164 standard form of the national version (for example, +12345678901) and international version (such as, +0012345678901) so that you can use either the national or international version when specifying the query.

The following table shows more examples to summarize the behaviors of the exact search filter by phone_number:

Fuzzy search by phone number

Fuzzy search by phone number works in a similar way to fuzzy search by email addresses. A phone number is tokenized by removing non-numeric characters other than the leading + (plus sign). Matched customer profiles are those whose phone_number attribute has tokens that match all the provided tokens in the search query at least once in any order of tokens.

To use the fuzzy search by phone number, you can specify part of a customer's phone number. For example:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "phone_number": {
          "fuzzy": "(234) 567-8901"
        }
      }
    }
  }'

As another example, if you use the following fuzzy search filter:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "phone_number": {
          "fuzzy": "(234)567"
        }
      }
    }
  }'

You get all the US customers whose phone numbers use the following formats:

• (234) 567-NNNN, (234) N56-7NNN, (234) NN5-67NN, (234) NNN-567N, (234) NNN-N567

• (n23) 456-7NNN, (n23) 4N5-67NN, (n23) 4NN-567N, (n23) 4NN-N567

• (nN2) 345-67NN, (nN2) 34N-567N, (nN2) 34N-N567

• (nNN) 234-567N, (nNN) N23-4567, (nNN) 234-N567

• (nNN) 567-234N, (nNN) N56-7243, (nNN) 567-N234

• (nN5) 672-34NN, (nN5) 67N-234N, (nN5) 67N-N234

• (n56) 723-4NNN, (n56) 7N2-34NN, (n56) 7NN-234N, (n56) 7NN-N234

• (567) 234-NNNN, (567) N23-4NNN, (567) NN23-4NN, (567) NNN-234N, (567) NNN-N234

where "n" stands for any number between 1 and 9 and "N" stands for a number between 0 and 9. This example shows that the fuzzy phone_number filter matches a query expression with the stored phone_number attribute token by token, irrespective of the token order.

Fuzzy search by phone numbers can be powerful. As an example, you can use a fuzzy filter in a search to return likely candidates for a user to select as the user enters the phone number digit by digit, provided that you have defined metrics for the likeliness.

Search by reference ID

When a Square customer profile is associated with an external entity in another system, the association is captured by the reference_id attribute of the Square Customer object.

Given the ID of an external entity, you can use the Square Customers API search by reference ID to determine the associated customer profiles in a Square seller's Customer Directory. To do so, you specify a reference_id filter when calling the SearchCustomers endpoint.

As with search by email address and by phone number, the reference_id search filter lets you query customer profiles with an exact or fuzzy match of the query expression against the reference_id attribute value.

Exact search by reference ID

To search Square customer profiles by reference ID with an exact match, use a search-by-reference-Id filter as illustrated in the following example search request:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "reference_id": {
          "exact": "ZGYZ-ABZG-97YX-XJ16"
        }
      }
    }
  }'

The response returns the Square customer profiles whose reference_id attribute value is exactly ZGYZ-ABZG-97YX-XJ16.

Fuzzy search by reference ID

To perform a fuzzy search by reference IDs, use a fuzzy search filter as shown in the following example search filter:

curl https://connect.squareup.com/v2/customers/search \
  -X POST \
  -H 'Square-Version: 2020-12-16' \
  -H 'Authorization: Bearer {{ACCESS_TOKEN}}' \
  -H 'Content-Type: application/json' \
  -d '{
    "query": {
      "filter": {
        "reference_id": {
          "fuzzy": "ZGYZ-97YX"
        }
      }
    }
  }'

This filter returns the customer profiles whose reference_id attribute contains the ZGYZ and 97YX tokens at least once each and in any order.

As a string value, a reference ID is tokenized by removing non-alphanumeric characters. A customer profile is selected if each provided token is matched at least once against the profile's reference_id attribute, irrespective of the order of the tokens.

Fuzzy search by reference IDs can be powerful to help manage customer profiles. For example, with the help of a structured, multi-part identifier schema, you can use the fuzzy search to aid discovery of customer profiles in a structured way by matching part of a reference ID (for example, a prefix or suffix) or by querying reference IDs containing multiple tokens.