So, I've been using the Braintrust platform for a few months now, mostly to pull job market data into my analytics dashboards via their API. The new UI refresh that just rolled out is definitely slick—much cleaner and easier on the eyes. Big fan of the visual upgrade!
But here's my immediate problem: it completely broke all my deep links and bookmarks. 😅 I had a whole organized system in Chrome with saved links to specific search filters and talent pool pages that I use as references for my API calls. Now they all just redirect to the main dashboard.
For example, my bookmark to a filtered search for "Python" & "API Integration" roles in "San Francisco" used to look like this:
` https://app.braintrust.com/find-talent?skills=python%2Capi-integration&location=San+Francisco`
Now it just dumps me at the homepage. This is a bit disruptive for my workflow.
**My questions for the community:**
* Is anyone else running into this with saved links or integrations?
* More importantly, has anyone figured out the new URL pattern? I need to reconstruct my bookmarks.
* For the API-savvy folks: Have the underlying API endpoints changed, or is this purely a front-end routing shift? My scripts are still running... for now.
I'm hoping the old patterns just have a new equivalent path and I can update my links. Otherwise, I'll have to rebuild my whole reference system. The new look is great, but stability for power-users is key!
The broken bookmark issue is a classic side effect of a frontend routing change without proper URL migration or backward compatibility. I've seen this happen when teams switch from query parameters to a path-based structure, or move to a client-side routing framework that doesn't handle legacy URL patterns.
Your API scripts are likely unaffected if they call the backend directly. The key question is whether they introduced new API versioning or deprecated the endpoints your bookmarks' state represented. Check for a `v2` in the path or a new OpenAPI spec. If your scripts rely on scraping the authenticated frontend instead of direct API calls, then your problem is much larger.
You'll need to inspect the network traffic while using the new UI to reverse-engineer the pattern. Look for the API calls the page makes when you manually re-create your filter. That will give you the new canonical source for your data pulls and possibly reveal the new URL schema.