We've introduced a new and improved Jobs API endpoint, /search/jobs, which replaces the current /jobs endpoint.
The new endpoint should be near drop-in replacement, supporting the same parameters and the same results, but with improved performance, especially for larger projects and complex filters.
The old endpoint is now considered deprecated and will be removed some time in the future (will be announced separately).
A major difference is that the new endpoint returns results from a secondary database, which is synchronized with a slight delay.
This means a new job may not be shown right away after it's created and job detail may contain slightly outdated data if it was updated recently. The delay should be couple seconds at max during normal operation.
Other difference is the new endpoint will return maximum 500 items per page.
See the Job Queue API documentation for more details.