Official SDKs
Choose an SDK for your language and find installation steps, requirements, and public API examples.
The official SDKs connect your application's backend to the Raims public API. Each guide covers requirements, installation, configuration, creating charges, pagination, errors, and webhook verification.
Choose an SDK
Use the guide for your backend language. Installation channels vary by SDK:
| Language | Guide | Distribution |
|---|---|---|
| C# and .NET | .NET SDK | NuGet, Raims package |
| PHP | PHP SDK | Packagist, raims/raims-php package |
| Go | Go SDK | Go module on GitHub |
| Java | Java SDK | Maven Central, com.raims:raims-java |
| Python | Python SDK | PyPI, raims package |
| Node.js and TypeScript | Node.js SDK | npm, @raimshq/raims package |
| Ruby | Ruby SDK | RubyGems, raims gem |
| Elixir | Elixir SDK | Hex, raims package |
| Rust | Rust SDK | crates.io, raims crate |
| Delphi | Delphi SDK | Source code in GitHub releases |
Read the guide before installing to check language versions, dependencies, and platform requirements. To update, follow the same guide and review the release notes for the version you choose.
Prepare your integration
Keep your API key on the server. Do not include it in code delivered to browsers, mobile apps, or your customers' desktop applications. Obtain the credential in API keys.
The validated credential determines the company, environment, and permissions.
Sandbox and Production use https://api.raims.com; the SDK does not change the
key's environment. Start with a Sandbox key and review the conditions in
Authentication.
The SDKs preserve the API rules: monetary amounts in cents, dates in UTC Unix
seconds, pending HTTP 202 results, and application-supplied idempotency. Check
the API reference for each operation's fields and conditions.