> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/support/troubleshooting/how-to-inspect-callouts-to-zuora.md).

# Inspect Callouts to Zuora

Limio allows you to inspect the callouts to Zuora generated when order is processed. This allows you to debug interactions and understand the flow of data between Limio and Zuora.

{% hint style="info" %}
From Release 116, tenants on **Stripe Billing** can inspect their callouts in exactly the same way — Stripe API calls (for example `POST https://api.stripe.com/v1/subscriptions`) appear in the same Callout table on each process event, with the endpoint, timings and full request/response detail.
{% endhint %}

## Where can I view callouts?

1\. When looking at an event, click on the process\_event object in the first table.

<figure><img src="/files/HEXhee6VyD3tWZd1TEmh" alt=""><figcaption></figcaption></figure>

2\. When looking at a process\_event look in the Callout table to find the callout you want to view and click on Details.

<figure><img src="/files/9AgSGNPW7mS7OfythIqM" alt=""><figcaption></figcaption></figure>

3\. You're presented with a JSON view of the callout including details like errors, request timings and order details

<figure><img src="/files/CBnHEodmH9w1emzjFzQj" alt=""><figcaption></figcaption></figure>

Callouts will vary depending on the original event. Generally, the most important callout will be the POST callout to <https://rest.apisandbox.zuora.com/v1/orders>. By inspecting this callout, you will be able to send the payload provided to Zuora Orders, for example for a New Order, a Cancellation, an Add/Remove Product, an Update product etc... Learn more about how Limio processes different customer events in Zuora in: [https://docs.limio.com/integrations/keeping-zuora-and-limio-in-sync/how-limio-events-updates-zuora-for-commerce](https://docs.limio.com/integrations/keeping-zuora-and-limio-in-sync/how-limio-events-updates-zuora-for-commerce "mention")

## Understanding Zuora Errors

When there is an error in the order process, the callouts can provide some extra details about the reasoning for the error.

Here's an example of a Zuora payment error:

<figure><img src="/files/1TUwQNKDiKAyKRBbnK62" alt=""><figcaption></figcaption></figure>

To get an understanding of the Error and how this can be resolved, you can follow these steps below:

1. Select the "v1/orders" POST request in the callouts table<br>

   <figure><img src="/files/w3hWqTlhmP2t07JuzVC1" alt=""><figcaption></figcaption></figure>
2. Expand the response object and copy the "code" value<br>

   <figure><img src="/files/umvDdnU5ZVIiEYRVLx26" alt=""><figcaption></figcaption></figure>
3. Refer to this Zuora Error Code Documentation below for a description of the error code and any suggested resolutions.\
   <https://developer.zuora.com/docs/guides/error-codes/>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.limio.com/support/troubleshooting/how-to-inspect-callouts-to-zuora.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.