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

Circle Transactions API

The Transactions API from Circle — 12 operation(s) for transactions.

Circle Transactions API is one of 7 APIs that Circle publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 12 operations across 12 paths. It is described by OpenAPI 3.2.0, at version 2026-05-23.

Requests are made against a single base URL, https://api.circle.com.

12 operations 12 paths 0 schemas 4 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-05-23
Base URL
https://api.circle.com/v1/w3s
Authentication
HTTP Bearer
License
Proprietary
Resource Areas
1

Authentication & Security 1

Circle Transactions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Circle API key, formatted as PREFIX:ID:SECRET, supplied as Bearer token.

Paths & Operations 12

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

Transactions 12
GET
/v1/w3s/transactions
List transactions
listTransactions → 200
GET
/v1/w3s/transactions/{id}
Get transaction
getTransaction 1 param → 200
GET
/v1/w3s/transactions/lowestNonceTransaction
Get lowest nonce transaction
getLowestNonceTransaction → 200
GET
/v1/w3s/developer/transactions/feeParameters
Get fee parameters
getFeeParameters → 200
POST
/v1/w3s/developer/transactions/transfer
Create a transfer transaction
createTransferTransaction → 201
POST
/v1/w3s/transactions/transfer/estimateFee
Estimate transfer fee
estimateTransferFee → 200
POST
/v1/w3s/transactions/contractExecution/estimateFee
Estimate contract-execution fee
estimateContractExecutionFee → 200
POST
/v1/w3s/transactions/validateAddress
Validate a blockchain address
validateAddress → 200
POST
/v1/w3s/developer/transactions/contractExecution
Create contract-execution transaction
createContractExecution → 201
POST
/v1/w3s/developer/transactions/walletUpgrade
Create wallet-upgrade transaction
createWalletUpgrade → 201
POST
/v1/w3s/developer/transactions/{id}/cancel
Cancel a transaction
cancelTransaction 1 param → 200
POST
/v1/w3s/developer/transactions/{id}/accelerate
Accelerate a transaction
accelerateTransaction 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

circle-transactions-api-openapi.yml Raw ↑

Other APIs Circle publishes across the network.

Gas Station and Paymaster
Circle NFTs API
Circle Signing API
Circle Tokens API
Circle Wallet Sets API
Circle Wallets API
Where this information came from

This is an independent, third-party profile of Circle Transactions 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.