API reference·Version 0.0.0

ERI Core Content Delivery API

Programmatic threat intelligence feeds for enterprise client ingestion pipelines.

Start the tutorial

Sandbox URL

https://staging-api.emergentriskinternational.com/api/v1

Auth

X-API-Key

Production transport

Mutual TLS

Endpoints

8

Base URLs

Every path in this reference is relative to one of these. Sandbox runs the same contract as production, whose base URL is provided at onboarding.

• Sandboxhttps://staging-api.emergentriskinternational.com/api/v1
• Localhttp://127.0.0.1:3001/api/v1Local only

Transport security (mutual TLS)

All connections to the production gateway are additionally protected by mutual TLS (mTLS): clients must present an ERI-issued client certificate during the handshake, and the gateway rejects connections that do not. mTLS is a transport-layer control enforced at the edge and is therefore described here rather than as an OpenAPI security scheme - it cannot be exercised from the interactive "try it" console. Application-layer authentication is enforced by the Core API gateway and documented via the security scheme below.

Authentication

API keyEvery endpoint

Organization-scoped API key. Send in the X-API-Key request header.

Keep the key server-side and out of URLs. A missing or unknown key returns 401.

Authenticated request

curl https://staging-api.emergentriskinternational.com/api/v1/reports \
  -H "X-API-Key: $ERI_API_KEY"

Endpoints

8 operations, grouped by resource.

Reports3

• GETList reports/reports
• GETSearch reports/reports/search
• GETRetrieve a report/reports/{id}

Organizations2

• POSTCreate an organization/organizations
• GETRetrieve an organization/organizations/{id}

API keys3

• GETRetrieve API key metadata/api-keys/{id}
• PATCHChange API key privileges/api-keys/{id}/privileges
• POSTRevoke an API key/api-keys/{id}/revoke