SDKs
Language SDKs that wrap the Ours Privacy Ingest API for Node.js, Python, Go, Ruby, PHP, C#, and Kotlin.
SDKs
Prefer not to call the REST API directly? The Ours Privacy ingest SDKs wrap every endpoint in this section. All send to the same Ingest API and authenticate with the same source API key, and all are described by one OpenAPI specification.
Available SDKs
| Language | Best for | Docs |
|---|---|---|
| Node.js / TypeScript | Backend services and Node automation | Node.js SDK |
| Python | Backend services and data pipelines | Python SDK |
| Go | Go services and infrastructure tooling | Go SDK |
| Ruby | Rails and Ruby backends | Ruby SDK |
| PHP | PHP applications | PHP SDK |
| C# | .NET applications | C# SDK |
| Kotlin | Kotlin and JVM backends | Kotlin SDK |
| OpenAPI spec | Generating your own client in any language | OpenAPI Schema |
For install snippets and a feature comparison across every SDK family — including client and platform SDKs — see the Ingest SDKs hub and the SDK Overview.
When to Pick Which
- Writing application code? Use the SDK that matches your stack. Each is typed where the language supports it and tracks the OpenAPI spec.
- High-volume replay or backfill? Send through the
/batchendpoint, which every SDK supports. - Need a language we don't ship yet? Generate a client from the OpenAPI spec.
Next Steps
- Ingest SDKs hub — install snippets for each language.
- Authentication — create the source key the SDKs need.
- Quickstart — the same operations against the raw REST API.
How is this guide?