standard-relayer-api

standard-relayer-api copied to clipboard

This has confused more than one person now -- there are still references to the old `/token_pairs` route in the v3 spec See https://github.com/0xProject/standard-relayer-api/issues/59#issuecomment-570862883

steveklebanoff

waylalfarwq

https://8080-0-121f7db3.hummingbot-test-drive.appsembler.com/http://0x(hex1).0x(hex2).0x(hex3).0x(hex4

PinkDiamond1

Cannot GET /token_pairs

1

file : `http/v3.md` `curl https://api.0x.org/token_pairs?page=3&perPage=20` returns ```html Error Cannot GET /token_pairs ```

SvenMeyer

Add correct endpoint addresses

1

aketekt

In SRA v3, the order object schema specifieds "chainId" for HTTP, and "domainHash" for WS. I notice that [this commit](https://github.com/0xProject/standard-relayer-api/commit/3621ade726d98bc607a37098950c77dfd9ed173b) changed domainhash to chainid for HTTP, and I'm wondering if...

AusIV

If /orders returns "relayerApiOrdersResponseSchema" which references relayerApiOrdersSchema -> relayerApiOrderSchema, then it makes sense for the non-paginated interface (/order/{hash} to return "relayerApiOrderSchema".

amaurer

The Websockets API should clarify that messages should be of "text" type rather than binary. 0x connect expects this, but the specification is ambiguous,

AusIV

Guidance For MultiAssetProxy

2

With the introduction of the MultiAssetProxy, some things in the current version of the Standard Relayer API are a bit unclear. For example > makerAssetAddress [string] returns orders where the...

AusIV

Error code for IP block

3

Relayers may choose to block certain IP addresses. Would be nice to have a standardized Error flow for this.

aakilfernandes