---
title: "Add a transaction receipt · Transactions · Practice Manager API · COUNT Partner API"
description: "Adds one receipt holding every file sent, from public URLs or inline base64 content. POST /firm-partners/workspace/transactions/{uuid}/receipts"
canonical: "https://developers.getcount.com/practice-manager/reference/transactions/add-transaction-receipt"
source: "https://developers.getcount.com/practice-manager/reference/transactions/add-transaction-receipt"
---
[Transactions](https://developers.getcount.com/practice-manager/reference/transactions) / Add a transaction receipt

# Add a transaction receipt

POST `/firm-partners/workspace/transactions/{uuid}/receipts`

Adds one receipt holding every file sent, from public URLs or inline base64 content.

Each file is up to 5 MB, the same as the multipart upload. The receipt appears in the transaction's history. On an intercompany transaction it is also copied to the counterpart transaction.

HMAC signature only

[Chart of Accounts API](https://developers.getcount.com/practice-manager/reference/chart-of-accounts) [Bills API](https://developers.getcount.com/practice-manager/reference/bills) [Invoices API](https://developers.getcount.com/practice-manager/reference/invoices)

#### Headers

`count-workspace-id` uuid required

UUID of the client workspace to act on. It must be one of your firm's client workspaces (or the firm's own workspace) and within the API key's client workspaces.

#### Path parameters

`uuid` uuid required

The transaction UUID.

#### Request body

`attachments` array required

The receipt's files. Up to 10 entries; every file is downloaded or decoded and virus-scanned before anything is saved, so one bad file fails the whole request.

`url` string

A public http(s) URL. COUNT downloads the file and stores its own copy, so the link only has to work at the moment you call. Send either `url` or `contentBase64`, not both.

`fileName` string

Required with `contentBase64`. The file name, including its extension.

`contentBase64` string

The file's bytes, base64-encoded (a `data:...;base64,` prefix is accepted). At most 10 MB once decoded, or the route's own cap where that is lower.

`contentType` string

Optional MIME type, e.g. `application/pdf`. Worked out from `fileName` when omitted.

`title` string

Optional display title. Defaults to the file name.

`note` string

A note shown on the receipt.

#### Responses

`201` Receipt added.

`400` A malformed entry (both or neither of `url` and `contentBase64`, a non-http(s) URL, invalid base64), more than 10 files, a file over 5 MB, a type that cannot be attached, or a URL that could not be downloaded. The message names the entry, e.g. `attachments[1]`.

`401` Missing signing headers, an invalid HMAC signature, or a timestamp more than 5 minutes off. [Troubleshoot](https://developers.getcount.com/practice-manager/authentication#errors)

`403` The key is inactive or its scope does not allow this request, the workspace is not managed by your firm or is outside the key's client workspaces, the workspace has no active subscription, or it is portal-only and the route needs bookkeeping. [Troubleshoot](https://developers.getcount.com/practice-manager/authentication#errors)

`404` Transaction not found.

`422` A file was blocked by the virus scan. Nothing was saved.

`429` More than 40 attachment adds a minute for this client and workspace. Retry after the Retry-After header. [Troubleshoot](https://developers.getcount.com/practice-manager/authentication#errors)

[Previous GET List transaction receipts](https://developers.getcount.com/practice-manager/reference/transactions/list-transaction-receipts) [Next POST Upload a transaction receipt](https://developers.getcount.com/practice-manager/reference/transactions/upload-transaction-receipt)

POST `https://api.getcount.com/firm-partners/workspace/transactions/{uuid}/receipts`

Request

```javascript
import crypto from 'node:crypto';

const BASE_URL = 'https://api.getcount.com';
const CLIENT_ID = process.env.COUNT_CLIENT_ID;
const CLIENT_SECRET = process.env.COUNT_CLIENT_SECRET;

const method = 'POST';
const signingPath = '/workspace/transactions/3fa85f64-5717-4562-b3fc-2c963f66afa6/receipts';
const timestamp = Math.floor(Date.now() / 1000).toString();
const body = {
  "attachments": [
    {
      "url": "https://files.example-partner.com/invoices/INV-20481.pdf",
      "title": "Supplier invoice"
    },
    {
      "fileName": "receipt.png",
      "contentType": "image/png",
      "contentBase64": "iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mNkYPhfDwAChwGA60e6kgAAAABJRU5ErkJggg=="
    }
  ],
  "note": "Office groceries"
};
const bodyString = JSON.stringify(body);

const bodyHash = crypto.createHash('sha256').update(bodyString).digest('hex');
const baseString = `${method}:${signingPath}:${timestamp}:${bodyHash}`;
const signature = crypto.createHmac('sha256', CLIENT_SECRET).update(baseString).digest('hex');

const response = await fetch(`${BASE_URL}/firm-partners/workspace/transactions/3fa85f64-5717-4562-b3fc-2c963f66afa6/receipts`, {
  method,
  headers: {
    'x-client-id': CLIENT_ID,
    'x-timestamp': timestamp,
    'x-signature': signature,
    'Content-Type': 'application/json',
    'count-workspace-id': '5e4d3c2b-1a09-4f8e-8d7c-6b5a49382716',
  },
  body: bodyString,
});

console.log(await response.json());
```

Response · 201

```json
{
  "status": "success",
  "message": "Success on adding receipt to the transaction.",
  "data": {
    "receipt": {
      "id": "f2a3b4c5-d6e7-4f8a-9b0c-1d2e3f4a5b6c",
      "note": "Office groceries",
      "images": [
        {
          "id": "a3b4c5d6-e7f8-4a9b-8c1d-2e3f4a5b6c7d",
          "fileName": "FreshMart receipt 2026-11-12.jpg"
        }
      ],
      "createdAt": "2026-01-15T10:30:00.000Z",
      "updatedAt": "2026-01-15T10:30:00.000Z"
    }
  }
}
```
