JSON responses and timing
Response envelopes, reserved Credit and request timing semantics.
JSON response envelope
Non-SSE JSON execution responses use the following platform envelope. The original function result is inside resp.
{
"precharge_credit": "2.00000000",
"request_received_at": "2026-11-06T08:00:00.123Z",
"response_first_byte_at": "2026-11-06T08:00:00.640Z",
"resp": { "data": {} }
}
This is an illustrative response, not a measured request. Function response examples and field paths below describe the payload inside resp: their /data path is /resp/data in the complete HTTP body. Platform JSON errors use resp.error.code; task acknowledgements are also inside resp. Keep checking the HTTP status.
precharge_credit is the initial amount reserved, expressed as an eight-decimal Credit string; it is not the final charge. It is "0.00000000" when no reservation occurred and null when the reservation or task acceptance cannot be confirmed. Final charges follow the published pricing and settlement rules.
Both timestamps are UTC RFC3339 values with millisecond precision. request_received_at is when the Gateway received the first request-header message. response_first_byte_at is when it prepared the first outgoing body chunk; it is neither supplier TTFB nor browser receipt time. The X-Apibasket-Request-Received-At header mirrors the received timestamp. JSON execution responses are not cacheable.
The online trial shows a Wi-Fi icon followed by a clock icon, each with a value and no visible text label. Wi-Fi displays the estimated interval from the browser's execution POST to Gateway receipt, including website forwarding and client/server clock differences. The clock displays the measured total request duration minus that estimate. Challenge and proof-of-work preparation are excluded from the underlying total. If the estimate is missing, negative or outside the measured total, both values are unavailable (—). These values do not isolate pure network latency or supplier execution time.
SSE event bodies and bodyless HTTP responses retain their existing format. Catalog, login and administration responses are outside this envelope.