How do I get a test key?

From the developers panel, choosing the test environment when you create it. After that you can also create keys via the API asking for the test environment. The first one is best taken from the panel.

Do test records mix with the real ones?

No. They are two different companies: what you create with fact_test_ is not visible from a fact_live_ key, nor the other way round. It is not a filter, it is isolation by company.

Can I check that my webhook endpoint verifies the signature correctly?

Yes, with the endpoint's ping call, which is delivered in the sandbox too. Ordinary test events are recorded with livemode: false, but they do not go out.

Do I need to change code to move to production?

Reuse your integration for shared operations. Generate a fact_live_ key: editing the prefix of a test key does not work. Prepare your live contacts and series; their identifiers differ from those in the sandbox.

Invoicing sandbox

Test your invoices in a separate environment

From the app or through the API, check documents, totals and states before working with real data. Tests have their own company and numbering.

Start free Start with the API

From Factuarea
Separate data and numbering
From your integration

Invoicing · separate environments

InvoiceDraft

No number assigned

CustomerEstudio Ribera

Design consultancyQuantity: 2 × €150.00€300.00

Net amount: €300.00
VAT 21%: €63.00
Total: €363.00

Test document, not a tax invoice

Two companies, separate sequences

Test seriesF-2026-0006

Production seriesF-2026-0184

A draft uses no number. Issuing only advances the test series.

Validation and results

Check what happens when something fails, too

The sandbox applies the validation rules of available operations. Review invoice totals, correct rejected data and prepare your integration to handle errors.

POST /v1/invoicesfact_test_…

Line item fields

"lines": [{
  "quantity": 2,
  "unit_price": 150,
  "tax_rate": 21
}]

Result201 Created

{
  "data": {
    "status": "draft",
    "number": null,
    "total": 363,
    "currency": "EUR"
  }
}

Result422 Unprocessable Entity

{
  "error": {
    "type": "invalid_request_error",
    "code": "invalid_param_value",
    "param": "lines.0.quantity"
  }
}

Draft created: €300.00 net and €63.00 VAT. No invoice number is used yet.

You can also test permissions, states and idempotency. Use the features enabled by your plan; test mode does not expand access or remove API limits.

Understand API errors

What you can actually test

Test the process and know its limits

Data stays separate from production. Fiscal submissions and document emails do not reach third parties. Webhooks have one specific exception: the connection ping.

VeriFactu and AEAT

No records are sent to AEAT. Direct VeriFactu module routes are unavailable in the sandbox. A test does not prove fiscal acceptance.

Document email

Follow the sending flow and its states without delivering email to the recipient, including your own inbox.

FacturaE and FACe

FACe submissions are simulated. A FACE-SANDBOX-* reference is not a real filing with the public administration.

Automations

Inspect triggers and runs. Steps are skipped with sandbox_neutralized: the adapter does not run and its action is not applied.

Webhooks · Sandbox

invoice.createdInternal record only

Recorded without external delivery

Test events remain available to query with livemode: false. They are not sent to the external receiver.

GET /v1/events
"livemode": false

webhook.pingReal HTTP delivery

The ping does reach your receiver

Check connectivity and verify the signature. It sends webhook.ping without creating a business event in the event log.

POST /v1/webhook_endpoints/{id}/ping
{"type":"webhook.ping"}

Explore webhook delivery and signatures

Take what you have tested into production

Same contract, separate resources

Reuse your integration for operations available in both environments. Prepare real data and use a newly generated production credential; editing a key prefix does not turn it into another key.

How you access sandbox

From Factuarea

Enter Test mode and check your documents. Switching back to Production restores your real company context. Test data stays separate.

Test modeProduction

In the app, choose the environment in the header; on mobile, use the user menu. You confirm before switching.

Before enabling production

0 of 3 points reviewed

Check the points you have already verified in your integration.

Prepare real resourcesCreate or select production contacts and series. Their identifiers differ from those in the sandbox.
Generate a production keyCreate a fact_live_ key with the necessary permissions and store it in your secrets manager. Do not reuse the test secret.
Review real effectsCheck issuance, email and receiver settings before operating. Enabled production deliveries do reach third parties.

Read how test mode works Create your first invoice through the API

Choose your connection

An integration that fits your stack

Work with an SDK, explore the API contract or connect your assistant. Choose your tool to find the right starting point and documentation.

Compatible technologies and clients

Your tool → Factuarea

Official SDK

Your integration, in TypeScript

Install the official SDK to work with the API from Node.js. Includes retries, pagination and webhook signature verification.

npm install @factuarea/sdkConnect TypeScript

API operations: 595
resources: 50
MCP tools: 581
documentation pages: 1306

Questions

Sandbox questions

No. A fact_test_ key operates on the sandbox company and uses that company's series. The sequence of your production series is neither touched nor consumed.

A more connected business

Test the integration with isolated data

Generate a fact_test_ key in the developer dashboard. Send it to the same API URL with the permissions your application needs.

Start free Try my first invoice