Firing a POST to /api/v2/flows/executions from the desktop wrapper keeps throwing a 400 Bad Request. The payload structure matches the docs exactly: {"triggerType": "api", "flowId": "b8c9d0e1-f2a3-4b5c-6d7e-8f9a0b1c2d3e", "data": {"extRef": "ORD-8821"}}. The token’s valid until 16:30 GMT and I’ve hardcoded the Content-Type to application/json, yet the network inspector shows the serialized body arriving as an empty {}. The flow triggers fine in the console, so the client SDK is likely stripping the nested data object during the fetch call before it hits the wire.