> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sandpay.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Available SDKs

> Which SDK for which language, and the roadmap

SandPay maintains one official SDK per language. Full list with current statuses:

| SDK         | Status             | Installation               |
| ----------- | ------------------ | -------------------------- |
| **Node.js** | Available — v0.3.0 | `npm i @drwintech/sandpay` |
| **curl**    | Always available   | *(no installation)*        |
| **Python**  | Planned Q2 2026    | —                          |
| **PHP**     | Planned Q2 2026    | —                          |
| **Java**    | Planned Q3 2026    | —                          |
| **Go**      | Planned Q3 2026    | —                          |

## Common conventions

Regardless of which SDK you use:

* Bearer auth (`Authorization: Bearer sp_sk_test_...`) — see [Authentication](/en/authentication).
* Typed errors with `status`, `code`, `message`, `requestId` properties — see [Errors](/en/errors).
* Webhook signature verification via a dedicated helper — see [Webhooks](/en/webhooks).
* Strict types mapped to the [OpenAPI 3.1](/en/api-reference/overview) spec.

## No official SDK for your language?

You can talk directly to the HTTP API — it's designed to be trivially easy to integrate in \~30 lines of code in any language with an HTTP client.

<Note>
  Writing a community SDK (Ruby, Rust, Elixir, Kotlin…)? We'd love to hear about it — open an issue on [github.com/htleclerc/sandpay](https://github.com/htleclerc/sandpay) or write to [support@sandpay.dev](mailto:support@sandpay.dev). We can list your SDK here, provide an official repo, or take over maintenance depending on your preference.
</Note>

## See also

* [Node SDK — complete reference](/en/sdks/node)
* [API Reference](/en/api-reference/overview)