Lists deleted records
Lists records that have been deleted, so a copy kept in sync through this API can remove them. Results are sorted by DeletedOn ascending, then type id, then id, using cursor pagination.
Each record appears once, with its latest deletion; this is not a history. A record restored in the Gorelo app leaves this feed and appears in its normal list again. DeletedOn is the deleted record’s last update, so it can move later if the deleted record is edited.
A contact is listed here when it was deleted, and also when its client was deleted, since GET /v1/contacts stops listing a deleted client’s contacts. Such a contact’s DeletedOn is the later of the contact’s and the client’s last update. In the same way, a task is listed when it was deleted and also when its project was deleted, with the later of the task’s and the project’s last update.
An invoice is listed when it was deleted. A voided invoice is not deleted: it is still returned by GET /v1/invoices.
A record with no recorded last update has no deletion time and is not listed.
Each type needs read access on its own scope: clients Clients, contacts Contacts, contracts, items and invoices Billing, tickets Tickets, custom assets Assets, projects and tasks Project. Asking for a type the key cannot read is a 403 with code 070208 on TypeIds.
Autorizações
Your Gorelo API key. See Generate API key. If your data is hosted in Australia, click the base URL at the top of this page and select https://api.aue.gorelo.io.
Parâmetros de consulta
Required. Comma-separated record types to include: 1 Client, 2 Contact, 3 Contract, 4 Ticket, 5 Item, 6 Invoice, 7 Custom asset, 8 Project, 9 Task, 10 Agent asset. Up to 10 values; any other value is a 400.
ISO-8601 UTC timestamp; keeps only deletions at or after it.
Opaque pagination cursor from a previous page; omit for the first page.
Number of items per page, 1-200 (default 50). Out of range is rejected, not clamped.
Resposta
OK
100, 101, 102, 103, 200, 201, 202, 203, 204, 205, 206, 207, 208, 226, 300, 301, 302, 303, 304, 305, 306, 307, 308, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 421, 422, 423, 424, 426, 428, 429, 431, 451, 500, 501, 502, 503, 504, 505, 506, 507, 508, 510, 511 The DataContext of a cursor-paginated success response: carries the paging metadata
for the returned page.