available: false to available: true as they ship).
Request
Endpoint
- Production
- Staging
https://v3-api.cleargrid.ai/admin/v3Headers
Bearer token obtained from the Lender Login endpoint. Format:
Bearer <access_token>.Path parameters
Your lender public ID. Must equal the
lenderId encoded in the JWT, otherwise the request returns 403.Example request
Response
- 200 — Success
- 403 — Lender mismatch
All five sections (
S1–S5) and all 25 dataset codes are returned. Phase 1 datasets carry available: true; Phase 2 and reserved datasets carry available: false.Response fields
HTTP status code, mirrored in the body.
200 on success.Human-readable result message.
Version anchor for the catalog response shape. Currently
"v1". Additive changes (new fields, new datasets) stay on v1. Breaking changes — if and when they happen — will land at a new endpoint path (/exports/v2/...) so existing pipelines keep working unchanged.Array of section objects.
Always an empty array on success.
Use cases
- Boot-time discovery — fetch once and build a client-side allowlist of
(section, dataset)pairs whereavailable: true. - Periodic re-check — fetch on a schedule (e.g. weekly) to detect datasets that have been newly activated for your tenant.
Need Help?
Our support team is available Monday-Friday, 9 AM - 6 PM GST. Reach out at support@cleargrid.co or visit our help center.