Skip to main content
Each environment uses a different API key. View, copy, or rotate the key for the environment you are using in the Production dashboard or Sandbox dashboard. See Where can I manage API keys? for details.

Create sandbox entities

Sandbox does not reserve or publish a fixed set of RFCs. When you create an entity, you can use any RFC that matches the format for its type: 13 characters for a person and 12 characters for a company. The dashboard can generate a valid-format RFC for you, and you can edit it before creating the entity. By default, sandbox assigns the entity a stable simulated fiscal profile. Tax status and applicable tax-return extractions reuse that profile so the generated records remain consistent across extractions. To select a specific profile through the API, add metadata.sandbox.taxRegime to POST /entities:
Person entities support 605 (Salaries and assimilated income), 612 (PFAE), 621 (RIF), 625 (Digital platforms), and 626 (RESICO). Company entities support 601 (General legal persons law) and 626 (RESICO). Omit metadata.sandbox.taxRegime when you do not need a particular profile; sandbox then assigns one of the supported regimes for the entity type when it creates the entity, and keeps it.

Background check profile

The in-house background check extractors (court_records, adverse_media, blacklists, and politically_exposed_persons) generate simulated findings in sandbox. By default each one decides on its own, and stably, whether an entity has findings: most entities have court cases or adverse media coverage, and a few are on a blacklist or hold a public office, so a re-run returns the same records. To exercise a specific path, add metadata.sandbox.backgroundCheck to POST /entities:
  • flagged: every applicable source finds the entity. The court records extractor returns several cases with their publication history, including one criminal case; the adverse media extractor returns articles; the blacklists extractor returns a sanctions or debarment listing; the politically exposed persons extractor returns an office for a person entity.
  • clean: every applicable source finds nothing.
Politically exposed persons screening applies to person entities only: a company entity is not screened under either profile, and its extraction fails as unsupported, as in production. Omitting the field, or sending null, leaves the choice to sandbox. The profile is read when it is sent on POST /entities and only changes what sandbox generates. Production accepts the field and ignores it.