Overview
typeship's own SDKs for its API, in TypeScript, Python, and Go. Generated by typeship from its own spec, so each is also a sample of what your users get.
typeship drives its own API through the packages it generates for itself. Each is built from the same OpenAPI spec by the same engine that generates your packages, and each has the shape every SDK typeship generates in that language: zero runtime dependencies, typed payloads and errors, auto-pagination, retries, hooks, and validation. If you want to see what your users will get before you generate anything, read one of these.
| Language | Package | Install |
|---|---|---|
| TypeScript | typeship-ax on npm, which also carries the typeship CLI and the typeship MCP server | npm install typeship-ax |
| Python | typeship on PyPI | pip install typeship |
| Go | github.com/typeship-ax/go | go get github.com/typeship-ax/go |
All three take an API key from the console under api keys, call the same seventeen operations, and read the same snake_case payloads. What differs is the idiom: TypeScript returns ApiResult, Python raises, Go returns (T, error). The SDK platform pages describe each idiom in full; the pages here cover what is specific to typeship's operations.
The packages live in the typeship repository under packages/typeship-sdk, packages/typeship-python, and packages/typeship-go, regenerated from the spec on every change.