Sending documents

Use the send operation for the document type you need, with its send scope and declared idempotency header. Sending, marking as sent, downloading a PDF and submitting to FACe are different operations. A request accepted by the API does not prove that the recipient received the email; inspect the email delivery log.

curl -X POST "https://api.factuarea.com/v1/invoices/$INVOICE_ID/send" \
  -H "Authorization: Bearer $FACTUAREA_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: send-fac-2026-00042" \
  --data '{
  "to": "facturacion@acme.example"
}'

Sender identity

When the sender-identity gate applies, either an active Factuarea subscription or an accepted census identification proves the sender’s identity. Merely entering card details is not the condition read by the service. An absent or unavailable census response does not prove identity; an active subscription remains an alternative.

A rejection uses 422 sender_identity_not_verified. Complete census verification or activate the subscription, then retry the intended send. This guide describes the enforced behavior when the gate is active; availability is determined by the service configuration.

Managed companies and test mode

For a managed company, sender identity is resolved against its accounting firm. The firm must correct the rejected identity; do not ask the managed company to purchase its own subscription. A sandbox company remains subject to test-mode suppression: document email is not delivered to real recipients.

Handle delivery failures

Identity verification does not remove email quotas or other account budgets. A 429 requires the action and retry timing reported by the rate-limit response; repeated immediate retries will not fix it. A validation error requires correcting its field. Preserve request_id when investigating an accepted request with an unexpected delivery outcome. Store autosend_enabled uses the same sending safeguards.