Tracing a call end to end
Every call through Apideck is logged and viewable per consumer. Each entry is a linked pair: the unified request you made, and the raw request Apideck made downstream.
The parent, and the child. Both kept.
Jump between the two with View child and View parent to trace any call end to end. Pick a call, then pick a half.
Nothing to debug — but note the shapes. You wrote a REST call against a unified model; NetSuite was asked in SOAP for a vendor payment search. Neither of those facts is in your code.
/accounting/bill-payments200 412msThe unified request you made, and the normalized response — identical across every connector.
{ "status_code": 200, "status": "OK", "service": "netsuite", "resource": "BillPayments", "operation": "all", "data": [ { "id": "12345", "downstream_id": "PYMT-9981", "currency": "USD", "total_amount": 1250.00, "reference": "Bill payment - March", "payment_method": "check", "transaction_date": "2026-03-04T00:00:00.000Z", "updated_at": "2026-03-04T11:22:08.114Z" } ]}The abstraction stays inspectable.
A unified API is a layer between your code and a system you don't control. The moment something goes wrong, the useful question is which side of the layer it went wrong on — and that's a question you can only answer if both sides were recorded.
What you sent, and the normalized response you got back. If this looks wrong, the problem is in your call or in the mapping.
Exactly what the connector received and returned, in its own format. If this looks wrong, the problem is downstream — and you have the evidence.
Support conversations become a link to a log entry instead of a description of what you think happened.