Argos juridical person API

Introduction

Argos Juridical Person is an artificial intelligence service designed to analyze and interpret global companies related data and generate structured risk analysis reports.

The service processes large volumes of data from international risk watchlists and provides: • PEP (Politically Exposed Persons) match analysis • International sanctions detection (OFAC, UN, EU) • Adverse media identification • Regulatory enforcement action assessment • Automated risk level classification • Generation of professional PDF reports

Use cases

Business Onboarding Risk Assessment Financial institutions can automatically analyze new customer data against international watchlists to identify PEP status, sanctions exposure, and adverse media, enabling faster and compliant onboarding decisions.
Ongoing Customer Monitoring The service continuously evaluates existing clients against updated risk databases, detecting new sanctions, regulatory actions, or reputational risks in near real-time.
Third-Party / Vendor Due Diligence Organizations can assess suppliers, partners, and contractors by analyzing their exposure to sanctions, enforcement actions, or negative media before establishing business relationships.
Compliance Automation for AML Programs Compliance teams can streamline Anti-Money Laundering (AML) workflows by automating risk classification and generating structured reports for audits and regulatory reviews.
Enhanced Due Diligence (EDD) For high-risk entities or individuals, the service provides deeper analysis, consolidating risk indicators into detailed reports that support decision-making processes.
Regulatory Reporting and Audit Support Automatically generated PDF reports provide traceability and documentation required for regulatory audits and internal compliance reviews.

General information

URLs of the service

Resource	URL
Base URL	https://web-prod01.tuidentidad.com
Swagger UI	https://web-prod01.tuidentidad.com/api/argos/juridicalPerson

Technical Specifications

Specification	Value
Protocolo	HTTP/HTTPS
Data format	JSON
Method	HTTP POST
Authentication	API Key (Header)
Content-Type	application/json
Supported languages	Spanish (es), English (en)

Authentication

Each company is assigned a unique, non-transferable API key that must be included to authenticate requests.

Headers

Header	Type	Required	Description
ApiKey	string	yes	Customer key.

Example: ApiKey: YOUR_API_KEY

Authentication Errors

Code	Public message	HTTP	Typical cause
ARGM-041	API key is required	401	API key missing from the header
ARGM-042	Invalid or inactive API key	401	API key is not registered or inactive
ARGM-043	Access denied: your account does not have access to this service	403	The account does not have access to this service

Example JSON response when no API key is provided

{
 "success": false,
 "analysis_result": null,
 "warnings": [{
 "code": "ARGM-041",
 "message": "API key is required",
 }]
}

Endpoint: / interpreter

Description: Sends a request to perform an AML risk assessment for a legal entity. Processing is executed in the background, and the client immediately receives a verificationId. Returns HTTP 202 Accepted.

Propertie	Value
URL	https://web-prod01.tuidentidad.com/api/argos/juridicalPerson
Method	POST
Content-Type	application/json
Authentication	Required (ApiKey)

Request Format

Headers

Header	Type	Required	Description
ApiKey	string	yes	Customer key.

Body Parameters

field	Type	Required	Description	Default	Example
json	object	yes	JSON response de BGC Media WorldCompliance	-	{...}
businessName	string	yes	Business name of the juridical person to search for.	-	Grupo México S.A.B.
country	string	no	Country ISO 3166-1 alpha-2	-	MX
rfc	string	No	Registro Federal del Contribuyente	-	XAXX010101000
lang	string	No	Language: "en" (english), "es" (spanish). Default value: "en"	en	es

Response 202 Accepted

{ "verificationId": "a7f8e3d2-4c1b-4567-89ab-cdef01234567" }

Get method

Description: Retrieves the status and result of a legal entity verification. The client must invoke this endpoint after receiving the webhook notification with status 3 (Delivering) and responding with {"completed": true}. Upon retrieval, the status is automatically updated to 4 (Completed). This operation is not billable (TransactionItems = 0).

Propertie	Value
URL	https://web-prod01.tuidentidad.com/api/argos/verificationStatus?verificationId={id}
Method	Get
Content-Type	application/json

Query Parameters

Parameter	Type	Required	Description
verificationId	string (UUID)	yes	Unique verification identifier returned in the POST request.

7. Error codes

Code	Public message	HTTP	Typical cause
ARGM-001	The field '`businessName`' is required and cannot be empty	400	The `businessName` field cannot be empty.
ARGM-002	The field '`json`' is required and must contain valid Check360 JSON data	400	Missing required `JSON` field
ARGM-003	The field '`lang`' must be 'en' or 'es'	400	Not Supported language
ARGM-004	Invalid request body: could not parse JSON	400	Request body is not valid JSON.
ARGM-005	The field '`country`' has an invalid format	400	Invalid country code (ISO 3166-1 alpha-2)
ARGM-006	The `verificationId` is required	400	`verificationId` was not included in the method
ARGM-007	The `verificationId` has an invalid format	400	The `verificationId` in not a valid UUID
ARGM-008	Content-Type must be application/json	415	Incorrect Header Content-Type

Examples of integration

CURL

curl --request POST \ 
  --url https://web-prod01.tuidentidad.com/api/argos/juridicalPerson \ 
  --header 'apikey: [API_KEY]' \ 
  --header 'content-type: application/json' \ 
  --data '{ 
    "json": { "status": 200, "body": { "records": [...] } }, 
    "businessName": "Grupo México S.A.B. de C.V.", 
    "country": "MX", 
    "rfc": "GME881101NI7", 
    "lang": "es" 
  }'

Response (202 Accepted):

{ "verificationId": "ce4ebf37-0ccf-427d-961e-example" }

Example of webhook received by the client (status 3)

{ 
  "verificationId": "ce4ebf37-0ccf-427d-961e-example", 
  "verificationType": 4, 
  "verificationStatus": 3, 
  "companyId": "3fcc760d-54bc-4b16-868e-example", 
  "verification": "{...JSON string del resultado...}", 
  "data": { 
    "VerificationId": "TUID2026032714example", 
    "VerificationStatus": 4, 
    "Verification": { 
      "analyzed_name": "Grupo México S.A.B. de C.V.", 
      "risk": "High", 
      "entity_info": { "business_name": "...", "country": "MX" }, 
      "relevant_data": { "sanctions": true, "blacklists": true }, 
      "relationships": [...], 
      "conclusion": "...", 
      "sources": [...], 
      "file": "base64..." 
    }, 
    "Warnings": null 
  } 
}

Example request with an error

Request sin businessName:

{ "json": { ... } } // missing businessName

Response (400 Bad Request):

{ "code": "ARGM003", "message": "The field 'businessName' is required." }

Best practices

Security

Never expose your API key in client-side code.
Store API keys in environment variables or secret management services.
Use HTTPS in production.
Rotate your API keys periodically.

10. Support

For technical support or integration inquiries, please contact us through the following channels.

Channel	Contact
Web site	https://tuidentidad.com
Documentation	https://web-prod01.tuidentidad.com/api/argos/juridicalPerson
Email support	soporte@tuidentidad.com

When reporting an issue, please include the following information:

Error code received (e.g., ARGM-005)
Request date and time
Request sent
Response received
Programming language