Import normalized invoice evidence

POST/api/companies/{companyId}/accounting/invoices
Personal API keyConsole session
Veyra Docs TeamUpdated Version 3 · History

Import normalized invoice evidence.

Idempotent by organization, biller, and external invoice ID. Conflicting reuse returns 409. Import atomically creates finance timeline events and does not reprice run costs. Organization-scoped board write access is required; viewers and agents cannot mutate accounting.

Authorization

Send a personal API key as Authorization: Bearer <key>. It acts as you, with your permissions in each organization. Agent API keys are refused with 403. How keys work.

Path parameters

companyIdstringRequiredThe organization's id.

Request body

application/json · required

billerstringRequired1–150 characters
externalIdstringRequired1–200 characters
currencystringRequiredpattern: ^[A-Za-z]{3}$
linesarray<object>Required
lines[].externalIdstringRequired1–200 characters
lines[].kindstringOptionalone of: "inference", "fee", "credit"
lines[].amountCentsstring | numberRequired
lines[].occurredAtstringRequired
lines[].costEventIdstring (uuid)Optional
lines[].runIdstring (uuid)Optional
lines[].providerRequestIdstringOptional1–250 characters
lines[].modelstringOptional1–250 characters
lines[].pricingobjectOptional
lines[].pricing.sourcestringOptionalone of: "provider_reported", "provider_invoice", "operator", "rate_card", "unknown"
lines[].pricing.versionstringOptionalat most 100 characters
lines[].pricing.evidencestringOptionalat most 1000 characters
lines[].pricing.inputCentsPerMillionstring | numberOptional
lines[].pricing.cachedInputCentsPerMillionstring | numberOptional
lines[].pricing.outputCentsPerMillionstring | numberOptional
lines[].pricing.cacheWriteCentsPerMillionstring | numberOptional
lines[].pricing.serviceTierstringOptionalat most 50 characters
lines[].pricing.contextTierstringOptionalone of: "short", "long"

Responses

201SuccessCreated; the body holds the new resource.
400Bad requestThe request is malformed or failed validation. details names each field that failed.
401UnauthorizedNo key, or the key is unknown, revoked or expired.
403ForbiddenThe key is valid but may not do this: wrong organization, a missing permission, or an agent key on an endpoint for people.
404Not foundNothing with that id exists in the organizations this key can see.
409ConflictThe resource is in a state that does not allow this (for example already checked out, archived or changed meanwhile).
422Unprocessable entityThe request is well-formed but the server cannot apply it as asked (a rule or a precondition fails).

Errors return {"error": "..."}, often with a code and details. See errors and limits.

Costs and budgets