Skip to main content
Avala provides official SDKs and client libraries to help you integrate with the platform from your preferred language or framework. Each SDK wraps the Avala REST API with idiomatic methods, built-in authentication, automatic retries, and full type safety.

Client Libraries

Quick Comparison

FeatureREST APIOpenAPIPythonTypeScript
InstallDirect HTTPCode generationpip install avalanpm install @avala/sdk
AsyncAnyVariesSync + AsyncAsync
Type SafetyN/AGenerated typesFull type hintsFull TypeScript types
Auto RetriesManualVariesYesYes
PaginationManualVariesBuilt-in iteratorsBuilt-in iterators
DependenciesN/AVarieshttpx, pydanticNone (native fetch)

Environment Variables

All SDKs respect the following environment variables, so you can configure them once and use them across your entire stack.
VariableDescriptionDefault
AVALA_API_KEYYour Avala API key for authentication. Used automatically if no key is passed to the client constructor.None (required)
AVALA_BASE_URLOverride the default API base URL. Useful for self-hosted deployments or development environments.https://server.avala.ai/api/v1

Authentication

All requests to the Avala API must include your API key in the X-Avala-Api-Key header. You can find your API key in the Avala dashboard under Settings > API Keys.
export AVALA_API_KEY="your-api-key"
Once the environment variable is set, all SDKs will pick it up automatically without any additional configuration.

MCP Integration

Use Avala with AI assistants like Claude, Cursor, and VS Code through the Model Context Protocol. The @avala/mcp-server package exposes your datasets, projects, and exports as tools that AI assistants can call directly.