Skip to content

Sandbox vs Live API Keys

LexgoSign sandbox is an API key stage, not a separate host or environment.

Use a sandbox key while integrating. Switch to a live key when you need legally binding signatures for real recipients.

Same base URL

Sandbox and live keys both call production API hosts:

https://api.lexgo.cl/v1

Gateway path

Externally, api.lexgo.cl strips the /api prefix. Call https://api.lexgo.cl/v1/....

There is no sandbox-api host

https://sandbox-api.lexgo.cl does not exist. Always use https://api.lexgo.cl and select sandbox or live via your API key.

Confirm the stage of your key with POST /v1/test — the response includes "environment": "sandbox" or "environment": "live".

Sandbox restrictions

Behavior Sandbox Live
Base URL api.lexgo.cl api.lexgo.cl
Recipient emails Only enterprise team members Any valid email
Document watermark NON-BINDING DOCUMENT on every page None
Legal validity Not legally binding Legally binding
QUALIFIED_CHILE signature type Free FirmAki sandbox identity checks and signing Allowed
Usage / billing reports Excluded Included

Recipient email allowlist

With a sandbox key, every recipient email must belong to a user on your enterprise team. Otherwise create/send fails with:

The email of the recipient '…' is not in the sandbox allowed email list: …

How to add an allowed email

  1. Sign in to app.lexgo.cl
  2. Open Equipos in the sidebar (/teams)
  3. Click Acciones → Crear miembro
  4. Invite or create the user with the email you will use as a sandbox recipient

Only emails listed under your organization members can be used as sandbox recipients.

Sandbox vs staging

Do not confuse sandbox keys with Lexgo's staging environment:

Concept What it is Host
Sandbox key Test stage of your production API key api.lexgo.cl
Staging Separate Lexgo deployment for Lexgo QA api-beta.lexgo.cl

Integrators almost always want a sandbox key on api.lexgo.cl, not staging.

  1. Create a sandbox API key in Lexgo (Settings → API Keys)
  2. Add test recipients as team members under Equipos
  3. Create and send an envelope against https://api.lexgo.cl
  4. Open signing links / complete the flow with those team emails
  5. When ready for production, create a live key and use real recipient emails

Chilean advanced signatures in sandbox

Use QUALIFIED_CHILE to exercise FirmAki's sandbox authentication and signing journey. This is provider test signing: documents retain the NON-BINDING DOCUMENT watermark, have no legal validity and are excluded from live billing. Recipients must remain active members of your enterprise team and use reachable email inboxes; FirmAki sends its own email verification code.

Create/send the envelope with your sandbox key, open its signer link, and follow the provider's hosted identity checks. Use one of the published test RUTs (44444444-4, 55555555-5, 88888888-8, 99999999-9) with Clave Única password testing. The requested and authenticated RUT must match. Use Simular NFC, answer each Buró question with its matching answer ID (1→1 through5→5), and select Khipu DemoBank, password 1234, authorization 11-22-33.

Complete email verification, set your test certificate password, then return to Lexgo and sign through FirmAki. For repeatable sandbox tests, FirmAki's example certificate password is Password123!; it is test data and must never be used for a live certificate. Clave Única uses the separate published password testing. A completed test produces a watermarked PDF; a provider login or a delivered webhook alone does not mean the envelope is signed.

See FirmAki's sandbox test data. Live keys continue through the live provider.