Added `ext_id` filtering to Jobs API + normalized future publish timestamps

Table of contents

New ext_id filter on /api/jobs/

The /api/jobs/ endpoint now supports filtering by ext_id (external job ID). This allows direct lookup of listings by source-specific identifier and helps avoid errors caused by unsupported query parameters. Supported usage includes single values, multi-value filters, and exclusions:

• ext_id=62140064
• ext_id=62140064|6524216002
• ext_id=62140064|-6524216002

See endpoint docs: /c/jobs-api-endpoint-documentation/

Future publish timestamps now normalized at import

We fixed an issue where some job listings could appear with a publish date in the future. From now on, newly imported listings are automatically normalized so their publish date can never be later than the current UTC time.

This means customers will no longer see future-dated jobs in API responses, resulting in a more reliable chronological feed.

This behavior is now standardized across all supported import sources. Listings with future timestamps are still accepted when otherwise valid, but their publish date is adjusted to the current UTC time at import, preventing incorrect future visibility while preserving listing availability.