Once the API is available, both are served from
https://api.bullionwale.com.
What is the same
- The checks on an order. A test order goes through the same symbol, side, price-freshness, trading-halt, quantity and weight-allocation checks as a production order, and is priced the same way, with your own pricing. So a test order that is refused tells you a production order would be refused for the same reason, with one exception:
limit_exceededis judged against your test position (see below), so it does not predict a production refusal, and a production order can be refused for your real position when a test order is not. - Authentication, scopes and idempotency. Keys, scopes,
Idempotency-Key, replays and422 idempotency_key_reusedbehave the same. - The error format. Every refusal has the same shape and codes. See Errors.
What is different
How test orders use your weight allocation
Test orders are checked against your account’s real weight allocation, but against the net position of your test orders, not your real one. They never change your real position, and real orders never change your test position.GET /positions on the test path shows the test book.
Moving from test to production
- Run your integration against the test environment, including retries after timeouts and the error cases you handle.
- Meet the production access requirements and receive a live key.
- Change the base path from
/api/trading/test/v1to/api/trading/v1and use the live key. - Handle the production-only answers:
202with apendingorder,409 order_rejected, and the503 booking_…codes. - Check
GET /me:production_trading_availablemust betruebefore you send a real order.