openapi: 3.0.1 info: title: thirdweb Authentication Transactions API description: thirdweb provides a unified interface for Web3 development. This specification documents real, publicly documented HTTP endpoints across the thirdweb unified API (api.thirdweb.com - wallets, transactions, contracts, tokens, payments and bridge), Engine (backend transaction execution), Insight (indexed on-chain data) and Nebula (AI blockchain interface). Authenticate frontend usage with an x-client-id header (plus x-bundle-id for native apps) or a Bearer JWT, and backend usage with an x-secret-key header. termsOfService: https://thirdweb.com/tos contact: name: thirdweb Support url: https://thirdweb.com/support version: '1.22' servers: - url: https://api.thirdweb.com description: thirdweb unified API (wallets, transactions, contracts, tokens, payments, bridge) - url: https://engine.thirdweb.com description: thirdweb Engine (backend transaction execution) - url: https://insight.thirdweb.com description: thirdweb Insight (indexed on-chain data) - url: https://nebula-api.thirdweb.com description: thirdweb Nebula (AI blockchain interface) security: - SecretKeyAuth: [] - ClientAuth: [] - BearerAuth: [] tags: - name: Transactions description: Transaction submission and status. paths: /v1/transactions: get: operationId: listTransactions tags: - Transactions summary: List transactions. responses: '200': description: A list of transactions. post: operationId: sendTransactions tags: - Transactions summary: Send a batch of transactions. requestBody: required: true content: application/json: schema: type: object responses: '200': description: Transactions queued. /v1/transactions/{transactionId}: get: operationId: getTransaction tags: - Transactions summary: Get a transaction by ID. parameters: - name: transactionId in: path required: true schema: type: string responses: '200': description: Transaction details. content: application/json: schema: $ref: '#/components/schemas/TransactionResult' components: schemas: TransactionResult: type: object properties: transactionId: type: string transactionHash: type: string chainId: type: integer status: type: string description: Queued, submitted, mined, or errored. securitySchemes: ClientAuth: type: apiKey in: header name: x-client-id description: Client ID for frontend usage. Web sends x-client-id only; native apps also send x-bundle-id. BundleIdAuth: type: apiKey in: header name: x-bundle-id description: Bundle ID for native (desktop/mobile) platform authentication alongside x-client-id. SecretKeyAuth: type: apiKey in: header name: x-secret-key description: Secret key for backend usage; never expose publicly. BearerAuth: type: http scheme: bearer bearerFormat: JWT description: JWT access token obtained from wallet authentication, for frontend usage.