EtherDelta / ForkDelta API

Name: EtherDelta / ForkDelta API API
Brand: EtherDelta / ForkDelta API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingnone1 EndpointsREST

For Agents

Retrieve the legacy ForkDelta ticker snapshot for ERC-20 token pairs from the now-archived EtherDelta successor exchange.

Quickstart

Get started with EtherDelta / ForkDelta API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get the ForkDelta ticker snapshot"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with EtherDelta / ForkDelta API API.

Pull a historical snapshot of ticker data for ERC-20 token pairs traded on ForkDelta

Reference the OpenAPI shape when migrating off legacy EtherDelta integrations

Document the rate-limit ceiling (6 concurrent connections, 12 reconnects per minute per IP) for any code still talking to the host

Identify the WebSocket fallback (wss://api.forkdelta.com) for clients that need live data rather than the REST snapshot

GET STARTED

Start building with EtherDelta / ForkDelta API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for EtherDelta / ForkDelta API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for EtherDelta / ForkDelta API, keeping it validated and agent-ready. EtherDelta was an early Ethereum-based decentralized exchange for ERC-20 tokens, succeeded by ForkDelta. The exchange and its successor are both archived: most live trading happened over a socket.io WebSocket at wss://api.forkdelta.com, with only a single REST ticker endpoint at /returnTicker. This spec documents that lone REST endpoint so historical analysts and archivists can still pull a snapshot of the ticker. Status: defunct — ForkDelta was archived in December 2022.

Use Cases

Patterns agents use EtherDelta / ForkDelta API API for, with concrete tasks.

★ Historical archival snapshot of EtherDelta ticker data

Researchers studying early DEX market structure call /returnTicker once to capture whatever ticker data the legacy host still serves and persist it for later analysis. The endpoint returns price, last trade, and volume fields per token pair, enough to reconstruct a coarse view of the exchange's activity. Because the project is archived, treat any successful response as a snapshot, not a live feed.

GET /returnTicker once and persist the JSON response as a single timestamped snapshot file.

Migration audit from a legacy EtherDelta-based system

Teams retiring a wallet, analytics tool, or research notebook that still references the ForkDelta REST host audit their code against the documented shape so they can confidently swap in a current DEX data source. The spec shows there is only one REST endpoint, which simplifies the migration: every other call on the legacy host was over the socket.io WebSocket and must be replaced separately.

Compare the existing client's REST call list against this spec and flag any non-/returnTicker REST call as legacy-only and unsupported.

Liveness check on the archived ForkDelta host

Before relying on any old ForkDelta-derived data, an integrator pings /returnTicker to confirm whether the host still answers and whether the response shape has drifted. Because the project is archived, the result may be a non-2xx code or stale data, both of which are valuable signals for the integrator to abandon the dependency.

GET /returnTicker once with a short timeout and report whether the response is 2xx and contains ticker entries; otherwise mark the dependency as dead.

AI agent reasoning about a defunct DEX

An AI research agent asked about EtherDelta's API surface uses Jentic to resolve the operation, reads the spec to learn that only /returnTicker is REST and that everything else was socket.io, and surfaces that to the user with the WebSocket URL and rate limit. The agent does not need to scrape archived blog posts to answer.

Search Jentic for 'EtherDelta ticker', read the operation description, and reply with the REST path /returnTicker, the WebSocket fallback wss://api.forkdelta.com, and the documented rate-limit ceiling.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for etherdelta / forkdelta api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/returnTicker

Return ticker data for all traded ERC-20 token pairs

GET

/returnTicker

Return ticker data for all traded ERC-20 token pairs

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The /returnTicker endpoint requires no credential, so Jentic exposes it as a public-data tool with no vault entry needed. Should the operation ever require auth in the future, credentials would be stored encrypted in the Jentic vault.

Intent-based discovery

Agents search Jentic with queries like 'ForkDelta ticker' or 'EtherDelta historical data' and Jentic returns GET /returnTicker, sparing the agent from having to consult archived blog posts about the project.

Time to first call

Direct integration: an hour to handle the legacy host and rate-limit headers. Through Jentic: minutes — the operation is a single discoverable tool.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Binance API

Binance offers a live, fully supported exchange API for spot and derivatives trading.

Use Binance when you need a current, supported exchange API rather than EtherDelta's archived REST endpoint.

Alternative

Kraken API

Kraken provides a regulated, actively maintained exchange API with deep ERC-20 listings.

Use Kraken when you want regulated access to ERC-20 token markets in place of the defunct EtherDelta surface.

Alternative

Bitfinex API

Bitfinex exposes a current REST and WebSocket API for trading ERC-20 and other tokens.

Use Bitfinex when ERC-20 trading on a live exchange is the actual goal.

FAQs

Specific to using EtherDelta / ForkDelta API API through Jentic.

Why is there no official OpenAPI spec for EtherDelta / ForkDelta API?

EtherDelta and ForkDelta did not publish an OpenAPI specification, and the projects are now archived. Jentic generates and maintains this spec so that AI agents and developers can reason about the legacy surface via structured tooling. It is validated against the documented API and kept available for migration and archival use. Get started at https://app.jentic.com/sign-up.

What authentication does the EtherDelta / ForkDelta API use?

The /returnTicker REST endpoint is unauthenticated; no API key or token is required. Through Jentic the operation is exposed as a public-data tool, with rate-limit guidance applied at the gateway.

Is the EtherDelta API still active?

EtherDelta itself ceased operations and ForkDelta, its successor, was archived as of December 2022. Treat any successful response from /returnTicker as a stale snapshot rather than live exchange data, and prefer a current DEX source for fresh prices.

What are the rate limits for the EtherDelta / ForkDelta API?

The documented limit is 6 concurrent connections and 12 reconnects per minute per IP address. Because the project is archived, exceeding these limits is more likely to result in silent failures than enforcement, but you should still respect them for politeness toward whatever host is still answering.

How do I retrieve the ForkDelta ticker through Jentic?

Search Jentic for 'ForkDelta ticker snapshot'. Jentic returns GET /returnTicker. Execute it with no parameters; the response is a JSON object keyed by token pair, where each value contains last price, bid, ask, and 24-hour volume.

Can I place trades through this API?

No. The REST surface only exposes /returnTicker. All trading actions on the legacy exchange happened over the socket.io WebSocket at wss://api.forkdelta.com, which is outside this OpenAPI document and is not supported by the archived project.