Skip to main content
PATCH
Update

Overview

Updates an existing person’s attributes and data. This endpoint automatically triggers a re-evaluation of the person’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 person to update

Request Body

All fields are optional - only include the fields you want to update.
string
Update the person’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
Update ISO 3166-1 alpha-2 country code
object
Update custom attributes (merges with existing attributes)
object
Update person-specific data (merges with existing entityData)
string
Update person status. Available statuses:
  • pending - Initial state, awaiting processing
  • under_review - Under manual review
  • active - Approved and active
  • suspended - Temporarily suspended (requires reason)
  • blocked - Permanently blocked (requires reason)
  • rejected - Rejected during onboarding (requires reason)
Note: Status changes to suspended, blocked, or rejected require a reason field for audit purposes.
string
Required when changing status to suspended, blocked, or rejected. Provides audit trail for status changes.
string
UUID of the risk matrix to associate with this person. Updates which rules are used for risk evaluation.

Response

object
The updated person 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 person state before the update (for audit/comparison)
This endpoint does not return rulesResult or rulesExecutionSummary. The rules engine is not executed on update; those fields are only returned by endpoints that run rules (create, create-automatic, enrich, refresh, analyze).

Behavior

When you update a person, 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 and Occupation

Update Contact Information

Update Custom Attributes Only

Update Person Status

Response Example

Error Responses

404 Not Found

400 Bad Request - Invalid Data

400 Bad Request - Missing Reason for Status Change

401 Unauthorized

500 Internal Server Error

Use Cases

Update After KYC Verification

Progressive Profile Enrichment

Best Practices

  1. Partial Updates: Only send the fields you want to change - no need to send the entire person
  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