Documentation/API Access/Getting Started with the EU Digital Passport Processor API
Reference§09.01SectionAPI AccessReg. ref.REST API v1Last reviewed2026-04

§09.01 · API ACCESS

Getting Started with the EU Digital Passport Processor API.

Generate an API key, authenticate requests, and start creating passports programmatically.

What the API is for

The EU Digital Passport Processor REST API lets you create, read, and manage battery passports directly from your own systems — ERP, PLM, spreadsheet pipelines, or custom tooling — without using the dashboard UI.

Common uses:

  • Create passports in bulk from your production data
  • Push product data updates as specifications change
  • Query passport status and EU registry state from your own reports
  • Integrate DPP creation into existing manufacturing workflows

Which plans include API access

API access is included in all EU Digital Passport Processor paid subscriptions. Demo accounts cannot generate API keys. To check your subscription status, go to Settings → Billing.

How to generate an API key

  1. Go to Settings → API KeysOpen your dashboard and navigate to Settings, then click API Keys in the sidebar.
  2. Click Generate New KeyGive the key a descriptive name (e.g. "Production ERP integration") and optionally set an expiry date.
  3. Copy the key immediatelyClick Generate. The full key is shown once and cannot be retrieved again. If you lose a key, revoke it and generate a new one.

Authentication

Every API request must include your key in the Authorization header:

Bearer token authentication
Authorization: Bearer dpp_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxx

Keys follow the format dpp_live_ followed by 64 hex characters. This prefix makes keys easy to identify if accidentally exposed in logs or code.

Base URL

API base URL
https://eudigitalpassportprocessor.com/api/v1

All endpoints are versioned under /api/v1/. This ensures your integrations continue to work as the platform evolves.

Store API keys in environment variablesNever hardcode API keys in source code. Use environment variables or a secrets manager. Use one key per integration so you can revoke individual integrations if needed.
REL Related entries
SectionEntryReviewed
API AccessAPI Endpoints Reference2026-04