June was a month of fixing things that were quietly costing people time. Two of them affected paid customers directly, so if you noticed your API feeling slower than it should, or got the same usage email twice, this is why, and it's sorted.

Rate limits improvements

If you were on a paid plan, your API key might get incorrect rate limits. We've corrected that. There's nothing to change on your side. Your existing API keys picked up the correct limit as soon as the fix went out.

Usage alerts

We email you when you reach 75% and 100% of your monthly API quota so nothing stops working without warning. Alerts now follow your real billing cycle. One email per milestone, per cycle, whatever date your plan renews on.

Every SDK shipped an update

All four OMOPHub clients moved forward this month:

Client	Version
Python SDK	1.8.1
R SDK	1.8.1
Node.js / TypeScript SDK	1.0.3
MCP Server	1.5.2

One address for semantic search. Semantic search now lives at /v1/search/semantic in every SDK, which is where it should have been all along. The old address still works and always will, so nothing breaks if you're running an older version. You'll just see a deprecation note in the response headers.

Corrected sort options in the Node.js SDK. TypeScript was suggesting sort values the API doesn't actually accept, so a perfectly reasonable-looking line of code came back as a validation error. The suggestions now match reality across vocabulary listings, vocabulary concepts, and basic search.

Consistent identification. Python, R and Node.js now identify themselves to the API in the same format. That sounds cosmetic, but it means our support team can tell which SDK and version a request came from when you write in with a problem.

Also in June

Clearer FHIR resolver errors. When semantic search is briefly unavailable, the FHIR-to-OMOP resolver now says so plainly instead of returning a generic failure, so you can tell a temporary outage apart from a code that genuinely has no match.
A proper sign-in error page. Sign-in problems now land on a real OMOPHub page explaining what happened, rather than a bare error screen.
Security and dependency updates across the API, the dashboard and all four SDKs.

Links

Something not working the way you expect? Open an issue or reach out from the dashboard, we read everything.