SDKs and API artefacts
Generate typed clients for your published APIs in five languages, track releases and download OpenAPI and Postman files.
Updated 7 Oct 2026
On this page
SDKs for the Nexra platform itself
To call Nexra (integrations, runs, connections, approvals) from your code, use an official SDK for TypeScript, Python, Go, C# and .NET or Java. This page is about client code for the APIs you publish.
Two ways to get client code
| Instant artefacts | Managed SDK pipeline | |
|---|---|---|
| Who | Anyone, for public API products | Workspace members, for your workspace's products |
| How | API reference → Download, or GET /api/developer-portal/public/catalogue/:slug/artifacts/:format | Dashboard → SDKs, the CLI or POST /api/developer-portal/sdk/generate |
| Formats | OpenAPI, Postman, TypeScript, Python, Go, C#, Java | TypeScript, Python, Go, C#, Java |
| Extras | None | Jobs, checksums, compatibility checks and release channels |
Supported targets
All targets are beta.
| Language | Runtime | Package name |
|---|---|---|
| TypeScript | Node.js 20+ | @amakora/nexra-<product> |
| Python | Python 3.10+ | amakora-nexra-<product> |
| Go | Go 1.22+ | github.com/amakora/nexra-<product> |
| C# | .NET 8+ | Amakora.Nexra.<Product> |
| Java | JDK 21+ | com.amakora.nexra.<product> |
Each artefact is a single client source file (NexraClient.ts, nexra_client.py, nexra_client.go, NexraClient.cs or NexraClient.java) generated from the published OpenAPI 3.0 or 3.1 document.
Generate an SDK in the console
Open Dashboard → SDKs.
Choose the API product, version, language and environment. Production SDKs need an application whose production access is approved.
Generate. The job moves through queued, generating and succeeded (or failed).
Download the artefact. Downloads carry an X-SDK-SHA256 header; verify it before use.
Optional: run a compatibility check between two API versions, then create a release on the preview or stable channel. Releases can later be deprecated, quarantined or retired.
Requirements:
the product belongs to your workspace and is published;
the version is not retired;
every operation in its OpenAPI document has an operationId.
Current limitations
Generated clients leave full schema models, automatic pagination and retries to your own code.
Packages are not published to npm, PyPI, NuGet, Maven or Go proxies; releases are recorded in Nexra's internal registry and downloaded from the console.
Bundled software bills of materials are placeholders.
From the command line
See Nexra CLI.
Connect a provider account across interfaces
See Connect through MCP, APIs, CLI and SDKs for account setup, exact operation selection, authentication, copyable examples, sandbox boundaries and approval troubleshooting.