Skip to main content
POST
Create an entity (person or company)

Overview

Creates a new entity with the specified type and attributes. Entities represent the core data objects you want to analyze for risk and compliance.

Endpoint

Authentication

Requires a valid API key in the Authorization header:

Request Body

string
required
The type of entity to create. Available types:
  • person - Individual person/customer
  • company - Business entity
string
Your unique identifier for this entity in your system. Optional — gu1 assigns one automatically when omitted (see table below).
string
required
Display name for the entity
string
required
ISO 3166-1 alpha-2 country code (e.g., “US”, “BR”, “AR”)
string
Tax identification number (validated based on country). Within an organization, an active normalized taxId may belong to only one entity (person or company). Conflicts return 409 with code DUPLICATE_TAX_ID.
When externalId is omittedThe taxId column is still saved in the country display format when you provide a tax ID. Send an explicit externalId when you need your own CRM or user ID independent of the tax document.
string | null
Optional primary contact email stored on the entity row (nullable). Existing entities keep null until set. Send null on PATCH to clear.
string | null
Optional primary contact phone stored on the entity row (nullable). Existing entities keep null until set. Send null on PATCH to clear.
object | null
Optional weekly operational hours for KYT rules (outside_entity_operational_hours). Root-level field (not inside attributes).
  • timezone (required when operationalHours is sent): must be one of the transaction_time_zone enum values. Full list: Transaction Time Zone Enum.
  • weekly: keys mondaysunday. Each day: { "start": "09:00", "end": "18:00" } or { "closed": true }. Omitted days are treated as closed.
  • Used by transaction rules that compare transactedAt to this schedule in the entity’s local timezone.
string | null
Optional root-level nationality: ISO 3166-1 alpha-2, or a recognized label the API maps to ISO2. If omitted, the root field may still be derived from entityData.person.nationality or entityData.company.nationality when mappable.
string | number | Date
Registration or incorporation date of the entity. Accepts:
  • ISO 8601 datetime string (e.g., “2020-06-15T00:00:00Z”)
  • Unix timestamp (number)
  • JavaScript Date object
object
Optional — Custom attributes. Accepts flat ({ "phone": "..." }) or category-nested ({ "contact": { "phone": "..." } }) input. Stored verbatim (nested objects act as categories, returned as sent); see Update entity for details.
object
Optional - Custom risk factors and manual risk score overridesProperties:
  • reasons (array of strings) - Reasons for the risk assessment
  • customLabel (object) - Custom risk label configuration:
    • name (string) - Label name (e.g., “High Risk”, “Suspicious”)
    • color (string) - Color code for UI display
    • status (string) - Status indicator
    • minScore (number) - Minimum score for this label
    • maxScore (number | null) - Maximum score (null for infinite)
    • severity (enum) - Severity level: ‘low’, ‘medium’, ‘high’, ‘critical’
  • displayRange (object) - Score range display configuration:
    • max (number | null) - Maximum value (null for infinite)
    • min (number) - Minimum value
    • current (number) - Current score value
    • isInfinite (boolean) - Whether the range is infinite
  • originalScore (number) - Original calculated score before manual override
  • normalizedScore (number) - Normalized score value
Use case: Override automatic risk scoring with manual assessments for special cases.
object
Optional - Type-specific data structure. See examples below for each entity type.
When to use entityData?
  • Optional for basic entity creation - You can create an entity with just type, name, taxId, and countryCode
  • Required for enrichment and risk analysis - If you want to run compliance checks, you’ll need to provide relevant fields
  • Can be populated later - You can create a minimal entity first, then update it with full data before running risk analysis
Minimal Example (Person):
Full Example (Person with KYC data):
boolean
default:"false"
Mark this entity as a client/customer for tracking purposes
string | string[]
One or more risk matrix UUIDs (legacy: a single UUID string). If provided, after creation the system evaluates this entity only against active rules tied to those matrices (unless skipRulesExecution is true). Same semantics as riskMatrixIds when you send a single id as a string.
string[]
Preferred way to pass multiple matrices: ordered list of UUIDs belonging to your organization. When present and non-empty, it takes precedence over riskMatrixId.
boolean
default:"false"
Skip automatic rules execution after entity creation
number
default:"0"
For company entities: How many levels of shareholders to auto-create (0-5).
  • 0 = None (default)
  • 1 = Direct shareholders only
  • 2 = Shareholders + their shareholders
  • 3-5 = Deeper nested levels
Useful for automatic KYB and UBO (Ultimate Beneficial Owner) discovery.
array
Declarative links to entities that already exist in the same organization (max 10). Independent of shareholderDepth / enrichment.Each item must include exactly one of: relatedEntityId (UUID), relatedTaxId, relatedExternalId.If the counterpart is missing → 404 RELATED_ENTITY_NOT_FOUND and the entity is not created.
string
default:"under_review"
Initial status for the entity. Options:
  • active - Entity is active
  • inactive - Entity is inactive
  • blocked - Entity is blocked
  • under_review - Entity is under review (default)
  • suspended - Entity is suspended
  • expired - Entity has expired
  • deleted - Soft deleted
  • rejected - Entity was rejected
object
Optional. Requests watchlist mode (op 1: screening plus watchlist subscription for periodic runs) for a monitoring-capable enrichment, instead of a one-off check (op 0).Scope today: only global_gueno_sanctions_enrichment. Map keys must match codes in autoExecuteIntegrations.enrichments. Legacy *_check codes were removed (2026-06-04) and are no longer part of the contract.
  • main: flags for the main entity on this POST /entities.
  • relationships: ignored here; use Create automatically with depth > 0.
Per-code value (object recommended; legacy boolean still accepted):
  • { "watchlist": true } — subscribe; monitoring rules use the entity’s global riskMatrixId.
  • { "watchlist": true, "riskMatrixId": "<uuid>" } — subscribe; only that matrix on monitoring-triggered runs.
  • { "watchlist": false } or false — no watchlist.
  • true — same as { "watchlist": true }.
Requirements (if any fail, enrichment still runs as op 0): (1) code in enrichments or active via execute-all; (2) org monitoring ON in Marketplace for Gu1 sanctions.Guide: Gu1 sanctions monitoring. Examples: Monitoring on create.
object
Configure automatic execution of enrichment integrations when creating the entity.Properties:
  • executeAllActiveEnrichments (boolean) - Execute all active enrichment integrations
  • enrichments (array) - Array of specific enrichment provider codes to execute (see Provider Codes Reference)
  • enrichmentGroupRefs (array of strings, optional) - Marketplace enrichment group slugs. With executeAllActiveEnrichments: false, groups are resolved and merged with explicit enrichments. With executeAllActiveEnrichments: true, group refs are ignored (not resolved); explicit enrichments may still append after the active set.
  • excludeEnrichments (array, optional, default: []) - Provider codes to omit from the final resolved enrichment set

Entity Data Structures

Person Entity

Gender (entityData.person.gender) — closed enum. Only the values below are accepted; any other string (e.g. X, non_binary) returns a validation error.Argentina (AR): automatic CUIL derivation from DNI + gender and RENAPER identity checks only recognize M/F (or male/female). With other or unknown, CUIL is not auto-derived and RENAPER cannot use gender from the entity.

Company Entity

Address Format: The address field supports both formats:
  • String format (simple): "Av. Paulista, 1000, São Paulo, SP, Brazil"
  • Object format (structured):
This applies to person, company, and location entities.

Device Entity

Payment Method Entity

Location Entity

Document Entity

Alert Entity

Query Parameters

boolean
default:"false"
Force re-enrichment of the entity even if it already exists in the system.Type: boolean (query string: "true" or "false")Behavior:
  • When true: Forces the system to fetch fresh data from enrichment providers (e.g., background checks, KYC data, company registries)
  • When false or omitted: Uses cached enrichment data if available
  • Overrides organization setting enrichmentsConfig.reEnrichExistingEntities
Use Cases:
  • Re-validating entity data after a significant time period
  • Updating information when you know external data has changed
  • Manual refresh triggered by compliance team
  • Periodic data quality audits
Example:
Note: Re-enrichment may incur additional costs from third-party data providers.

Response

boolean
Indicates if the entity was created successfully
object
The created entity object including:
  • id - gu1’s internal ID
  • externalId - Your external ID
  • organizationId - Your organization ID
  • type - Entity type
  • name - Entity name
  • riskScore - Initial risk score (0-100)
  • status - Entity status
  • entityData - Type-specific data
  • attributes - Custom attributes
  • createdAt - Creation timestamp
  • updatedAt - Last update timestamp
object
Result of rules execution (only present when rules ran, e.g. when skipRulesExecution is false and a risk matrix is configured), including:
  • success (boolean) - Whether rules executed successfully
  • rulesTriggered (number) - Number of rules that were triggered
  • alerts (array) - Alerts generated by rules
  • riskScore (number) - Final calculated risk score
  • decision (string) - Final decision (APPROVE, REJECT, HOLD, REVIEW_REQUIRED)
  • rulesExecutionSummary (object) - Present when rules ran. See below for structure.
object
At the root of the response (same as transactions API). Only present when rules ran (e.g. skipRulesExecution is false and rules engine executed). Same value as rulesResult.rulesExecutionSummary. Summary of which rules matched (hit) vs did not match (no hit), executed actions, and total score. Omitted when rules did not run.
  • rulesHit (array) - Rules whose conditions were met. Each item: name, description, score, priority, category, status (e.g. active, shadow), conditions (array of { field, value, operator? }), actions (alerts, suggestion, status, assignedUser).
  • rulesNoHit (array) - Rules that were evaluated but conditions were not met. Same structure as rulesHit (includes configured actions, not executed).
  • actionsExecuted (object) - Aggregated executed actions across all rules that hit: alerts (array of { name?, type?, severity?, description? }), suggestion (BLOCK | SUSPEND | FLAG, highest weight), status (entity status applied, if any), assignedUser ({ userId }, if any), customKeys (array of strings, optional) — custom action keys from matched rules; for integrations/workflows.
  • totalScore (number) - Sum of score of all rules that hit and are not in shadow status.

Example: Gu1 Sanctions Monitoring on Create

monitoring does not run integrations by itself — it only changes how an enrichment already listed in autoExecuteIntegrations runs. Today the documented case is global_gueno_sanctions_enrichment (org must allow monitoring in Marketplace).
Legacy *_check codes (e.g. global_gueno_sanctions_check) were removed (2026-06-04). For watchlist on create, use global_gueno_sanctions_enrichment in both enrichments and monitoring.main.

Watchlist Only (Person)

Local Enrichments + Gu1 Monitoring (AR Person)

Combine registry/KYC enrichments with Gu1 watchlist in one POST /entities. monitoring only affects keys present in the map.
ar_renaper_* and ar_repet_* run as normal enrichments; only global_gueno_sanctions_enrichment can use op 1 when org monitoring is enabled.

Dedicated Risk Matrix for Monitoring (Optional)

riskMatrixId: null means inherit the entity global matrix for monitoring runs.

Company (type: "company")

Same monitoring.main shape; adjust type, entityData.company, and enrichments for your country.
monitoring.relationships is not used on POST /entities. For shareholders or related entities in the same job, use Create automatically with depth > 0, monitoring.relationships, and matching codes in autoExecuteIntegrationsShareholders.

Examples

Create Person Entity (KYC)

Create Company Entity (KYB)

Response Example

Error Responses

400 Bad Request — Invalid tax ID

400 Bad Request — Missing required fields

409 Conflict — Duplicate entity

Duplicate tax ID (same organization, any entity type) returns DUPLICATE_TAX_ID with existingEntityId / existingEntityType in details when available.

401 Unauthorized

429 Too Many Requests

500 Internal Server Error

Next Steps

After creating an entity, you can:
  1. Request AI Analysis - Get automated risk assessment
  2. List Entities - Query your entities
  3. Get Entity Details - Retrieve complete entity information
  4. Apply Rules - Run compliance and risk rules