> 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 **** 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. --- # 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://mobile-calendar.gitbook.io/v1/overview/troubleshooting.md?ask=&goal= ``` `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.