Simulate a broker-rejected FX trade (sandbox only)

Rejects a booked trade the way a broker fill rejection would, driving the same domain command the real broker integration sends, so client integrations can exercise the failed-trade flow without a live counterparty. The trade ends Failed with the broker-rejection reason, observable through the standard trade reads. Sandbox-only: the scenario is registered exclusively when the platform runs in Simulated integrations mode, so in Real or Mocked mode this endpoint returns 404 for every request. Only a booked trade can be rejected, and the sandbox broker fills every trade on initiation unless its internalReference starts with TRADE-pending, so place the trade with that trigger to keep it rejectable.

Path Params
string
required

The unique identifier of the trade to reject

Body Params
string
required
length ≥ 1
Headers
string
required

Fresh RFC 9449 proof JWT (ES256) signed with the client's DPoP key, binding this request's method and URL to the access token; generate a new proof per request

Responses
204

Trade rejected; GET /fx/trades/{id} now shows it Failed with the broker-rejection reason

Language
Credentials
OAuth2
URL
LoadingLoading…
Response
Choose an example:
application/problem+json