Developer centre

Build with TermHub

Use versioned UK terminology through a server-side API, or keep a database you control current with the automatic SQL sync agent.

Quickstart

Make your first call

Create a credential in API.
Save the one-time API secret, beginning th_live_.
Call source discovery, then search.

curl https://www.termhub.co.uk/api/v1/sources \
  -H "Authorization: Bearer YOUR_API_SECRET"

API contract

OpenAPI reference

Use the canonical contract for endpoint shapes, authentication, response fields and errors.

Open API reference

Download OpenAPI JSON

Automatic SQL delivery

Your database, kept current

Install the customer-operated agent once for PostgreSQL, Microsoft SQL Server or MySQL. It discovers every entitled published release on each scheduled check; TermHub never needs inbound database access.

Access control: every check verifies your subscription. If access ends, new syncs are refused immediately; if access is restored, the installed agent resumes automatically.

Set up automatic sync

Postman

Test locally

Import the collection and environment. Set apiSecret as a local variable; do not sync it to a shared workspace.

Download collection

Download environment

Security

Use the right credential

Key ID (th_key_) identifies a credential. API secret (th_live_) authorises requests.

Keep API secrets in a server-side secret manager, never browser or mobile code.

Search published terminology

curl "https://www.termhub.co.uk/api/v1/search?q=amoxicillin" \
  -H "Authorization: Bearer YOUR_API_SECRET"

Results include code, display, active state, source, release version and release date.

SQL delivery quickstart

Download the TermHub connector and follow the PostgreSQL, MySQL and Microsoft SQL Server setup guide. The connector runs in your environment and does not send database credentials to TermHub.