EIC (Energy Identification Code) Validator

Validate 16-character EIC codes — the ENTSO-E / ENTSOG identifiers used across European electricity and gas markets, and by EPİAŞ in Turkey — using the official check-character algorithm. Also decodes the issuing office and object type. Runs as a fast Standby API. No login, no personal data.

Endpoint

GET /validate?eic=<code>

Input is uppercased and whitespace is stripped automatically. Hyphens are meaningful and preserved.

Example

GET /validate?eic=10YTR-TEIAS----W

{
  "inputRaw": "10YTR-TEIAS----W",
  "normalized": "10YTR-TEIAS----W",
  "valid": true,
  "length": 16,
  "lioCode": "10",
  "objectType": "Y",
  "objectTypeName": "Area / domain",
  "checkCharGiven": "W",
  "checkCharExpected": "W",
  "errors": []
}

An invalid code returns "valid": false with a reason in errors, for example a check-character mismatch, a wrong length, or an illegal character.

What it checks

• Length — exactly 16 characters.
• Character set — only A–Z, 0–9 and - are permitted.
• Check character — the ENTSO-E weighted mod-37 check character over the first 15 characters. Detects every single-character error.

EIC structure

Part	Position	Meaning
Issuing office (LIO)	1–2	Local Issuing Office assigned by ENTSO-E
Object type	3	See table below
Identifier	4–15	Allocated by the issuing office
Check character	16	Validates the whole code

Object types

Letter	Meaning
X	Party (market participant)
Y	Area / domain
Z	Measurement point
W	Resource object
T	Tie-line
V	Location
A	Substation

Use cases

• Validate market participant / balancing party codes before submitting energy-market messages.
• Clean and verify EIC fields in ETRM, settlement, or nomination data.
• Check codes in EPİAŞ / ENTSO-E integrations and data pipelines.

Pricing

Pay-per-event: $0.001 per API call (api-call).

Related trade & logistics validation APIs

• IMO Ship Number Validator API
• Container Number Validator API (ISO 6346)
• Turkish GTIP / HS Code Lookup API

Notes

This Actor performs offline algorithmic validation. A valid result means the code is structurally correct (well-formed and check-character-consistent); it does not confirm that the code is currently registered and active in the ENTSO-E central registry or a local issuing office registry.