Banks
Pre-check lists before they hit the Shariah board agenda — exceptions only in the room.
Developer docs · conceptual
Coming Q3 2027Embed screening in your stack.
Bank and fintech-oriented APIs for AAOIFI-aligned screening workflows — auth, rate limits, and example routes shown here are fictional previews only.
Use cases
What institutions plug in
Screening embeds for product engines, wealth platforms, and internal compliance tools.
Fintech
Surface educational compliance cues in apps without claiming auto-certification.
Asset managers
Batch holdings through policy packs aligned to AAOIFI screening themes.
Reference (fictional)
Example routes
Illustrative paths for planning integrations — not callable today.
| Method | Path | Purpose |
|---|---|---|
POST | /v1/screen/holdings | Submit a holdings batch for assistive screening |
GET | /v1/screen/jobs/{id} | Poll job status and flag summary |
POST | /v1/screen/instruments | Single-name activity + ratio snapshot |
GET | /v1/policies | List available policy pack IDs |
These endpoints are examples only. Do not build production clients against them. Final paths, schemas, and SLAs will be published nearer launch.
Onboarding (planned)
How access will work
Enterprise conversations first — then sandbox credentials when the product opens.
1 · Scope
Share your use case (wealth app, bank list, fund ops). We confirm whether screening APIs fit.
2 · Sandbox
When live: test keys, sample payloads, and disclaimer UX requirements in your client.
3 · Production
Tenant credentials, rate plans, and optional human escalation hooks via Baashir review.
Platform concepts
Auth & rate limits
Authentication
Expected pattern: API keys or OAuth-style client credentials per environment (sandbox / production). Keys rotate; never embed secrets in public apps.
- Per-tenant credentials
- Scoped permissions (screen vs admin)
- Audit logs of who called what
Rate limits
Conceptual fair-use ceilings by plan — e.g. requests per minute and holdings per job — to keep screening quality stable for all tenants.
- Burst + sustained quotas
- 429 responses with retry guidance
- Enterprise overrides via contract (when offered)
Outcomes
What you get (when live)
- Screening embed Programmatic access to AAOIFI-aligned flag workflows.
- Docs & sandbox Developer-facing references (published at launch).
- Human escalation hooks Paths to Baashir review when automation is not enough.
- Clear legal posture Assistive outputs; not SFC-licensed advice; waitlist ≠ contract.
FAQ
Common questions
Are these APIs live?
No. Target window is Q3 2027. Example routes on this page are fictional previews.
Can we discuss enterprise access early?
Yes — contact us with your use case. Early talks do not guarantee pricing or dates.
Will the API auto-certify products?
No. Responses assist AAOIFI-aligned workflows. Final Shariah opinions remain human-reviewed where required.
Does joining the waitlist create a purchase contract?
No. It registers interest only and does not guarantee access timing.
Waitlist + enterprise
Register interest, or talk to us about institutional integration needs.