Overview
Choose an SDK and integrate Insion easily with your tech stack.
Insion SDKs provide idiomatic, typed access to the same moderation, records, users, and appeals API. Each language guide documents its actual client surface installation, authentication, configuration, errors, and every supported operation so start by choosing the runtime used by your application.
Choose your language
TypeScript
A typed client for TypeScript and JavaScript applications.
Python
Synchronous and asynchronous clients for Python services.
Java
A Java client for JVM applications and backend services.
Ruby
An idiomatic Ruby client for Rails and Ruby applications.
Go
A context-aware Go client for services and workers.
C#
An asynchronous .NET client with cancellation support.
PHP
A PHP client for web applications and server-side workflows.
Swift
A Swift-concurrency client for Apple-platform applications.
Rust
An asynchronous Rust client with generated builders and models.
What every SDK lets you do
All clients authenticate with an Insion bearer token and expose the same core capabilities. The method names, request builders, async model, and error types vary by language, so use the relevant language guide for exact code and types.
| Capability | Use it when you need to |
|---|---|
| Moderate a record | Create or update content and receive a moderation decision immediately. |
| Ingest a record | Submit content for asynchronous moderation and consume the outcome through webhooks. |
| Manage users | Create or update users, list them, and inspect their moderation action state. |
| Retrieve and list | Query stored records and users using Insion IDs, filters, and cursor pagination. |
| Create appeals | Submit an appeal for an eligible suspended user when appeals are enabled. |
Integration path
- Choose the appropriate SDK, follow its installation and client-creation instructions.
- Configure a bearer token and, where needed, timeouts, retry behavior, custom headers, or a custom HTTP client.
- Choose synchronous moderation when the caller needs the outcome now; choose ingestion when your webhook flow handles the result later.
- Store both your own stable
clientIdand Insion's returned resourceid. They serve different purposes across creation, deletion, retrieval, and pagination. - Implement the error-handling guidance in the selected SDK before putting requests on a user-facing or background-processing path.
Use the API instead?
For endpoint semantics shared across languages, including request/response behavior and webhook integration, use the API reference.