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

LegendTrade Wallets API

Wallet registration for fill tracking (authenticated).

LegendTrade Wallets API is one of 5 APIs that LegendTrade publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 5 operations across 5 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 0.1.0.

Requests are made against a single base URL, https://api.legend.trade.

5 operations 5 paths 1 schemas 1 DELETE1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.1.0
Base URL
https://api.legend.trade
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

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

  • bearerAuth — The /wallets/ endpoints are authenticated — unauthenticated requests return 401 {"error":"Unauthorized"}. Legend does not publish the credential format for thi…

Paths & Operations 5

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

Wallets 5

Wallet registration for fill tracking (authenticated).

POST
/wallets/register
Register a wallet for fill tracking
registerWallet body → 200401
POST
/wallets/bulk
Bulk register wallets
bulkRegisterWallets body → 200401
POST
/wallets/sync
Sync all wallets from Postgres to cache
syncWallets → 200401
GET
/wallets/stats
Get wallet sync stats
getWalletStats → 200401
DELETE
/wallets/{address}
Unregister a wallet
unregisterWallet 1 param → 204401

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (1 property). Each schema is shown below with its type and property counts.

Error
object
Legend's error envelope — a single error string.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

legendtrade-wallets-api-openapi.yml Raw ↑

Other APIs LegendTrade publishes across the network.

Legend WebSocket API
LegendTrade Health API
LegendTrade Info API
LegendTrade Market Data API
Where this information came from

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