Documents

Digits automates the accounting process from a file upload:

• Attach receipts to transactions
• Perform automatic reconciliations from a statement
• Create bills to be paid

Upload Documents

To upload a document to Digits, perform a well-formed multipart MIME file upload to the document upload endpoint. Note that this endpoint is hosted at a different subdomain than the Connect API.

Endpoint

POST https://vault.digits.com/document-upload

Authentication

Use an entity-app access token with documents:write in the Authorization header. Vault derives the destination from that token.

https://vault.digits.com/document-upload does not support an entity selector for organization-level tokens. A service-account or organization-app token cannot choose a destination by adding entity.id or JSON metadata. Use a separately authorized entity app for this upload flow. See Authentication.

Request Parameters

Query Parameters:

Headers:

Request Body

The request body must be a multipart MIME upload containing one or both of the following parts:

1. File part (required): The document file to upload

   • Content-Disposition must include filename parameter
   • Only one file is supported per upload
   • Any MIME type is accepted

2. Details part (optional): JSON metadata for document features

   • Content-Disposition name must be details
   • Content-Type must be application/json
   • Body should contain a DocumentUploadDetails JSON object

DocumentUploadDetails Schema

The optional details part accepts a JSON object with the following structure:

{
  "features": [
    {
      "kind": "VendorName",
      "feature_page": 1,
      "text_feature_value": {
        "text_value": "ACME Corporation"
      }
    }
  ]
}

Feature Kinds for document classification include:

• VendorName, VendorAddress, VendorEmail, VendorPhoneNumber, VendorWebsite
• InvoiceId, InvoiceDate, DueDate, TotalAmount
• PayerName, PayerAddress, PayerEmail, PayerPhoneNumber
• Memo, Terms, AccountNumber
• BankStatementLineItem, InstitutionName, InstitutionAccountNumber
• And many more document-specific features

Response

Success (200 OK):

{
  "collection_id": "550e8400-e29b-41d4-a716-446655440000",
  "document_id": "660e8400-e29b-41d4-a716-446655440001"
}

Document Already Exists (304 Not Modified):

Returned when If-None-Match header is provided and the document with matching external-id and content hash already exists.

Example Request

Basic Upload:

curl -X POST "https://vault.digits.com/document-upload?source=Connect" \
  -H "Authorization: Bearer YOUR_CONNECT_ACCESS_TOKEN" \
  -F "[email protected];type=application/pdf"

Upload with Document Features:

curl -X POST "https://vault.digits.com/document-upload?source=Connect" \
  -H "Authorization: Bearer YOUR_CONNECT_ACCESS_TOKEN" \
  -F "[email protected];type=application/pdf" \
  -F 'details={"features":[{"kind":"VendorName","text_feature_value":{"text_value":"ACME Corp"}}]};type=application/json'

Upload with Duplicate Detection:

curl -X POST "https://vault.digits.com/document-upload?source=Connect&external-id=invoice-12345" \
  -H "Authorization: Bearer YOUR_CONNECT_ACCESS_TOKEN" \
  -H "If-None-Match: abc123def456789..." \
  -F "[email protected];type=application/pdf"

Duplicate Detection

To avoid uploading duplicate documents:

1. Include the If-None-Match header with the document's content hash
2. Provide the external-id query parameter
3. If a matching document exists, the API returns 304 Not Modified
4. Otherwise, the document is uploaded normally

Supported Methods

• POST: Upload a new document
• PUT: Upload or replace a document