Correct contact search date filtering and operator docs - #625
Merged
Conversation
adisan19
marked this pull request as ready for review
August 19, 2026 12:52
VarshSuresh
approved these changes
Aug 19, 2026
The single_filter_search_request.operator enum falsely implies != is valid for every field type, and omits >= / <= which work on integer/float fields. Both are type-blind facts an OpenAPI enum can't express structurally (fields are dynamic, including custom attributes), so the enum stays a flat superset of all valid operators and the description now states validity per field type, including the date-field exception (=, IN, NIN, <, > only; !=, <=, >= 400). Also corrects the SearchContacts endpoint's "Searching for Timestamp Fields" and "Accepted Operators" prose to state the day-truncation and >-matches-next-day rule explicitly, and to generalize the created_at-only <=/>= admonition to all Date fields plus !=. Applied identically across all versions (2.7-2.16, Preview/0) since the operator/type validation is shared search infrastructure, not gated by public API version.
Production QA on the contact search date filters showed two things the previous wording got wrong: unsupported operators return 422, not 400, and version 2.16 places a contact's value in a day using the workspace timezone, not UTC (the UTC anchoring is gated on a change that has not been released). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…ate docs Preview now filters standard contact timestamps on the exact second and accepts !=, >= and <= on them, while Date custom attributes stay whole-day and reject those three. Verified in production on 2026-08-19. Also drops IN and NIN from the documented date operators, since they are not usable on date fields.
The five lines rendered as one wall of text, since consecutive markdown lines join into a single paragraph. Splits it into short paragraphs with a bulleted operator list and a labelled example, and normalises the wording that had drifted between versions.
tag_id takes only = and !=; IN, NIN and the string-match operators all return invalid_operator. The shared schema description grouped it with plain string fields, which contradicted the endpoint table.
adisan19
force-pushed
the
adisanarula/contacts-search-date-operator-docs
branch
from
August 19, 2026 13:47
3e567ab to
71921b5
Compare
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
adisan19
enabled auto-merge (squash)
August 19, 2026 15:43
VarshSuresh
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
The contact search docs describe date filtering incorrectly. They list operators that actually return a 400 error, leave out two that work, and never mention that a date value is cut down to a whole day, which makes
>look like it skips a day.How?
Rewrites the timestamp section and the operator table in every version to say which operators each field type accepts, and what day truncation does to the comparison results.
Generated with Claude Code