API Terms of Use

Last updated: July 2026

These API Terms govern all access to OpenFlow's programmatic interfaces at api.openflow.network/gw and any related SDKs, data feeds, and API keys. By calling the API, obtaining a key, or passing a feeRecipient, you agree to these terms. They incorporate the Risk Disclosures; end users of your application remain subject to the Terms of Service.

1. The API

The API provides swap quotes (public, no key), unsigned-transaction building, swap confirmation, and pools and tokens data endpoints. Server-side execution keys (ofdex_*) are issued to member exchanges via the For CEX dashboard. For market swaps the API returns unsigned transactions — the end user's own wallet signs and submits, and OpenFlow never takes custody of funds. Limit and DCA order parameters are stored server-side and executed by an automated keeper. No uptime, latency, or support commitment is made; endpoints may change at any time. Public endpoints are currently rate-limited at 10 requests/second per IP.

2. Eligibility and jurisdiction

You may not use the API if you or your organisation are subject to OFAC, EU, UK, or UN sanctions, or barred by applicable export-control laws. You are solely responsible for the legality of your product in every jurisdiction where you offer it. OpenFlow makes no representation that any use of the API is lawful anywhere. You must implement the geographic and eligibility restrictions we notify to you and must not knowingly serve OpenFlow-powered functionality to users in restricted jurisdictions.

3. API keys and security

Keys are issued to a specific legal person and are non-transferable. You are responsible for all use under your keys and must keep them secret (server-side only; never in client-side code). Notify OpenFlow immediately through the support page of any suspected key compromise.

4. Fees and the integrator revenue share

Swaps carry a protocol fee of 2.5 basis points of swap output, charged inside the swap transaction. If you pass a valid feeRecipient wallet address, 60% of the fee on attributable swaps is directed to that address and 40% to OpenFlow — automatically within the transaction. The on-chain record is authoritative. You are responsible for the accuracy of your feeRecipient address, all taxes on amounts you receive, and any licensing or disclosure duties your receipt of the share may trigger. The share does not increase the fee paid by end users. You must disclose the total 2.5 bps fee and your share of it to your end users clearly and before execution.

5. Data use and redistribution

You receive a limited, revocable, non-exclusive, non-transferable license to use API data within your application to serve your own end users. You must not resell, sublicense, or redistribute raw API data as a standalone product; use the data to build a competing quote or data service; remove required attributions; or represent the data as endorsed by OpenFlow. Caching is permitted for up to 15 minutes; quotes must never be shown past their validity window of approximately 30 seconds.

6. Integrator conduct

Operate your application lawfully. Do not use the API for market manipulation, wash trading, money laundering, sanctions evasion, or exploitation of protocol vulnerabilities. Do not misstate what OpenFlow does — in particular, "OpenFlow never touches funds" is accurate only for market swaps; limit and DCA orders are stored server-side and executed by OpenFlow's keeper, and your UI must present them as best-efforts standing instructions. Surface risk disclosures materially equivalent to the Risk Disclosures to your end users before they trade.

7. Suspension and termination

We may throttle, suspend, or terminate your API access at any time for breach, security risk, or discontinuation of the API. Accrued on-chain fee shares are unaffected by termination; no shares accrue after termination.

8. Disclaimers

The API and all data are provided "as is" and "as available" without warranties of any kind. We do not warrant that quotes are achievable, that stored orders will execute, or that the API will be uninterrupted, secure, or error-free.

9. Limitation of liability

OpenFlow's aggregate liability arising from or related to the API will not exceed the greater of (a) the protocol's 40% fee portion attributable to your integration in the 12 months before the claim and (b) USD 1,000. OpenFlow will not be liable for indirect, incidental, special, consequential, or punitive damages, or loss of digital assets. Nothing excludes liability that cannot lawfully be excluded.

10. Indemnity

You will defend and indemnify OpenFlow and its personnel against third-party claims, regulatory actions, losses, and reasonable legal fees arising from your application, your use of the API, your breach of these API Terms, or your violation of law or third-party rights.

11. Export controls and sanctions

You will comply with all applicable export-control and sanctions laws in your use of the API and distribution of your application. You represent that neither you nor any party receiving your fee share is a sanctioned person or located in an embargoed jurisdiction.

12. General

We may update these terms prospectively by posting the new version; continued use after the stated notice period is acceptance. You may not assign without our consent. Questions: use the support page.