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

# Status

> The normalized status value, the live/dead category, the office's own wording, and the difference between null, other and unknown.

Offices describe a mark's legal state in hundreds of ways. The record gives you the normalized value, a three-way category, and the office's own wording:

```json theme={null}
"status": {
  "value": "pending",
  "category": "live",
  "date": null,
  "office_status": "Në proces ekzaminimi",
  "office_status_code": null
}
```

## Value

| `status.value` | Meaning | `status.category` |
| - | - | - |
| `registered` | Registered and in force, as far as the register shows | `live` |
| `pending` | Filed and not yet decided: examination, publication, opposition | `live` |
| `abandoned` | Withdrawn, refused or lapsed before registration | `dead` |
| `cancelled` | Registered, then cancelled, revoked or invalidated | `dead` |
| `expired` | Registered, then not renewed | `dead` |
| `unknown` | The office itself reports the status as unknown | `unknown` |
| `other` | The office's status has no mapping yet | `unknown` |
| `null` | The office did not state a status | `null` |

The mapping follows each office's own terms, which do not always line up with these definitions. Some offices, for example, keep a lapsed mark as registered until a grace period ends. When the exact legal state matters, read `office_status`, and check the office record before acting on it.

## Category

`status.category` groups values into `live` (registered or pending), `dead` (abandoned, cancelled or expired) and `unknown` (`unknown` or `other`). It is `null` only when the status is `null`.

Use the category for "is this mark a potential obstacle" questions, and the value when you need to tell pending from registered.

## null, other and unknown

These three look alike but mean different things, and you can filter on each one separately:

| You see | It means | Filter with |
| - | - | - |
| `"value": null` | The office published no status for this record. | `status=none` |
| `"value": "other"` | The office published a status that Pinakel has not mapped yet. The wording is in `office_status`. | `status=other` |
| `"value": "unknown"` | The office published a status, and it says the status is unknown. | `status=unknown` |

The same applies to `status_category=none` and `status_category=unknown`. A record with `other` today may get a mapped value later, when Pinakel adds a mapping; it then appears in the [changes feed](https://docs.pinakelai.com/guides/syncing.md).

## Office wording

* `office_status` is the office's status text, untranslated, for example `Në proces ekzaminimi` ("under examination") in Albania.
* `office_status_code` is the office's status code, for registers that publish codes.

Both are in the full record only, not in summaries. Both can be `null`.

## Status date

`status.date` is the date of the current status as the office states it, often the date of the last decision or event. It is `null` when the office does not publish one. Filter on it with `status_date_from` and `status_date_to`.

## Filtering

```bash theme={null}
# Live marks only
--data-urlencode "status_category=live"

# Registered or pending, in two equivalent spellings
--data-urlencode "status=registered,pending"
--data-urlencode "status=registered" --data-urlencode "status=pending"

# Everything that might still be live, including records with no usable status
--data-urlencode "status_category=live,unknown,none"
```

Values within one parameter are combined with OR; different parameters are combined with AND.


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