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

# API Log

> Each request made with your keys, what was sent and what was received, visible in your account.

Each request made with one of your keys is logged. You can find it in your account, with the body sent and the response received, so you can troubleshoot an integration yourself, without writing to us.

## `X-Request-Id`

Any response from the API, successful or not, has the header `X-Request-Id`:

```http theme={null}
HTTP/1.1 422 Unprocessable Content
Content-Type: application/problem+json
X-Request-Id: 01JAQ9B2C4D6E8F0G2H4J6K8M0
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 287
```

The ID uniquely identifies the request. Keep it in your logs next to each call: with it you will find the request in the log, and if you ask us for help, it's the first thing we need.

## Where to see it

In your account, under **Settings → API → Log** ([housera.ro/setari/api/jurnal](https://housera.ro/setari/api/jurnal); in the sandbox, `https://staging.housera.ro/setari/api/jurnal`).

For each request you can see:

* **the time and duration**;
* **the key** used (by name);
* **the method, path, and status** of the response;
* **the listings affected** by the request;
* **the IP address and application** (header `User-Agent`) from which it came;
* **`Idempotency-Key`**, if you sent it;
* **the body of the request and the response**.

If you are the owner or admin of an agency, you can also see the requests from your colleagues in the agency.

You can filter by:

* **the request ID or part of the path** (for example `listings/ref/CRM-10293`);
* **the code of a listing**, to see everything that has been done through the API on it;
* **result**: successes, client errors (`4xx`), server errors (`5xx`);
* **key**.

## What is retained and for how long

| What | How long |
| - | - |
| The bodies of the request and the response | 30 days |
| The rest of the information about the request | 365 days |

The body of the request is **redacted** before saving: secrets, keys, and contact data are not kept in clear. The API responses do not contain contact data. A body larger than 64 KB is kept only partially.

## What does not appear

* **Requests without a valid key** (missing, incorrect, or expired key) cannot be linked to your account, so they do not appear in your log. If you receive `401`, check the header `Authorization` and the expiration date of the key.
* **The requested vocabulary without a key** (`GET /schema`) is not recorded.

## The history of a listing

Changes made through the API also appear in the history of the listing, as “API” modifications, with the name of the key and the request ID. This way you can distinguish an edit made from your system from one made by a colleague directly on housera.ro.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.