> For the complete documentation index, see [llms.txt](https://docs.nerovasystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerovasystems.com/sdks/readme.md). # Overview Official client libraries for Nerova's public tenant-v1 API contract, built from the same OpenAPI document as the server so they never drift from it. Official client libraries for Nerova's `tenant-v1` API. Nerova is API-first SaaS. Use these server-side SDKs to build your platform's API integration. Each client is built from the same published OpenAPI document: the technical request/response contract for the API. The first release is for Platform accounts serving human medical/clinic, salon/barber, and beauty businesses including nails. Generated symbols do not expand that offer to veterinary or other verticals, vaccination automation, or the retired customer WhatsApp payment flow. See [First-release scope](https://docs.nerovasystems.com/documentation/console/platform-access#first-release-scope); this wording does not remove existing SDK symbols or prove runtime retirement. SDK installation does not grant account access. The [target access policy](https://docs.nerovasystems.com/documentation/console/platform-access) provides private integration docs and credit-funded Testing after platform approval, before a commercial agreement. Existing public packages are not withdrawn by that policy description. ## Available today The .NET, TypeScript, Python, PHP, and Go SDKs are the current clients, built from the published contract, with RFC 9457 problem documents surfaced as typed errors. They are published as preview packages on the shared `0.3.0-preview.2` version line: `Nerova.Sdk` on public NuGet, `@nerova/sdk` on public npm, and `nerova-sdk` on PyPI, where PEP 440 spells the same release `0.3.0b2`. The PHP package `nerova/sdk` on Packagist spells it `0.3.0-beta.2`, and the Go module `github.com/nerova-systems/nerova-sdk-go` uses the tag `v0.3.0-preview.2`. The surface may change before 1.0, so pin the exact version. See [SDK and Postman status](/sdks/available-sdks/client-tools.md) for the exact state of every artifact. * [Use the .NET SDK](/sdks/available-sdks/dotnet.md) * [Use the TypeScript SDK](/sdks/available-sdks/typescript.md) * [Use the Python SDK](/sdks/available-sdks/python.md) * [Use the PHP SDK](/sdks/available-sdks/php.md) * [Use the Go SDK](/sdks/available-sdks/go.md) ## Coming soon Clients for three more languages (Java, Ruby, and Dart) are shipping shortly, built from the same contract. No package is published yet for these languages. The [SDK roadmap](/sdks/coming-soon/roadmap.md) states plainly what ships for each language and what is not yet claimed. Until the roadmap announces availability, use the .NET, TypeScript, Python, PHP, or Go SDK, or call the REST API directly following the [developer documentation](https://docs.nerovasystems.com). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nerovasystems.com/sdks/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.