Authentication

All Fordje Connect API endpoints require authentication via an API key passed in the X-API-Key request header.

Including your API key

curl -X GET "https://connect.fordje.com/v1/ahjs" \
  -H "X-API-Key: your-api-key"

Error responses

If the API key is missing or invalid, the API returns a 401 Unauthorized response. The error field distinguishes the specific failure so you can branch on it in your client:

`error`	Triggered when
`MISSING_API_KEY`	The request did not include an `X-API-Key` header.
`INVALID_API_KEY`	The `X-API-Key` header was present but the key is unknown, revoked, or malformed.

Example response:

{
  "response_type": "error",
  "description": "Missing API key. Include your key in the X-API-Key header.",
  "error": "MISSING_API_KEY",
  "status_code": 401
}

Key management

API keys are managed through your Fordje account. From there you can:

Create new API keys
View existing keys
Rotate keys (generates a new key and revokes the old one)
Revoke keys that are no longer needed

API keys are sensitive credentials. Never expose them in client-side code, public repositories, or logs.

Key scoping

Each API key is associated with an organization. The key inherits the organization’s AHJ subscription, which determines which AHJs you can access through the API. See AHJs for details.

Getting started

Core concepts

Guides

Including your API key

Error responses

Key management

Key scoping

​Including your API key

​Error responses

​Key management

​Key scoping

Including your API key

Error responses

Key management

Key scoping