Update
API Reference
Update a company entity
Update attributes and data for an existing company — for company entities in the gu1 risk and compliance platform, with examples for update use cases.
PATCH
Update
Overview
Updates an existing company’s attributes and data. This endpoint automatically triggers a re-evaluation of the company’s risk score and emits real-time update events.Endpoint
Authentication
Requires a valid API key in the Authorization header:Path Parameters
The gu1 ID of the company to update
Request Body
All fields are optional - only include the fields you want to update.Update the company’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).Update tax identification number
Update ISO 3166-1 alpha-2 country code
Update custom attributes (merges with existing attributes)
Update company-specific data (merges with existing entityData)
Update company status. Available statuses:
pending- Initial state, awaiting processingunder_review- Under manual reviewactive- Approved and activesuspended- Temporarily suspended (requiresreason)blocked- Permanently blocked (requiresreason)rejected- Rejected during onboarding (requiresreason)
suspended, blocked, or rejected require a reason field for audit purposes.Required when changing status to
suspended, blocked, or rejected. Provides audit trail for status changes.UUID of the risk matrix to associate with this company. Updates which rules are used for risk evaluation.
Response
The updated company object with all current values
Newly created evaluation triggered by the update
id- Evaluation IDentityId- Entity IDdecision- “PENDING” (awaiting processing)evaluationType- “SYSTEM”reasons- Array with “Re-evaluation triggered by attribute change”
The company 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 company, the system automatically:- Records the change in the entity events log with a before/after snapshot
- Triggers re-evaluation to recalculate risk score based on new data
- Emits real-time event to notify connected clients of the update
- Maintains audit trail for compliance and review purposes
Examples
Update Company Income and Occupation
Update Contact Information
Update Custom Attributes Only
Update Company 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 KYB Verification
Progressive Profile Enrichment
Best Practices
- Partial Updates: Only send the fields you want to change - no need to send the entire company
- Monitor Re-evaluations: Check the returned evaluation ID to track risk score recalculation
- Audit Trail: Use the
previousEntityin the response to maintain change history - Real-time Sync: Updates emit WebSocket events for real-time UI synchronization
- Idempotency: Safe to retry - updates with same data will not create duplicate events
Next Steps
- Get Company - View updated company details
- List Companies - Query companies with filters
- Upsert Company - Create or update in one operation