> For the complete documentation index, see [llms.txt](https://mobile-calendar.gitbook.io/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mobile-calendar.gitbook.io/v1/overview/troubleshooting.md).

# Troubleshooting

If you encounter issues while using the **Mobile Calendar API v1**, this section provides guidance on how to identify, analyze, and resolve problems effectively.

***

## Using the API Logs

Within the main application [app.mobile-calendar.com](https://app.mobile-calendar.com), navigate to:\
**Integrations > REST API > Logs**

In this section you will find:

* A complete history of API requests sent from your account.
* Request details including method, endpoint, parameters, and payload.
* Response details including status codes, headers, and error messages.
* Execution time and IP address of the client.

These logs are the first place to check when troubleshooting any API issue.

{% hint style="warning" %}
Logs are kept in the system for only **30 days**.
{% endhint %}

***

## Request Unique Identifier (RUID)

Every API request processed by the system is assigned a **RUID** (Request Unique ID).\
This identifier is included in error responses and visible in the Logs panel.

* The RUID ensures that every request can be traced precisely in our system.
* When contacting support, always provide the **RUID** of the failing request.
* This allows our team to investigate the issue quickly and efficiently.

Example error response (RFC 7807 format):

```json
{
  "type": "https://mobile-calendar.com...",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "An unexpected error occurred.",
  "instance": "/v1/public/reservations",
  "ruid": "c1a2f9e3-45d0-4c7e-9b62-0a9db31e8c21"
}
```

***

## Contacting Support

If after reviewing the logs you are unable to resolve the problem:

* Collect the following details:
  * RUID of the failing request
  * Endpoint and HTTP method used
  * Timestamp of the request
  * Full error message or problem response
* Send the information to **<info@mobile-calendar.com>** with a short description of the issue.

Our support team will analyze the request using the RUID and provide assistance.

***

## Best Practices

* Always validate request payloads before sending.
* Handle errors using the RFC 7807 standard fields (`type`, `title`, `status`, `detail`).
* Monitor rate limits to avoid `429 Too Many Requests`.
* Use the Logs panel regularly to ensure integration is working as expected.

***

✅ Following these steps will help you resolve most integration issues quickly and effectively.