Vladimir Vlasov
12/12/2025, 9:04 PM/api/jobs/search endpoint. When I search for “_product manager_” using the job_title_or parameter, I get results like “_Manager, Dairy Products Quality_” or “_Warehouse Manager - Product Distribution_” because the search matches individual terms rather than the complete phrase.
Is there a way to enforce exact phrase matching on the job_title_or field? Similar to how quoted terms work in Google Search.Kelli Jackson
12/22/2025, 5:16 PMKelli Jackson
12/22/2025, 5:18 PMKelli Jackson
12/22/2025, 5:18 PMIT System
12/23/2025, 8:22 AMSiddhant Bhansali
12/31/2025, 2:13 PMTrisden Mills
02/26/2026, 10:25 PMTom Wetwood
03/03/2026, 12:19 PMJonathan Stone
03/10/2026, 11:45 PMSotirios Gianniris
04/09/2026, 3:33 PMTrisden Mills
04/11/2026, 3:24 PMIgnacio Alarcón Zunino
04/17/2026, 6:45 PMphilip widjaya
04/28/2026, 9:43 AMTrisden Mills
05/05/2026, 10:45 AMPraveen Dissanayake
05/16/2026, 7:42 AMTali Rapaport
06/16/2026, 2:17 AMakhil kundhavaram
06/16/2026, 8:41 PMIgnacio Alarcón Zunino
06/17/2026, 5:52 PMjames.braidley
06/25/2026, 4:49 PMIgnacio Alarcón Zunino
06/29/2026, 4:52 PMAndry Ratovo
07/01/2026, 7:32 AMThomas Davy
07/20/2026, 6:48 PMChris Kirsch
07/24/2026, 7:29 PMnew Date(...).toISOString() vs local-date mismatch. Users at UTC+0 or positive offsets don't see it.
Workaround (for other users hitting this): set the OS timezone to Reykjavik (UTC+0, no DST) or UTC and restart the browser — then clicks land correctly. Or click one day later than intended on both ends.
Suggested fix: handle picker values as timezone-agnostic date-only (e.g. format as YYYY-MM-DD from the local calendar day, or use a date-only type) instead of converting through UTC instants.
Note: there's no manual date-entry field, so the calendar is the only way in — which makes the off-by-one the only path to a wrong range.Chris Kirsch
07/31/2026, 12:31 AMjobs_20260730_234014_720f07f1.xlsx — April 1–30, 2026; reaches 741 rows and then fails, including after multiple retries.
• jobs_20260730_234128_06aa6749.xlsx — May 1–31, 2026; fails at zero rows, including after retry.
• jobs_20260730_235546_9d23de98.xlsx — April 1–15, 2026; reaches 415 rows and then fails.
January–March completed successfully with the same query and XLSX format:
• jobs_20260730_233253_de80217e.xlsx
• jobs_20260730_233640_91889f75.xlsx
• jobs_20260730_233748_38ea9867.xlsx
We began bisecting April to isolate a problematic posting or day. The April 1–8 search then remained loading for more than 90 seconds with Export disabled.
Company Type is Direct employer, with job-title exclusions applied.
We also noticed that changing a displayed date range does not consistently execute the new search until the explicit Search button is clicked.
Please DM me if you need any confidential info to reproduce the error.jonathan.francois018
08/01/2026, 8:29 AMjonathan.francois018
08/03/2026, 8:06 AMSteven Ramenby
08/05/2026, 7:07 PMYolanda_Aye Khin Khin Hpone
08/14/2026, 10:22 AMGET /v0/billing/credit-balance
and it still returns:
api_credits: 200
used_api_credits: 193
So the additional 1,500 paid credits do not appear to have been provisioned to my workspace yet.
Workspace ID: 193604
Invoice: TS-10458
Could someone please check this for me? I’m currently blocked from continuing my API data collection.
Thank you!Salman Ahmed
08/18/2026, 11:44 AMjoao.barbosa
08/18/2026, 2:00 PM