What Are API Service Accounts?
API Service Accounts act as proxy machine accounts that companies can use to ingest and export data via our public API. Rather than routing data through a general warehouse, service accounts replicate a user account on the KEY ESG platform. This ensures that any ingested or exported data is clearly attributed to a specific machine account, providing transparency, traceability, and security.
Data Ingestion & Export (API-IN/OUT)
With the launch of our public API:
API-IN: Users will be able to ingest data directly into the KEY ESG platform, and modify submissions directly via API
API-OUT: Users will be able to export data out of the platform, including portfolio metrics and raw submission data.
This means customers can:
Automate data transfers, reducing reliance on manual entry.
Improve efficiency, consistency, and accuracy in reporting.
Integrate KEY ESG seamlessly into existing systems and workflows.
Update and delete submissions via API, saving significant time
Key Benefits of API Service Accounts
Enhanced Security & Clear Authentication
Service accounts use secure access tokens and client secrets.
Customers receive clear, step-by-step guidance for credential setup via our API documentation.
This ensures robust, user-friendly authentication and safe data transfers.
Granular Data Origin & Control
Data ingested via a service account is always attributed to that machine account.
This provides better visibility, tracking, and governance over data sources.
Ease of Integration & Developer-Friendly Resources
Our comprehensive API documentation helps teams map their data to KEY ESG’s data structure for ingestion and export.
Explore the docs here: https://api.keyesg.com/api/docs
What’s in Scope?
API-OUT: All submissions and output metrics (including custom metrics, except CSRD metrics).
API-IN : All data points excluding CSRD
FAQs:
How will metrics map across that are not already in the KEY ESG platform for API-in?
Each metric will need to be configured and mapped from the existing database into the KEY ESG library once. This process only needs to be configured at the beginning of the integration and will not need to be repeated once each metric is mapped.