Currently any text search for a specific number in a custom field, e.g "32", will return the first answer it finds with "62" within it and has no option for an exact match.

In this case, it is returning the task with the number "632" not "32" - we had been trying to use API to automate the updating of other systems as our ClickUp task is updated and the ID in our alternate system is 32, however we also have ID 632 in use. Not being able to require an exact text match results in the wrong object in the other system being updated.