API

What you can call

• Regulation comparisonSide-by-side ABS frameworks across countries
• Ease-of-ABS scoringPer country, or per competent national authority
• Compliance assessmentAn organization's public ABS posture, with quoted evidence
• Clearing-House lookupsLive ABS, Biosafety and focal-point records from api.cbd.int

Getting started

1. 1. Create an organization in the app, then issue a key under Workspace → API keys.
2. 2. Copy it immediately — the raw key is shown once, at creation. Only its hash is stored, so it cannot be recovered.
3. 3. Call GET /api/v1/me with an X-API-Key header to confirm the key works and see what your plan includes.

API access is the white_label_api capability, included with Enterprise. Every other tier reaches the same services through the web app. /v1/me and /v1/usage work with any valid key regardless of plan, so you can always check where you stand.

Limits and errors

Calls are metered per organization per calendar month. GET /v1/usage reports every meter and what remains; a null limit means unlimited, not zero.

Spending an allowance returns 429 with a Retry-After header, not 403 — you are entitled to the call, just not any more this period, so retrying later is the correct response.

What these responses are, and are not

Regulation and ease-of-ABS responses are Gleanloop's own curation and scoring — not a live government feed, and not legal advice. Fields that carry a caveat, such as abs_ch_is_country_wide_proxy, are part of the contract rather than decoration: they exist so you do not read more precision into a number than the underlying data supports. Verify against the ABS Clearing-House before acting on any of it.

Reference

Full interactive reference, with every endpoint, parameter and response schema:

Open the API reference →