Create content

post

https://stage-api.findity.com/api/v1/expense/content

Uploads a binary file as a Content resource the client can later attach to an expense record (e.g. as a receipt). The created resource is temporary — owned by the caller and eligible for cleanup if it is not subsequently attached. When action=scan is passed, the OCR result is persisted on the resource so it can be referenced later without re-scanning.

Query Params

action

string

enum

Optional server-side action to run against the uploaded content. scan runs synchronous OCR; the result is persisted on the resource.

Allowed:

organizationId

string

^[0-9a-fA-F]{32}$

Organization scope for the request. Required when the caller has access to more than one organization; auto-inferred otherwise.

Body Params

Headers

Content-Name

string

Optional name for the uploaded content. URL-decoded server-side. Auto-generated if omitted.

Content-Description

string

Optional description for the uploaded content. URL-decoded server-side.

qrScan

string

Optional URL-encoded string extracted from a fiscal QR code on the receipt (currently used for Portuguese receipts). URL-decoded server-side and persisted on the resource; the decoded value is returned in the response and on subsequent reads. Send only when the verification.receiptAttachment field has qrCodeSupported: true (see the fields endpoint) and the client successfully scanned a QR — otherwise omit the header.

content-type

string

enum

Defaults to image/*

Generated from available request content types

Allowed:

Responses

Language

Credentials

Bearer

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201OK

400Error