---
title: "Deleted Records · Practice Manager API · COUNT Partner API"
description: "Read the records removed from a workspace outright since a point in time, so an integration syncing with `updatedSince` can delete them on its side too."
canonical: "https://developers.getcount.com/practice-manager/reference/deleted-records"
source: "https://developers.getcount.com/practice-manager/reference/deleted-records"
---
Practice Manager API

# Deleted Records

Read the records removed from a workspace outright since a point in time, so an integration syncing with `updatedSince` can delete them on its side too.

Last updated 2026-11-18

## Overview

GET /firm-partners/workspace/deleted-records is the deletion half of incremental sync. List endpoints return records created or changed since `updatedSince`, but a record removed from the database outright no longer exists to be listed — this feed is where its id shows up instead.

Records that are only marked deleted are not here: the list endpoints return them with `includeDeleted=true`, each with `isDeleted: true`. See the Keeping in Sync guide for the full polling loop.

## Key concepts

### Paging and the next poll

Records come back oldest deletion first. Pass `nextUpdatedSince` back as `updatedSince` while `hasMore` is true; once it is false, store `nextUpdatedSince` and send it on the next poll. Keep this cursor separate from the cursors you store for each list endpoint.

### Journal entry lines

Editing a journal entry replaces its lines. The old line ids appear here as `journal_entry`, and the new lines appear on GET /firm-partners/workspace/journal-entries with `updatedSince`.

### 90-day window

Deletions are kept for 90 days. An `updatedSince` older than that returns 410 Gone, because earlier deletions may already be gone from the log: run a full load of each list endpoint again and read deletions from the time you started it.

## Deleted record

#### Attributes

`id` uuid

The id the record had on its list endpoint. Remove the record with this id from your copy.

`resourceType` enum

What kind of record was removed.

One of: `account`, `bill`, `budget`, `customer`, `customer_address`, `customer_contact`, `customer_note`, `expense_receipt`, `invoice`, `journal_entry`, `person`, `product`, `project`, `recurring_invoice_template`, `tag`, `tag_group`, `task`, `tax`, `time_entry`, `transaction`, `vendor`

`deletedAt` datetime

When it was removed (ISO 8601, UTC).

Example

```json
{
  "id": "b2c3d4e5-f6a7-8901-bcde-f23456789012",
  "resourceType": "tag",
  "deletedAt": "2026-11-18T08:14:02.000Z"
}
```

Scope and permissions

Needs the `workspace:read` scope. The connecting user needs any one of the view permissions (`view_transactions`, `view_invoices`, `view_bills`, `view_journal_entries`, `view_customers`, `view_vendors`, `view_accounts`, `view_products_services`, `view_projects`, `view_tasks`, `view_people`, `view_receipts`, `view_budgets`). Only resource types the app's grant can read are returned — for example `invoice` rows need `invoices:read`.

MCP equivalent

COUNT_list_deleted_records, with the same parameters under `query`. It is not offered inside COUNT AI chat.

## Related

- [Keeping in sync guide](https://developers.getcount.com/guides/keeping-in-sync)
- [Webhooks API](https://developers.getcount.com/practice-manager/reference/webhooks)
- [Journal Entries API](https://developers.getcount.com/practice-manager/reference/journal-entries)

## Endpoints

[GET List deleted records `/firm-partners/workspace/deleted-records` Returns the records removed outright since a point in time, oldest first.](https://developers.getcount.com/practice-manager/reference/deleted-records/list-deleted-records)
