When you are integrating with Adyen, you may want to analyze or debug API requests in the test environment, for example test payments.
Using API logs, you can see information about your API requests in the test Customer Area. You can troubleshoot the requests and responses, and see the metadata of your API requests.
The logs show all API requests made in your test environment in the past seven days. Requests older than seven days are removed from the API logs. API logs are only available in the test environment.
Using API logs
To view API logs, you must have one of these user roles:
- Merchant admin
- Technical integrator
To view and search API logs:
- Log in to your test Customer Area and select a merchant account.
- Select Developers > API Logs. This will show a list of every API request made on the test environment in the past seven days.
- Select an item to see the details of that API request. You will see the timestamp, which API was called, the PSP reference and full details of the request and response. Type a PSP reference into the search bar, or use the filter buttons to the right of the search bar to filter the list by date, API or HTTP method.
You can use API logs in end-to-end testing, to see details of the requests you have made to our APIs.
If you're testing the checkout flow for your online payments setup and a payment fails, you can check the API logs to see details of what you sent to the API and why the payment failed. You can compare failed API requests with successful ones.
Go to the API logs page. In the PSP reference column, select the payment reference to see details of the API request.
Under Response status at the top right of the page you will see the error code.
In the Request body section, you see the details of the request, including which endpoint the request was sent to.
- In the Response body section, you can see details of the response.
For example, when you see error code 422, the API request contained input that was not valid. The response body shows which field had the invalid input.
You can then check on your side what input was sent and make changes.