SDKs

Glytos is a plain REST API described by OpenAPI, so every language works. The most common starting points have hand-written SDKs - one for the browser and five for the server - plus a CLI for your terminal; everything else is either a generated client or a plain HTTP call, and both are first-class.

Which one

The web SDK is for one job: talking to an agent from a browser, by voice or as text. It never sees your API key.

The Node, Python, PHP, .NET and Go SDKs are for your backend. They expose the same resources under the same names, in each language's own casing, so pick the one your stack already speaks: threads for text conversations, calls and phoneNumbers for voice, and the rest of the platform either way. Helpers differ in places - for example PHP, .NET and Go have say, transfer and end shortcuts for a live call, while Node and Python reach the same actions through calls.control(...). The CLI wraps the same API for your terminal and CI.

The server SDKs and the CLI send your key in the X-API-Key header, and take an environment option that becomes the X-Environment-Id header - see Organizations.

Any other language

Two ways, both supported.

Generate a client

Point any OpenAPI generator at the spec. The published document declares no security scheme, so a generated client will not add authentication by itself - configure it to send the X-API-Key header on every request.

openapi-generator-cli generate \
  -i https://api.glytos.com/api/v1/openapi.json \
  -g java \
  -o ./glytos-java

openapi-generator-cli generate \
  -i https://api.glytos.com/api/v1/openapi.json \
  -g ruby \
  -o ./glytos-ruby

openapi-generator-cli generate \
  -i https://api.glytos.com/api/v1/openapi.json \
  -g rust \
  -o ./glytos-rust

Just call it

The API is small enough that a generated client is often more machinery than you need. An X-API-Key header and JSON is the whole protocol - see Authentication for the same call in eight languages.