IdentityResolutionSettings

Update Identity Resolution Settings.

Changed on Aug 11, 2026

Update the identity resolution settings for this memory store, which determine how Customer Memory will use identifiers for searching, merging, and resolving profiles.

put/v1/ControlPlane/Stores/{storeId}/IdentityResolutionSettings

Request

Base URL
https://memory.twilio.com
URL
https://memory.twilio.com/v1/ControlPlane/Stores/{storeId}/IdentityResolutionSettings
Auth
HTTP basic

Headers

If-Matchstring

Example:"eyJpZCI6ImFuX2lkIiwidiI6MX0"

Allows for optimistic concurrency control by making the request conditional. Server will only act if the resource's current Entity Tag (ETag) matches the one provided, preventing accidental overwrites.

Request body

matchingRulesstring[] required

Priority list of identifiers to locate profiles to apply new data to, or for determining if two existing profiles should merge.

Individual rules are evaluated with OR logic between them, meaning that satisfying any single rule will trigger a match. Each rule is a single identifier type; compound rules are not supported.

Rules are evaluated in order.

If no rule matches against existing profiles, a new profile will be created.
If a rule matches to a single existing profile, the profile will be updated.
If a rule matches to multiple existing profiles, those existing profiles will be merged.

Example request

{
  "identifierConfigs": [
    {
      "idType": "email",
      "limitPolicy": "fifo",
      "enforceUnique": true,
      "normalization": "email"
    }
  ],
  "matchingRules": [
    "email",
    "whatsapp",
    "phone"
  ]
}

Response

Identity Resolution Settings accepted for processing.

messagestring

statusUrlstring

URI to check operation status.

Example response

{
  "message": "Identity Resolution Settings accepted for processing."
}

Changes

Aug 11, 2026v1b0ed05460bbf Revision changes
- breaking
  the request property became required
- breaking
  the request property became required
- breaking
  the response property's max was increased from 99999.00 to 999999.00 for the response status
- breaking
  the response property's max was increased from 99999.00 to 999999.00 for the response status
- breaking
  the response property's max was increased from 99999.00 to 999999.00 for the response status
- breaking
  the response property's max was increased from 99999.00 to 999999.00 for the response status
- breaking
  the response property's max was increased from 99999.00 to 999999.00 for the response status
- info
  added the non-success response with the status

Operation history