v1

latestOpenAPI 3.1.02026-07-2685154311.7 KB

Flow

Update a customer profile within Flow workflows

Updates an existing customer profile within a Flow workflow context. Customer PII is automatically encrypted before storage when profile data is updated. Only specified fields are updated, maintaining data integrity.

IVMS101 Validation Requirements (when profileData is provided):

Same validation rules as POST apply when updating profileData
For natural persons: name object is required
For legal persons: name and nationalIdentification objects are required
When nameIdentifier array is provided, its fields are required
Unknown fields are rejected (strict validation)

put/entities/{entityDID}/flow/customers/{customerDID}

Path parameters

entityDIDstring did required

Decentralized Identifier (DID)

Example:did:web:vasps.id:jxnl0411:at

The DID of the entity

customerDIDstring required

Customer identifier to update (mailto:, tel:, or supported DID method)

Request body

customerType'natural_person' | 'legal_person'

Type of customer (must match profileData if provided)

profileDataobject

IVMS101-compliant customer profile data (will be encrypted). When provided, must follow same structure as POST endpoint with required fields. See POST /entities/{entityDID}/flow/customers for full schema.

verificationStatus'pending' | 'verified' | 'rejected' | 'expired'

Customer verification status

verificationLevel'basic' | 'enhanced' | 'premium'

Level of customer verification

verifiedAtstring date-time

When customer was verified

verificationExpiresAtstring date-time

When verification expires

Response

Customer updated successfully