API Introduction

DZap exposes two HTTP surfaces:

API	Base URL	Auth	Use for
Fuse API	`https://zap.dzap.io`	Optional API key	Zap quotes, bundles, positions, status
Trade API	`https://api.dzap.io`	Optional API key	Swaps, bridges, DCA, tokens, status

Both speak JSON over HTTPS. Both run on the same routing engine.

Pick one

OpenAPI-backed. Quote, build, bundle, execute, status.

REST routes for the full Core surface: quotes, build, execute, status, tokens.

Amounts are strings in wei - "1000000" is 1 USDC (6 decimals), not 1.
Native tokens use the sentinel 0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE. Never the zero address.
Slippage is percent - 1 = 1%, 0.5 = 0.5%.
Errors follow { "status": "error", "code": "...", "message": "..." }. See Error Codes.

Aspect	Fuse API	Trade API
Health endpoint	`GET /v1/status`	`GET /v1/status`
Auth	Optional API key (`x-api-key` header)	Optional API key (`x-api-key` header)

All endpoints are under /v1. Breaking changes ship under /v2; /v1 stays available with at least 90 days notice. Watch the changelog.

Last modified on July 14, 2026