Skip to main content

Overview

Updates an existing entity’s attributes and data. This endpoint automatically triggers a re-evaluation of the entity’s risk score and emits real-time update events.

Endpoint

Authentication

Requires a valid API key in the Authorization header:

Path Parameters

string
required
The gu1 ID of the entity to update

Request Body

All fields from the create schema are available except type (entity type cannot be changed). All fields are optional - only include the fields you want to update.
string
Update the entity’s display name
External ID cannot be updated with this endpoint. Use Change external ID (POST /entities/change-external-id) with a mandatory reason (min. 5 characters).
string
Update tax identification number
string | null
Update root-level contact email. Omit to leave unchanged; null clears.
string | null
Update root-level contact phone. Omit to leave unchanged; null clears.
string | null
Root nationality (ISO 3166-1 alpha-2 when stored). Omit to leave unchanged; null clears. Updating entityData person/company nationality may refresh the root field when sent together.
string
Update ISO 3166-1 alpha-2 country code
object
Update custom attributes (merges with existing attributes)
object
Update type-specific data (merges with existing entityData)

Risk matrices

Assign or replace which risk matrices apply to this entity. Same semantics as Create entity (riskMatrixId / riskMatrixIds).
string | string[] | null
Legacy: one UUID, an array of UUIDs, or null to clear all assigned matrices. When riskMatrixIds is sent non-empty, it takes precedence over this field.
string[]
Preferred for multiple matrices: ordered list of UUIDs belonging to your organization. Send [] (or riskMatrixId: null) to remove all assignments.
Updating matrices assigns them on the entity record only; it does not run the rules engine. See Update entity by ID for full behavior and Analyze entity to evaluate rules after assignment.

Response

object
The updated entity object with all current values
object
Newly created evaluation triggered by the update
  • id - Evaluation ID
  • entityId - Entity ID
  • decision - “PENDING” (awaiting processing)
  • evaluationType - “SYSTEM”
  • reasons - Array with “Re-evaluation triggered by attribute change”
object
The entity state before the update (for audit/comparison)

Behavior

When you update an entity, the system automatically:
  1. Records the change in the entity events log with a before/after snapshot
  2. Triggers re-evaluation to recalculate risk score based on new data
  3. Emits real-time event to notify connected clients of the update
  4. Maintains audit trail for compliance and review purposes

Examples

Update Person Income

Update Company Information

Update Custom Attributes Only

Update Transaction Status

Response Example

Error Responses

404 Not Found

400 Bad Request - Invalid Data

401 Unauthorized

500 Internal Server Error

Use Cases

Update After KYC Verification

Progressive Profile Enrichment

Transaction Resolution

Best Practices

  1. Partial Updates: Only send the fields you want to change - no need to send the entire entity
  2. Monitor Re-evaluations: Check the returned evaluation ID to track risk score recalculation
  3. Audit Trail: Use the previousEntity in the response to maintain change history
  4. Real-time Sync: Updates emit WebSocket events for real-time UI synchronization
  5. Idempotency: Safe to retry - updates with same data will not create duplicate events

Next Steps