Improve Close Reason List Validation
about 1 month ago
closeReason.listnow uses schema-backed request validation, returning clearerinvalid_inputmessages when fields are malformed.
closeReason.list now uses schema-backed request validation, returning clearer invalid_input messages when fields are malformed.source.list now uses schema-backed request validation, returning clearer invalid_input messages when fields are malformed.jobBoard.list now uses schema-backed request validation, returning clearer invalid_input messages when fields are malformed.archiveReason.list now uses schema-backed request validation, returning clearer invalid_input messages when required fields are missing or malformed.approval.list for Offer approvals so filtering by a later offer version ID can return the active approval process when that approval is attached to an earlier version of the same offer.excludeFormDefinition boolean parameter (defaults to false) to offer.info, offer.create, offer.update, offer.startApprovalProcess, and offer.approve. When set to true, the formDefinition field is omitted from the response, which can substantially reduce payload size for orgs with many selectable values on offer custom fields.interviewSchedule.cancel now uses the same schema-backed request validation as other recently updated Public API endpoints, returning clearer invalid_input messages when required fields are missing or malformed.project.search now returns more detailed validation messages when required search parameters are missing or invalid.syncToken) on paginated list endpoints such as application.list and candidate.list are now limited to a maximum number of pages. If the limit is exceeded, the API returns an incremental_sync_too_large error. Clients that receive this error should discard their current syncToken and perform a full sync instead.candidate.list createdAfter filter now compares against the candidate's added-at timestamp (COALESCE(added_at, created_at)), matching the field shown in the Ashby UI as "Added At" and the existing sort order on this endpoint.