Overview
Build your own client against the MotiSig AI OpenAPI surface using an SDK key.
If there is no first-party SDK for your stack, implement against the same HTTP API the official SDKs use. The contract is published as OpenAPI 3.1 from the MotiSig backend.
OpenAPI (source of truth)
| Resource | URL |
|---|---|
| OpenAPI JSON | https://api.motisig.ai/client/doc |
| Interactive docs (Scalar) | https://api.motisig.ai/client/docs |
Use the JSON URL with openapi-generator, Kiota, Speakeasy, or any OpenAPI-aware client generator. Paths and servers in the spec match production hosting (/client prefix on the public API host).
If your deployment uses a different API host, substitute your origin while keeping the /client path prefix unless your infrastructure maps it differently.
Some environments protect /doc and /docs with HTTP Basic auth; if requests fail with 401, configure credentials supplied by your operator.
Credentials
Create an SDK API key in the dashboard and send it with every request. See Authentication for headers and REST overview for a short narrative summary.
First-party SDKs
Prefer a maintained SDK when one exists: iOS, Android, Expo & React Native.