feat: say in the contacts API reference and the OpenAPI 400 description that a before value on the contact timeline that is not an RFC 3339 timestamp is rejected with a 400 rather than accepted

This commit is contained in:
Matthew Meszaros
2026-09-03 20:28:51 -07:00
parent 2f32b1b8c3
commit 8aaf9e8c8c
2 changed files with 2 additions and 2 deletions
+1 -1
View File
@@ -673,7 +673,7 @@ Auth: **Scope** `READ_CONTACTS` · **Org permission** `view_contacts`
| `id` | path | UUID | Contact ID. |
| `limit` | query | integer | Page size, 1 to 200 (default 50). Anything else is a `400`. |
| `cursor` | query | string | Opaque pagination cursor from `pagination.next_cursor`. A malformed cursor is a `400`. |
| `before` | query | string (RFC 3339 nano) | Deprecated. Returns the events strictly older than this timestamp, which can skip events that share an instant with the page boundary; use `cursor`. Ignored when `cursor` is set. |
| `before` | query | string (RFC 3339 nano) | Deprecated. Returns the events strictly older than this timestamp, which can skip events that share an instant with the page boundary; use `cursor`. A value that is not an RFC 3339 timestamp is a `400`. Ignored when `cursor` is set. |
### Response
+1 -1
View File
@@ -6854,7 +6854,7 @@
}
},
"400": {
"description": "Invalid contact ID, limit or cursor, or no organization selected.",
"description": "Invalid contact ID, limit, cursor or before timestamp, or no organization selected.",
"content": {
"application/json": {
"schema": {