> For the complete documentation index, see [llms.txt](https://docs.tiny.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiny.plus/api/changelog.md).

# Changelog

Changes to the API that an integration might notice, newest first. Dates are when a change reached production.

## 20 November 2026

* **Table views.** [`GET /v2/table_views?for={type}`](https://docs.tiny.plus/api/endpoints/table-views.md) lists the saved views a person has of a record type's table in tiny+: their own, the ones shared with them and the standard ones, each with its columns, its sort and its filters in words. `view={id}` on a list request returns the records that view lists, in its order, and other parameters narrow it further. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) lists `table_views` in `api_features`.
* **Bulk actions.** New requests change several records at once, as ticking rows in a table does: set a status, add or remove tags, assign, put on a list, follow, add a task to each, archive or delete. [`GET /v2/bulk?for={type}`](https://docs.tiny.plus/api/endpoints/bulk-actions.md) lists what the person may do, `POST /v2/bulk/{action}` runs it on up to 25 records and says what changed and what was left, and `POST /v2/bulk/undo` puts a run back. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) lists `bulk` in `api_features`.
* **A dashboard list on a saved view.** A dashboard's list panel can be set, in tiny+, to list one of the person's saved table views. In [`GET /v2/dashboards/{id}`](https://docs.tiny.plus/api/endpoints/dashboards.md#one-dashboard) such a panel carries `view` (`id` and `name`) and its `more_url` opens the table on that view; where the view is gone or not shared with the person, the panel has no rows and a `note`.

## 17 November 2026

* **Enquiries.** An enquiry read carries an `enquiry` object: how it came in, whether it is held, its reply clock (`reply_due`, `first_reply` and `reply`: `waiting`, `late` or `replied`), why it was closed, what it became, and the tiny+ AI engine's one-line `summary`, with the `draft_reply` on a single read. New requests do what the enquiry's page does: `POST /v2/enquiries/{id}/assign`, `/replied`, `/convert` (with a `GET` for its choices), `/undo`, `/close` (with a `GET` for the reasons and phases), `/release` and `/draft`. Enquiries have three new read-only fields: `source`, `source_detail` and `received`, with `source_form` for one from a web form. `GET /v2/enquiries?inbox=1` lists the ones nobody has yet. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) lists `enquiries` in `api_features`. See [Enquiries](https://docs.tiny.plus/api/endpoints/enquiries.md).
* **Enquiries marked Check.** The `enquiry` object carries `suspect` and `suspect_why`. Where the tiny+ AI engine finds something in an enquiry it would not rely on, `suspect` is `true`, `summary` and `draft_reply` are `null`, and an emailed enquiry is held for review.
* **Who gets a new enquiry.** A `POST /v2/enquiries` with no `assigned_user` used to leave the enquiry unassigned. It now goes where the account's rule says: the Inbox (still unassigned), one person, or each of a group in turn, and that person is notified. An enquiry whose `contact_email` belongs to exactly one contact is linked to that contact and their company. A create that repeats a `remote_id` answers with the first enquiry's id.
* **Web forms for enquiries** moved to `https://forms.tiny.plus/e/{key}`, with an embed script and, on the Pro plan, a post address for a website's own form. The old `/submit/` addresses pass visitors on. See [Capturing website enquiries](https://docs.tiny.plus/api/getting-access/javascript-token.md).
* **Contact Lookup** (invite only for now). In accounts we've invited, tiny+ can fill in a contact from the web: their job title, photo, a short bio and LinkedIn profile, and any email, mobile or direct line, for a person to check and apply. Where an account has switched it on for new contacts, a contact added through `POST /v2/contacts` at a company with a website is looked up too. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) says whether it's on, in `contact_lookup`, which is `false` for every other account. There, AI assistants get `look_up_contact`, and, where the account allows changes, `apply_contact_lookup`. Contacts in every account have a new field, `bio`. See [AI assistants](https://docs.tiny.plus/api/getting-access/ai-assistants.md) and the [Contact Lookup guide](https://docs.tiny.plus/guides/everyday/contact-lookup.md).

## 12 November 2026

* **A project sheet's other projects.** A project sheet read from `/v2/project_sheets` carries `other_projects`: the projects it covers beside `parent_project`, each an `id` and a `name`, left out where the token's user may not see the project. Write it as a list of project ids (or a comma list) to set them; projects no longer named are unlinked, and leaving the key out changes nothing. These are the sheet's relationships with projects, so `with_related` shows the same links. See [Records](https://docs.tiny.plus/api/endpoints/records.md).
* **A fee as a percentage of the construction value.** A fee template's and a fee option's `percent_of` may be `value_rate`: the fee is `percent_of_rate` percent of the project's construction value, and percentage lines are shares of that fee. `POST /v2/packs` takes `percent_of_rate` to start a proposal at another percentage than its template's. `percent_of` may also be `project_fee`: percentage lines are shares of the fee set on the project when the proposal was started, which the option keeps in `percent_of_amount`. See [Fee proposals](https://docs.tiny.plus/api/endpoints/packs.md#fee-proposals) and [Fee templates](https://docs.tiny.plus/api/endpoints/fee-templates.md).

## 11 November 2026

* **Connect.** [`GET /v2/connect`](https://docs.tiny.plus/api/endpoints/connect.md) is the board of who to contact this week and why, in four reason columns, read as the token's user or for a team or person they may choose. [`GET /v2/connect/{contact_id}`](https://docs.tiny.plus/api/endpoints/connect.md#one-person) gives one person's last contact, recent contact, who knows them, open tasks and proposals. `POST /v2/connect/{contact_id}/log` logs contact with them, and `POST` and `DELETE /v2/connect/{contact_id}/later` put a card away, drop its reason, or bring it back. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) lists `connect` in `api_features`.
* **Posts logged as contact with a person.** `POST /v2/updates` takes `log_type`, `log_date` and `log_next` on a post about a contact: the post is logged as a call, a meeting or other contact with them on that day, and a follow-up day books a task, returned as `task_id`. A logged post reads back with `touch_log`. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) lists `log_activity` in `api_features`. See [Logging contact with a person](https://docs.tiny.plus/api/endpoints/updates.md#logging-contact-with-a-person).
* **A saved email is contact.** An email saved against a contact with [`POST /v2/emails`](https://docs.tiny.plus/api/endpoints/emails.md) now counts as being in touch with them, on the day it was saved, wherever tiny+ shows when someone was last contacted, [Connect](https://docs.tiny.plus/api/endpoints/connect.md) included.
* **People to contact on dashboards.** A new panel, the top of the Connect board, arrives in [`GET /v2/dashboards/{id}`](https://docs.tiny.plus/api/endpoints/dashboards.md#one-dashboard) as kind `attention`, so a client that draws Needs attention draws it too.
* **Submission packs.** New endpoints open a project's pack, shape it (the ask, which sheets and CVs go in and in what order, the statement), rank the account's sheets and CVs against the ask, queue a build and fetch the PDF or Word file it makes: [`/v2/packs`](https://docs.tiny.plus/api/endpoints/packs.md). Packs come with the Pro plan's submission packs, which an account admin turns on under Account Settings → Submissions; [`/me`](https://docs.tiny.plus/api/endpoints/me.md#integrations) says whether they're on, in `integrations.submissions`. A pack names its `cover` sheet, from the set an account admin keeps, and may give it a `cover_image` of its own. It is drawn in the account's default layout, or one an account admin approved for packs (`layout`). The list takes `kind`: `pack` (the default), `fee_proposal` or `all`.
* **Fee proposals.** A pack of kind `fee_proposal` is a priced proposal: a letter, the scope by stage, a fee of one or more options with lines by stage (lump sums, percentages of the construction value, time charges at a rate card's rates, provisional allowances and exclusions), the programme and the terms, with the sheets and CVs chosen as for a pack. `POST /v2/packs` opens one from a fee template with `kind`, `template`, `bid_team` and `headline`; it reads with a `proposal` block whose figures come both as stored and as the document prints them; `PATCH` takes its words, `scope`, `terms`, the primary option as `fee` with its `lines`, and `restart`. Its first build writes the fee to the project, its stages or its bid team. [`GET /v2/fee_templates`](https://docs.tiny.plus/api/endpoints/fee-templates.md) and [`GET /v2/rate_cards`](https://docs.tiny.plus/api/endpoints/fee-templates.md#rate-cards) read what a proposal starts from. The MCP server gets `get_fee_proposal`. A proposal's `style` is `proposal` or `letter`, a fee letter with no cover and the sheets and CVs enclosed after it; a fee template has a `style` too. See [Fee proposals](https://docs.tiny.plus/api/endpoints/packs.md#fee-proposals).
* **CVs and capability statements.** Two new record types for accounts with submission packs, a Pro plan feature an account admin turns on under Account Settings → Submissions: [`/v2/cvs`](https://docs.tiny.plus/api/endpoints/cvs.md), one team member's experience for submissions, with the projects it names in order and each one's role (`notable_projects`: tiny+ projects by id, or ones from a previous firm by name, client and year), and [`/v2/capability_statements`](https://docs.tiny.plus/api/endpoints/capability-statements.md), the firm's approved statements, whose approval is stamped. A CV belongs to the person it is about: records admins and the new Submissions role read every one. Project sheets gain `summary`, `value_band`, `completion_year`, `client_id`, `size`, `awards` and `approved_for_external` (records admins only), and carry categories.

## 31 October 2026

* **Muted records.** A record read on its own says whether you've muted it, in `muted_by_me`: you still follow it, but its posts and changes don't notify you. People mute a record beside Unfollow on the web. See [Records](https://docs.tiny.plus/api/endpoints/records.md).

## 30 October 2026

* **Dashboards.** [`GET /v2/dashboards`](https://docs.tiny.plus/api/endpoints/dashboards.md) lists the token user's dashboards in their order, [`GET /v2/dashboards/{id}`](https://docs.tiny.plus/api/endpoints/dashboards.md#one-dashboard) gives one as rows of panels with each panel's data (tiles, lists, the pipeline strip, Meetings & tasks, Needs attention, Key dates and the rest), read with the dashboard's scope of whose records and which period, and `POST /v2/dashboards/{id}/scope` keeps that choice. Dashboards are laid out on the web; the API reads them.
* **No more Twitter Handle.** Companies, contacts and team members no longer have a `twitter` field: it isn't in `GET /v2/fields`, `GET /v2/form_structure` or the records' reads. See [Companies](https://docs.tiny.plus/api/endpoints/companies.md), [Contacts](https://docs.tiny.plus/api/endpoints/contacts.md) and [Team members](https://docs.tiny.plus/api/endpoints/team-members.md).

## 28 October 2026

* **A stage's fee is in its project's currency.** On accounts that use more than one currency, `GET /v2/stages` returns `stage_fee_value_currency`, the project's fee currency, and `stage_fee_value_entered`, the fee as it was sent; `stage_fee_value` is the amount converted into the account's currency, as a project's `fee_value` is. A write that sends `stage_fee_value_currency` has it ignored. See [Stages](https://docs.tiny.plus/api/endpoints/projects.md#stages).
* **A post's website card.** A post that shares a web page carries `has_link`, `link_url`, `link_url_formatted` (the host), `link_title`, `link_description` and `link_image` in [`GET /v2/updates`](https://docs.tiny.plus/api/endpoints/updates.md#the-news-feed-or-a-search), as the News Feed already did. See the [field reference](https://docs.tiny.plus/api/endpoints/updates.md#field-reference).
* **A project's dates follow its stages.** On accounts with stages, a project's `expected_start_date`, `expected_finish_date` and `expected_duration` are the span of its stages, its `lock_fields` names them, and an update that sends them leaves them as they are. See [Stages](https://docs.tiny.plus/api/endpoints/projects.md#stages).

## 23 October 2026

* **Company Lookup.** When someone adds a company, tiny+ can find its website, phone, email, address, logo, a one-line description and tags on the web, for a person to check and apply; a company added through `POST /v2/companies` is looked up too. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) says whether it's on, in `company_lookup`. AI assistants get `look_up_company`, and, where the account allows changes, `apply_company_lookup`. See [AI assistants](https://docs.tiny.plus/api/getting-access/ai-assistants.md) and the [Company Lookup guide](https://docs.tiny.plus/guides/everyday/company-lookup.md).
* **AI assistants can read lists.** The MCP server has `list_lists` (the lists the token's user can see, target lists first, or the lists a record is on) and `get_list` (one list with its summary and a page of its members), and, where the account allows changes, `create_list` and `add_to_list`. They are there when the account shows Lists in its menu, as `integrations.lists` on [`/me`](https://docs.tiny.plus/api/endpoints/me.md#integrations) says. See [AI assistants](https://docs.tiny.plus/api/getting-access/ai-assistants.md) and [Lists](https://docs.tiny.plus/api/endpoints/lists.md).

## 15 October 2026

* **Bid teams.** New endpoints read the competing teams a project is bid through, each led by another firm, and the teams under a lead firm with its two numbers, and add, change and remove them. A team's result moves its project: a win wins it, and the last team out of the running closes it. Bid teams come with the Pro plan, and an account admin turns them on under Account Settings → Projects; [`/me`](https://docs.tiny.plus/api/endpoints/me.md#integrations) says whether they're on, in `integrations.bid_teams`. The MCP server's `get_record` lists a project's teams. See [Bid teams](https://docs.tiny.plus/api/endpoints/bid-teams.md).
* **While a project has a bid team in the running, its fee and probability come from its teams.** A `PATCH /v2/projects/{id}` that sends `fee_value` or `probability` for it leaves them as they are. See [The fee and probability](https://docs.tiny.plus/api/endpoints/bid-teams.md#the-fee-and-probability).

## 11 October 2026

* **A list chooses each company's key contact.** On a list of companies, [`PATCH /v2/lists/{id}/members/{record_id}`](https://docs.tiny.plus/api/endpoints/lists.md#key-contacts) takes `key_contact_id`, and a member's `key_contact` is the one the list names, or else its first current contact by name, as before. [`GET /v2/lists/{id}/members/{record_id}`](https://docs.tiny.plus/api/endpoints/lists.md#one-member) is new: one member, with the company's current contacts to choose from. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) lists `list_key_contacts` in `api_features`. A confidential contact the token's user can't see is no longer given as the key contact, or counted in `other_contacts`.
* **A record read on its own names its people:** `assigned_user_record`, `created_user_record` and `modified_user_record`, named even after they leave the team, and `subscribers` lists its followers, each with `id` and `name`, where it used to be `null`. See [Get a record](https://docs.tiny.plus/api/endpoints/records.md#get-a-record).
* **A post names the people who like it:** `social.likers`, each with `id` and `name`, beside `like_ids`. See [Comments](https://docs.tiny.plus/api/endpoints/updates.md#comments).
* **`/me` says whether the account shows Support Docs:** `permissions.support_page`, for the account in use and for each of `extra_accounts`. See [Current user](https://docs.tiny.plus/api/endpoints/me.md#permissions).
* **More image types.** [`POST /v2/attachments`](https://docs.tiny.plus/api/endpoints/attachments.md#images-and-documents) stores WebP, AVIF, BMP, HEIC, TIFF and SVG files as images, converted to JPEG, or to PNG when the picture has transparency. They used to be kept as documents.

## 4 October 2026

* **Lists.** New endpoints read the account's lists of companies, contacts and projects, their members and a record's lists, and add, remove, comment, follow, make, change and delete. A personal list is only there for the person who made it. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) lists `lists` in `api_features`, and says in `integrations.lists` whether the account shows Lists. See [Lists](https://docs.tiny.plus/api/endpoints/lists.md).
* **A record's lists carry their comments.** Each list in [`GET /v2/lists?record_id={id}`](https://docs.tiny.plus/api/endpoints/lists.md#the-lists-a-record-is-on) has `comment`: what that list says about the record, or `null`.
* **`/me` says whether the person is an account admin:** `permissions.account_admin`, for the account in use and for each of `extra_accounts`. Only an account admin can set `created_user`, `modified_user`, `created_date` or `modified_date` to anything but their own. See [Current user](https://docs.tiny.plus/api/endpoints/me.md#permissions).

## 3 October 2026

* **A time zone field lists its zones.** In `GET /v2/fields/staff` and `GET /v2/form_structure/staff`, `timezone` has `options`: the zones tiny+ offers, each with a `value` and a `label`, such as `{"value": "Australia/Sydney", "label": "(UTC+10:00) Sydney, Canberra"}`. See [Time zone](https://docs.tiny.plus/api/endpoints/team-members.md#time-zone).
* **A time zone has to be one.** Setting `timezone` to anything but a zone name, such as `Australia/Sydney`, gets a `400`, and nothing is saved. It used to be saved as sent.
* **Time zones are stored under their current names.** A team member or an account on an old name now reads the current one in `/me` and `GET /v2/staff`: `Asia/Kolkata` rather than `Asia/Calcutta`, `Australia/Sydney` rather than `Australia/Canberra`. Those on `Etc/Greenwich`, which tiny+ offered as Dublin, read `Europe/Dublin`, with Irish summer time.

## 2 October 2026

* **Relationship plans.** New endpoints list, start, log and change relationship plans, on accounts with the Pro plan. [`/me`](https://docs.tiny.plus/api/endpoints/me.md#integrations) says whether an account has them, in `integrations.relationship_plans`. See [Relationship plans](https://docs.tiny.plus/api/endpoints/relationship-plans.md).
* **Tasks say which plan they belong to, and when they were completed:** `plan_id`, `plan_step_id`, `plan_occurrence`, `touch_type`, `completed_date` and `completed_user`. See [Tasks](https://docs.tiny.plus/api/endpoints/tasks.md#follow-ups-on-a-relationship-plan).
* **Companies say where their plans stand:** `plan_status`, `plan_next_due`, `plan_next_staff`, `last_contact_date` and `plan_count`. A company on a plan has its health worked out from its last contact on the plan. See [Companies](https://docs.tiny.plus/api/endpoints/companies.md#relationship-plans).
* **A post that holds a plan follow-up's notes carries `plan_touch`.** See [Posts](https://docs.tiny.plus/api/endpoints/updates.md#notes-logged-on-a-relationship-plan).
* **Fields that tiny+ keeps itself are left out of a write, not written.** A create or an update that sends one, such as `record_url`, saves the rest and names it in `ignored_fields`. See [Records](https://docs.tiny.plus/api/endpoints/records.md#fields-that-are-not-editable).
* **A project's status pipeline:** [`GET /v2/status_history/projects/{id}`](https://docs.tiny.plus/api/endpoints/projects.md#status-pipeline) returns the states a project has been in, where it is now and for how long, and what comes next, as its Status panel shows them.
* **A record's images and documents:** [`GET /v2/attachments?related_id={id}`](https://docs.tiny.plus/api/endpoints/attachments.md#images-and-documents-on-a-record) lists them, and [`GET /v2/attachments/{id}`](https://docs.tiny.plus/api/endpoints/attachments.md#open-a-document) gives a short-lived link that opens a document. An image attached through `POST /v2/attachments` is listed straight away.
* **`linked_to={id}`** on a list returns the records linked to another record, as a record's panels in tiny+ find them. [`/me`](https://docs.tiny.plus/api/endpoints/me.md) lists it in `api_features`. See [Listing, filtering and paging](https://docs.tiny.plus/api/concepts/listing.md#records-linked-to-another-record).
* **Meeting times come back in UTC.** `meeting_date` and `meeting_date_end` used to come back in Australia/Sydney time, though they are sent and filtered in UTC. See [Meetings](https://docs.tiny.plus/api/endpoints/meetings.md).
* **A meeting sent without `record_status` is `planned`.** It used to have no status, so no panel in tiny+ listed it.
* **A meeting's `primary_related` can be a project.** A project's id used to be dropped, leaving the meeting unlinked.

## 1 October 2026

* **`GET /v2/search/{type}` searches only that type.** For a type the tiny+ search box leaves out, such as `stages`, it used to search every other type instead and return their records. The MCP server's `search_records` tool did the same. See [Search](https://docs.tiny.plus/api/endpoints/records.md#search).
* **`GET /v2/search/updates` leaves out the posts a** [**search on `GET /v2/updates`**](https://docs.tiny.plus/api/endpoints/updates.md#the-news-feed-or-a-search) **does:** posts tiny+ writes automatically, confidential notes, and posts on a confidential record the token's user can't open. It used to return posts on such a record, with their opening words. It is the search [Ask](https://docs.tiny.plus/api/endpoints/ai-filter.md) falls back to for posts, and the MCP server's `search_records` tool uses it too. See [Search](https://docs.tiny.plus/api/endpoints/records.md#search).

## 30 September 2026

* **Setting who made a record, or when, needs an account admin.** Only an account admin can send `created_user`, `modified_user`, `created_date` or `modified_date`. Anyone else who sends one gets a `403`, unless the value is their own id or the one the record already has. See [Permissions](https://docs.tiny.plus/api/concepts/permissions.md).
* **`DELETE` answers `{"results": true}`**, or `false` if the record couldn't be deleted.
* **A simple access token works only for the account it was made in.** Sending another account's id as `account` gets `403 {"error": "This token is for account N only."}`, and a token whose creator has left the account gets a `401`. Account admins can now revoke a simple access token on the API Access screen. See [Simple access token](https://docs.tiny.plus/api/getting-access/getting-an-access-token.md).
* **Only a post's author, or a News Feed admin, can edit or delete it.** Every post's `perm_edit` and `perm_delete` now say whether the token can. See [Posts](https://docs.tiny.plus/api/endpoints/updates.md).
* **`GET /v2/updates?single_id=`** finds any post the token's user could see on a feed, not only posts on the News Feed.
* **Posts and comments check what they're attached to.** A comment on a post the token's user can't open, or a post whose `related_id` or `extra_ids` they can't see, gets a `404`, and nothing is saved. A comment that can't be saved gets a `500`, rather than `200 {"id": false}`.
* **Attaching a file needs edit rights on the record.** [`POST /v2/attachments`](https://docs.tiny.plus/api/endpoints/attachments.md) answers `403` for a record the token's user can't edit, and for a read-only token, and `400` for a confidential record they can't see, as for a missing one. Its errors are `{"error": …}` objects now, and `image/bmp`, `image/tiff` and `image/svg+xml` are kept as documents rather than failing.
* **`sort` on `GET /v2/updates`** takes `created_date`, `modified_date`, `name` or `id`. Anything else is ignored.
* **A confidential company's name is hidden** on the projects and contacts linked to it, from people who can't see the company.

## 29 September 2026

* **Ask can search posts.** [`POST /v2/ai/filter`](https://docs.tiny.plus/api/endpoints/ai-filter.md) with `"flavour": "updates"` returns `text`, `about` and `broadcast` filters for `GET /v2/updates`.
* **Confidential records stay confidential in the API.** Lists and searches leave out the confidential records the token's user can't open, a direct read masks them, and their history is refused. See [Permissions](https://docs.tiny.plus/api/concepts/permissions.md).

## 28 September 2026

* **Fixed:** [`POST /v2/webhooks/add`](https://docs.tiny.plus/api/endpoints/webhooks.md) works again. From 25 September it answered `500`.

## 14 September 2026

* **AI assistants can use tiny+** through its MCP server at `https://api.tiny.plus/mcp`. See [AI assistants](https://docs.tiny.plus/api/getting-access/ai-assistants.md).
* **Apps can register themselves** with `POST /oauth/register`. See [Register a Client App](https://docs.tiny.plus/api/getting-access/register-a-client-app.md).
* **Ask filters.** [`POST /v2/ai/filter`](https://docs.tiny.plus/api/endpoints/ai-filter.md) turns a plain-English question into filters for a list.

## 30 August 2026

* **The v1 API is closed.** Requests to `/api/v1`, which used `?token=`, now answer `404`. Use `/v2` with an [access token](https://docs.tiny.plus/api/getting-access.md).
* **`/me` has a `permissions` object,** with `show_fees` and `all_records`. See [Current user](https://docs.tiny.plus/api/endpoints/me.md).
* **Pipeline statistics were rebuilt.** [`GET /v2/stats/projects`](https://docs.tiny.plus/api/endpoints/stats.md) groups each status's figures by phase, covers every status, and takes the same `me`, `staff`, tag and custom-field filters as a project list. `/all` needs permission to see the company-wide pipeline, and fee figures are `null` when the account hides fees.
* **Lists can be filtered on more kinds of custom field:** date, number, currency, percentage and URL, as well as text and yes/no. A custom-field filter that can't be applied answers `400`, rather than returning the list unfiltered.
