Client libraries
Official SDKs and framework integrations — what's available now, what's on the roadmap, and how to integrate today.
The ShadhinPay API is plain REST over HTTPS, so you can integrate from any language or framework today using a standard HTTP client. Official client libraries — which wrap authentication, signature verification, retries, and typed models — are on the roadmap.
REST works everywhere, right now
You don't need to wait for an SDK. Every guide in these docs uses raw HTTP, and the pages below show the idiomatic way to call ShadhinPay from each ecosystem until the official library ships.
Roadmap
| Library / framework | Status | Guide |
|---|---|---|
| Node.js / TypeScript | Planned | Node.js |
| PHP / Laravel | Planned | PHP & Laravel |
| Python | Planned | Python |
| WordPress / WooCommerce | Planned | WordPress |
| Flutter / Dart | Planned | Flutter |
Statuses move from Planned → Beta → Stable as each library lands. This page is the index — each row links to a guide that shows how to integrate from that ecosystem today and tracks the official library's progress.
Node.js / TypeScript
Integrate from a Node backend.
PHP & Laravel
Integrate from PHP or a Laravel app.
Python
Integrate from Django, FastAPI, Flask, or scripts.
WordPress
Plans for a WooCommerce plugin.
Flutter / Dart
Plans for mobile checkout.
Want a library we haven't listed?
Tell us which language or framework you're building on — demand shapes the roadmap. Reach out from your dashboard's support channel.
What an official library will handle for you
When the SDKs land, they'll wrap the cross-cutting concerns you'd otherwise build yourself:
- Attaching the
Client-Id,Business-Id, andX-Api-Keyheaders - Generating and reusing idempotency keys on retries
- Webhook signature verification
- Typed request/response models and error handling
- Sane retries with backoff for transient failures
Until then, the API conventions page documents each of these so you can implement them directly.