# EU E-Invoice Sandbox Send Flow

> EU E-Invoice Sandbox Send Flow is a paid API for AI agents from api.wsystem.dev, paid per call via x402, $0.08/call, status unknown (last checked 2026-10-30).

Runs a full EU e-invoice send pipeline in sandbox mode: VIES buyer check, sanctions screening, EN 16931 UBL creation/validation, Peppol routing, and sandbox transport with a signed evidence receipt — no real buyer is reached.

## Facts

- Endpoint: POST https://api.wsystem.dev/einvoice/send?utm_source=zero.xyz
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/eu-e-invoice-sandbox-send-flow-cf07d156
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5CXS5GZRPI92SwF_dOXkk

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability eu-e-invoice-sandbox-send-flow-cf07d156 -d '<json body>'
```

Example prompt: Run my invoice through the full EU e-invoice sandbox pipeline using mock transport — I want to check VIES and sanctions on the buyer, validate the UBL structure against EN 16931, simulate the Peppol routing, and get back a signed evidence receipt without sending anything to a real buyer.

## When to prefer this

Use this endpoint when you need to test the complete EU e-invoice send pipeline end-to-end in a safe sandbox environment before going live. It is the right choice when you want all compliance checks (VIES, sanctions, EN 16931) plus Peppol routing simulation and a cryptographically signed receipt, all without any real delivery. Prefer it over the standalone invoice creation or eligibility endpoints when you need the full integrated flow in one call.

## Known failure modes

- Invoice object fails EN 16931 UBL validation — returns structured validation errors with field-level detail
- Buyer VAT number fails VIES check — returns invalid/unknown status
- Buyer name matches sanctions list — returns match details and blocks the send simulation
- Invalid or missing transport enum value — returns 400 with allowed values (mock, recommand, e-invoice-be)
- Mode field not set to 'sandbox' — returns error since only sandbox mode is exposed on this endpoint
- Malformed invoice object — returns schema validation error

## How this service works

SANDBOX e-invoice send flow: VIES buyer check + sanctions + EN 16931 UBL create/validate + Peppol/mandate route + sandbox transport (mock, Recommand playground or e-invoice.be test mode; loopback recipient, nothing reaches a real buyer) + Ed25519-signed evidence receipt

## Output

Returns an Ed25519-signed evidence receipt confirming the sandbox send attempt, along with the results of each pipeline stage: VIES VAT check on the buyer, sanctions screening outcome, EN 16931 UBL validation status, Peppol/mandate route decision, and the chosen sandbox transport log. No message reaches a real buyer.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "mode": {
   "enum": [
    "sandbox"
   ],
   "type": "string"
  },
  "invoice": {
   "type": "object"
  },
  "transport": {
   "enum": [
    "mock",
    "recommand",
    "e-invoice-be"
   ],
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/eu-e-invoice-sandbox-send-flow-cf07d156/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.wsystem.dev](https://www.zero.xyz/host/api.wsystem.dev/llms.txt)