Skip to main content

Why use an SDK?

You can call the Typecast API directly over HTTP, but SDKs are recommended for production code. SDKs wrap repetitive integration work such as authentication headers, request and response types, error handling, streaming handling, and response parsing, so you can integrate more safely and faster than implementing every HTTP call yourself. They also provide higher-level workflows such as text pauses and multi-speaker composition, which are cumbersome to implement with direct API calls alone. Use the SDK that matches where your Typecast API integration will run. If you are starting from a script or prototype, Python is usually the fastest path. For production services, choose the SDK that fits your existing backend or app runtime.
SDKUse when
PythonYou are building scripts, notebooks, data pipelines, backend jobs, or quick API prototypes.
Javascript/TypescriptYou are building Node.js services, frontend tooling, full-stack apps, or browser-compatible integrations.
GoYou need a lightweight backend service, CLI, worker, or concurrent batch process.
RustYou need strong type safety, predictable performance, or a native audio processing pipeline.
C#/.NETYou are building .NET services, Windows tools, Unity apps, or Blazor applications.
JavaYou are integrating with JVM backend systems, Spring services, or Java-first enterprise codebases.
KotlinYou are building Kotlin-first JVM services or Android applications.
C/C++You need native integration, embedded support, FFI bindings, or minimal runtime overhead.
SwiftYou are building iOS, macOS, watchOS, tvOS, or visionOS applications.
ZigYou want a low-level native integration with explicit memory control and no C dependency.
PHPYou are integrating Typecast into Laravel, WordPress, or PHP server-rendered backends.
Dart/FlutterYou are building Flutter mobile, desktop, or web applications.
RubyYou are building Rails apps, Ruby backend jobs, or internal automation scripts.

Utility SDK

SDKUse when
Autotag SDKYou need to preprocess phone numbers, dates, times, amounts, and other structured text so TTS reads it more naturally.