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

# Identifiers

> How Engrate uses the identifiers of each market.

Each market has its own identifiers for parties, areas and accounting points. For example, in Germany a party in a schedule has an EIC code and a grid operator has a BDEW code or a GLN. Engrate keeps the identifiers of the market. Because of this, you use the same identifiers in the API as in the market.

## Engrate identifiers

Engrate also gives each object its own identifier. Use this identifier to read the object in the API. Some objects, such as a schedule, have no identifier in the market. For these objects, the Engrate identifier is the only identifier.

## Look up parties and areas

The [Core API](https://docs.engrate.io/api-reference/core/overview.md) lists the parties, scheduling areas, control areas and metering grid areas of each market, with their identifiers. Use it to check a counterparty's code before you send a schedule.


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