> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superoffice.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Check exceptions from your app's API calls

> How to check exceptions and failed requests from your apps API calls in the SuperOffice Developer Portal.

SuperOffice logs application behavior to Application Insights. In the Developer Portal, you can monitor and analyze your application's failed requests to our APIs and exceptions thrown.

* Exceptions originate in the SuperOffice file set.
* Failed *inbound* requests are requests from your app to a SuperOffice API endpoint.
* Failed *outbound* requests are requests from SuperOffice to an ERP sync or a mirroring endpoint.

## At a glance

The **app page** shows application failures for one specific application.

1. In the Developer Portal, go to your app page.

   To see the list of all apps:

   * Select **Apps** from the top menu to see all apps across every partner you have access to, or
   * Go to the **Applications** section of your partner page to see that partner's apps.

2) Select **Failures**.

3) Select an environment and a time range.

4) Explore the **Exceptions** and **Failed Inbound Requests** tabs.

![API failure overview in SuperOffice developer portal -screenshot][img1]

## Drill down

### Exceptions

Exceptions are grouped by ID and the count shows how many times each exception occurred within the selected time frame.

To explore the details:

1. Click to select an exception from the list.

   ![API exception sample in SuperOffice developer portal -screenshot][img2]

2. Select one of the samples to access the full end-to-end transaction details.

   ![API exception details in SuperOffice developer portal -screenshot][img3]

## Failed requests from app to API

Requests are grouped by operation and the count shows how many times each operation failed within the selected time frame.

Explore the details as described above.

![List of inbound failed API requests in SuperOffice developer portal -screenshot][img4]

![E2E failed failed API request in SuperOffice developer portal -screenshot][img5]

## Improve app health

Leverage our [best practices for online app development][2] to both boost your application's stability and availability.

During development, following the statistics in SOD day-by-day can provide valuable insight into the impact of your improvements.

<Note>
  If you are stuck and need assistance, contact us and include the **operation ID** from the transaction.
</Note>

[2]: ../best-practices/index

[img1]: /media/loc/en/developer-portal/failures.png

[img2]: /media/loc/en/developer-portal/exception-sample.png

[img3]: /media/loc/en/developer-portal/exception-details.png

[img4]: /media/loc/en/developer-portal/failed-inbound.png

[img5]: /media/loc/en/developer-portal/500-details.png


## Related topics

- [Check application usage (API calls)](/en/developer-portal/analytics/metered-services.md)
- [Validation checklist](/en/developer-portal/custom-app/checklist.md)
- [Check application API performance](/en/developer-portal/analytics/metrics-performance.md)
- [Certification checklist](/en/developer-portal/standard-app/certification/checklist.md)
- [Get your custom app validated and live](/en/developer-portal/custom-app/validate.md)
- [Create your first application and connect to SuperOffice web services](/en/developer-portal/getting-started/quickstart.md)