Textile FX

Appearance

Textile FX API v1 (deprecated) ​

v1 is closed to new integrations

Do not build on v1. The current API is v2 RFQ.

v1 stays served so integrations already running on it keep working. It takes no new features and no new endpoints, and it is not the path for anything you are starting today. Limit orders are the one product that still runs here, and they are documented below for the integrations that already use them.

Base URL ​

https://api.textilecredit.com/v1

What is still here ​

  • Limit orders. Build the EIP-712 payload, submit the signed order, list your orders.
  • Corridors (GET /v1/corridors), the pairs and their live oracle rates.
  • Webhooks, a signed callback when an order settles. Endpoint registration on /v1/webhooks is the shared registry for both versions, including v2 events, so it stays.
  • Leftover swap routes (GET /v1/quote, POST /v1/swaps, GET /v1/order-book), served for old integrations only. Use v2 RFQ instead.

The shape of a limit order ​

GET  /v1/limit-orders/quote     → maker price for this size
POST /v1/limit-orders/prepare   → EIP-712 payload
      you sign with your wallet
POST /v1/limit-orders           → rest the signed order
GET  /v1/limit-orders/{id}      → status until a maker takes it

It is non-custodial. The API never signs anything, never touches your keys, and never holds funds. Every write endpoint hands you an unsigned transaction (to, data, value) or an EIP-712 payload to sign.

Conventions ​

  • Amounts are strings in atomic units, base-10, no decimals. "1000000" is 1 USDT. Rates are RAY-scaled (1e27) strings.
  • Addresses are standard EVM addresses. Lowercase is fine, we normalize.
  • Timestamps are ISO-8601 UTC.
  • Every response carries an X-Request-Id header. Include it when you report an issue.

Next ​