Queue one validation

Queues one validation: document_base64 holds the document's bytes, media_type says what they are (the content must agree, as in synchronous validation) and options are the synchronous options. XML at most 5 MiB, a PDF at most 20 MiB; the envelope at most 28 MiB.

Acceptance. Every decision synchronous validation makes before it validates is made now: the document's content and size, the scope, a PDF's inspection and its embedded invoice, and the release latest or the ruleset id resolves to. A document it would refuse is refused here with the same Problem, and nothing is queued or charged. An accepted job is pinned to that release and its engines, and one validation is reserved on the billing account until the job finishes: charged if it reaches a verdict, returned otherwise. A batch is admitted whole or not at all.

Running. The job runs through the same validation as POST /v2/einvoices/validate. Its result is a V2 validation result, read at result_url once the job is completed; its usage and its webhook or S3 event (ironfang/finance/einvoice/event/v2, naming job_id) are a synchronous validation's. An unavailable engine or a timeout is retried, up to 3 attempts; then the job is failed, indeterminate and uncharged. The document is held encrypted until the job finishes, at most 24 hours (expires_at), then erased.

Queue. An organisation holds at most 100 unfinished jobs and 25 MiB of their documents; more is 429 quota_exhausted.

Idempotency. As synchronous validation, with the request identified by the document's bytes, the options and the scope. Keys are V2's own, apart from V1 jobs and from synchronous validation.