API Reference

The full Veda Console API surface is described by an OpenAPI 3 specification. The interactive Swagger UI is the source of truth for request and response schemas, parameter shapes, and the list of supported endpoints.

OpenAPI / Swagger

Open the interactive Swagger docs →

• Swagger UI: api.veda.tech/docs

• OpenAPI JSON: api.veda.tech/openapi.json

• Version: 1.0.0

You can use the OpenAPI spec directly to generate clients in your language of choice (openapi-generator, oapi-codegen, openapi-typescript, etc.), drive contract tests, or import into Postman / Insomnia.

Base URL

https://api.veda.tech

Authentication

All endpoints are authenticated with an API key passed as a Bearer token:

Authorization: Bearer veda_user_live_...

API keys are created in the Veda Console — see Quick Start.

Rate limits & timeouts

• Rate limit: 60 requests per minute, per API key. When you exceed the limit, the API returns 429 Too Many Requests — back off with exponential delay and retry.

• Request timeout: 30 seconds for most endpoints. Build endpoints (/execute, /execute-multiple) with simulation enabled can take significantly longer. Pass skip_sim: true when you don't need a Tenderly simulation — it's the most common way to get faster responses.

If you need a higher limit for a production workload, reach out to your Veda contact with the expected request volume.

Conventions

• JSON only. All requests and responses are application/json unless noted otherwise.

• Errors use a detail envelope — either a string or { "error": "...", "details": "..." }. See Error handling for the common cases.

• Chain slugs are lowercase (ethereum, base, arbitrum, etc.). See Chain Support for the full list.

• Addresses are EIP-55 checksummed in responses; lowercase or checksummed is accepted on request.

• Amounts in request bodies are in the token's display units (e.g. 1000 means 1,000 USDC, not 1,000 wei).

Versioning

The Veda API uses major versions in the URL path. Every endpoint sits under a /v{N}/ prefix. The current major version is v1.

Deprecations

Endpoints or fields slated for removal in a future major version are marked as deprecated in the OpenAPI spec and announced in the Change Log with at least 30 days' notice. During the deprecation window, calls succeed and the response includes a Deprecation header pointing to the replacement.

Pinning a version

Always pin the version explicitly in your client (/v1/...). Don't rely on host-level redirects from an unversioned path — they're not guaranteed and may change.