Overview
The country requirements endpoints help developers understand what fields are required for entity creation in different countries. Each country has specific validation rules, tax ID formats, and required fields. This eliminates trial-and-error when creating entities and provides clear guidance on what data is needed. For companies, fiscal address fields (e.g.domicilioFiscal, direccion, address) are optional at creation. You can create with tax ID and legal name only, then populate the address later via manual edit or country enrichments (e.g. ARCA for Argentina).
Supported Countries
gu1 currently supports 16 countries with comprehensive validation:🇦🇷 Argentina
CUIT validation
🇧🇷 Brazil
CNPJ validation
🇲🇽 Mexico
RFC validation
🇨🇱 Chile
RUT validation
🇨🇴 Colombia
NIT validation
🇵🇪 Peru
RUC validation
🇺🇾 Uruguay
RUT validation
🇪🇨 Ecuador
RUC validation
🇵🇾 Paraguay
RUC validation
🇧🇴 Bolivia
NIT validation
🇻🇪 Venezuela
RIF validation
🇺🇸 United States
EIN validation
🇨🇦 Canada
BN validation
🇪🇸 Spain
CIF validation
🇵🇹 Portugal
NIPC validation
🇪🇪 Estonia
Registrikood validation
Get All Countries
Response Example
Get Country-Specific Requirements
Path Parameters
string
required
ISO 3166-1 alpha-2 country code (e.g., “AR”, “BR”, “US”)
Response Fields
boolean
Indicates if the request was successful
object
Country validation details
object
Example request payload
Examples
Get Argentina Requirements
Response Example
Country-Specific Examples
🇦🇷 Argentina (CUIT)
🇧🇷 Brazil (CNPJ)
🇲🇽 Mexico (RFC)
🇺🇸 United States (EIN)
🇪🇸 Spain (CIF)
Error Responses
404 - Country Not Supported
Best Practices
Query Before Creating
Query Before Creating
Always query country requirements before creating entities to ensure you collect all necessary data from your users upfront.
Cache Requirements
Cache Requirements
Country requirements rarely change. Consider caching them in your application to reduce API calls.
Validate Client-Side
Validate Client-Side
Use the
taxIdFormat regex pattern to validate tax IDs on the client side before submitting to the API.Localize Field Names
Localize Field Names
Display field names in the user’s language. The API returns local field names (e.g., “razonSocial” for Argentina instead of “legalName”).
Next Steps
Create Entity
Use the requirements to create a properly validated entity
Validate Tax IDs
Validate tax IDs before entity creation