Contracts and environments

Edel Markets has three network environments. Devnet is available for development; Testnet and Mainnet are coming soon. Keep endpoints, credentials and account identifiers within the same environment.

Use https://dev.edel-api.xyz for Devnet REST requests. The Testnet and Mainnet REST hostnames are listed below for configuration planning; a published hostname does not mean that trading or funding is available. Testnet and Mainnet have not launched. Keep the environment selected in the REST console aligned with your credentials.

OpenAPI defines REST endpoints, authentication requirements, request fields, responses and errors. AsyncAPI defines WebSocket channels, message envelopes and payloads. Use these schemas to generate client types and validate incoming data.

Choose versions compatible with your target environment, and check each operation’s availability and account permissions. Unsupported CCXT methods return HTTP 501 NotSupported.

Generate REST types from OpenAPI and realtime types from AsyncAPI. Validate received data before applying it to account or market state, and retain the schema version used by each client release.

Requests and responses. Check required fields, response alternatives and error values when upgrading a client.

Realtime messages. Check subscription envelopes, channel access, payload schemas and replay behavior.

Environment and access. Use credentials and identifiers for the chosen environment, then confirm supported operations and account permissions before enabling commands.

Use the REST API reference and realtime API reference, including the place-order operation.

Download External REST OpenAPI for REST request and response types, and Product-channel AsyncAPI for market and account WebSocket channels. Keep a copy of the schema used to generate your client, and check its compatibility with the chosen environment before enabling commands.

Handle the response alternatives and error codes defined for each operation. Validate WebSocket messages before applying them to market or account state. If a response is incompatible with your client, keep the affected state unavailable and follow the documented recovery steps.

Use asset metadata for identifiers and decimal scales, and the account’s funding capabilities to determine which assets it can accept. A response type alone does not establish deposit or withdrawal availability. See asset identifiers and account funding.

Find REST endpoints for market data, order entry, accounts, authentication and funding below. Check each operation’s credential requirements, request fields and environment availability before integrating. Unsupported compatibility methods return HTTP 501 NotSupported.