Getting started

Step-by-step guides for integrating with ERI's secure, multi-tenant intelligence layer. Learn how a request moves through the Core API, then build your first integration.

API referenceFirst tutorial

Anatomy of a request

Each failure code is documented in the OpenAPI contract

POST/organizationsX-API-Key: ••••••••••••

1. 01401

   Authenticate

   The key in X-API-Key must be active, unexpired and match its stored hash. Every failure returns the same message.

2. 02400

   Validate

   The body must be exactly name and email: a 2-200 character name, a valid email, no other fields.

3. 03409

   Check uniqueness

   Each organization needs its own email. A second organization with the same email is rejected.

4. 201Created{ "id": "019f…" }

Reads are tenant-scopedGET /organizations/{id} only returns the organization your key belongs to. Any other id returns 404, whether it exists or not.

What you will build

• 1Create an organizationTutorialSet up the Client Account boundary with a strict name and email payload.POST /organizations→
• 2Ingest the report feedTutorialPage through every report your Client Account can read, then fetch each one in full.GET /reports→
• 3Compare against the contractReferenceEvery tutorial example mirrors the generated OpenAPI 3.0 reference.openapi.yaml→

ProductionProvided at onboardingMutual TLS required

Sandboxhttps://staging-api.emergentriskinternational.com/api/v1Same contract as production

Base URLs and request conventions→