How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

thirdweb Engine API

Backend transaction execution with server wallets.

thirdweb Engine API is one of 9 APIs that thirdweb publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Engine. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 3 paths. It is described by OpenAPI 3.2.0, at version 1.22.

Requests are made against 4 base URLs: https://api.thirdweb.com, https://engine.thirdweb.com, https://insight.thirdweb.com, https://nebula-api.thirdweb.com.

4 operations 3 paths 0 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.22
Base URL
https://api.thirdweb.com
Authentication
API Key, API Key, API Key, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 4

thirdweb Engine API declares 4 security schemes for authenticating requests. An API key is passed in the header as x-client-id (ClientAuth). An API key is passed in the header as x-bundle-id (BundleIdAuth). An API key is passed in the header as x-secret-key (SecretKeyAuth). It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • ClientAuth — Client ID for frontend usage. Web sends x-client-id only; native apps also send x-bundle-id.
  • BundleIdAuth — Bundle ID for native (desktop/mobile) platform authentication alongside x-client-id.
  • SecretKeyAuth — Secret key for backend usage; never expose publicly.
  • BearerAuth — JWT access token obtained from wallet authentication, for frontend usage.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Engine 4

Backend transaction execution with server wallets.

POST
/v1/write/contract
Write to a contract via Engine.
engineWriteContract body → 200
POST
/v1/read/contract
Read from a contract via Engine.
engineReadContract body → 200
GET
/v1/accounts
List Engine server wallets.
engineListServerWallets → 200
POST
/v1/accounts
Get or create an Engine server wallet.
engineGetOrCreateServerWallet body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

thirdweb-engine-api-openapi.yml Raw ↑

Other APIs thirdweb publishes across the network.

thirdweb Authentication API
thirdweb Contracts API
thirdweb Insight API
thirdweb Nebula API
thirdweb Payments API
thirdweb Tokens API
thirdweb Transactions API
thirdweb Wallets API
Where this information came from

This is an independent, third-party profile of thirdweb Engine API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.