Musrefy developer platform

A read-only JSON API over the knowledge and listings published on Musrefy: glossary, regulators, international standards, market data with sources, jobs and events.

Request API access Read the documentation

Products

EndpointDescriptionQuery parameters
GET /api/v1/glossaryGlossary Published banking and finance terms in Arabic and English, with their source. q, page, per_page
GET /api/v1/glossary/{slug}Glossary term One published term. —
GET /api/v1/regulatorsRegulators Published regulators and supervisory authorities. country, page, per_page
GET /api/v1/regulators/{slug}Regulator One published regulator. —
GET /api/v1/standardsInternational standards Published standard summaries with the official link (the full text is never hosted). page, per_page
GET /api/v1/standards/{slug}Standard One published standard. —
GET /api/v1/data-seriesData series Latest value of each published market, rate or indicator series, with its source and as-of date. kind, page, per_page
GET /api/v1/data-series/{slug}Data series item Latest value of one series. —
GET /api/v1/jobsJobs Published job listings (public fields only). open, page, per_page
GET /api/v1/eventsEvents Published events (public fields only). upcoming, page, per_page

Getting started

  1. Sign in and send an API access request describing your application and the data you need.
  2. Once the Musrefy team approves it, create a key from your developer page. The key is shown only once: store it securely.
  3. Call the endpoints over HTTPS with your key. Keys can be revoked at any time.

Authentication

Send your key in the Authorization header of every request. Never put keys in public code or URLs.

Authorization: Bearer msk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Limits and pagination

  • Each application has a rate limit per minute (60 by default) shown on your developer page; the X-RateLimit-Limit and X-RateLimit-Remaining headers report it.
  • Lists are paginated with page and per_page (up to 100 per page); the response includes meta and links (first, prev, next, last).
  • Only published records are returned. Data values always come with their source and as-of date, which you must display with them.

Example 

curl --request GET \
  --url https://musrefy.net/api/v1/glossary?q=liquidity \
  --header 'Authorization: Bearer YOUR_API_KEY' \
  --header 'Accept: application/json'
{
  "data": [
    { "type": "glossary-terms", "id": "…", "attributes": { "term": { "ar": "…", "en": "…" }, "definition": { … }, "source": { … } }, "links": { … } }
  ],
  "meta": { "page": 1, "per_page": 25, "total": …, "last_page": … },
  "links": { "self": "…", "first": "…", "last": "…", "prev": null, "next": "…" }
}

Errors

401Missing, invalid or revoked key, or access not approved.
404The record does not exist or is not published.
429Rate limit reached; retry after the number of seconds in the Retry-After header.

{"errors": [{"status": "401", "title": "Unauthenticated", "detail": "…"}]}

Versions

The current version is v1 and is part of every path (/api/v1/…). Breaking changes will only ship in a new version, announced in advance. Platform status

Access, pricing and support

API access is granted on request after review. Commercial terms for higher volumes are agreed with the Musrefy team.

Request API access Contact us