Free halal stock screening API (Akinda free tier)
Akinda's Basic tier is a genuinely free halal stock screening API — 200 calls per day, no credit card. Here's what you get and how to start.

Most developer APIs that offer halal stock screening either require a contract or hide their free tier behind a sales process. Akinda is the exception — the Basic tier is free, self-serve, and lets a developer integrate halal compliance into a side project without any commercial commitment.
What's in the free tier
- 200 API calls per day against the
/compliance/<ticker>endpoint. - 1 GB of data transfer per month.
- US ticker coverage — currently around 5,000 tickers in the catalogue.
- No credit card required — sign up with email or Google.
- Same methodology as paid tiers — the screen doesn't change based on what you pay for.
What it's good for
The free tier is targeted at developers who want to try the API, ship a hobby project, or screen a personal portfolio. 200 calls per day is enough to run a modest watchlist refresh, build a Telegram bot that checks tickers, or wire a halal indicator into a personal Notion dashboard.
When you outgrow it
- You need the financial ratios (debt, liquidity, non-compliant revenue) — those live on
/basic-reportand require the Personal Standard tier. - You need the full AAOIFI screening grid + AI- extracted SEC dollar fields — that's on
/full-report, Personal Ultimate or higher. - You're hitting the rate limit — paid tiers scale to 300 / 2,000 / unlimited calls per minute.
How to start
- Create an account at /signup using email or Google.
- Copy the auto-provisioned API key from /api-keys.
- Fire your first request:
GET https://b2b-api.akinda.io/api/v1/compliance/AAPL?apikey=<key>.
You'll get back a compact JSON verdict — here is the real response for AAPL:
JSON
{"company_name":"Apple Inc.","halal_status":"HALAL","ticker":"AAPL"}The halal_status field comes back as HALAL, NOT HALAL or DOUBTFUL — plus an ERROR_DATA / INCOMPLETE_DATA state when a company's filings aren't available. Authenticate with the apikey query parameter or the X-API-Key header; there is no Authorization: Bearer flow. The verdict itself uses the same AAOIFI-based methodology on every tier — paid plans add the evidence behind it (the three ratios on /basic-report, the full screen on /full-report) and higher limits, not a different screen.
Verify it yourself via the Akinda API
Fire a live /full-report/<ticker> call from the playground using your own API key — see the compliance ratios, AAOIFI screen verdict, and source-breakdown fields the methodology produces.
Related reading