API Structure

Every endpoint follows the same request and response contract. Once you know the envelope, the pagination scheme, and the auth headers, you can call any route without re-reading per-endpoint docs.

Base URL

https://api.indexhog.com

Replace the host with your deployment.

Request Headers

The organization id for tenant-scoped routes goes in the URL path (/api/user/organizations/{organizationId}/...), not in a header.

Sending a typical authenticated request

ORG_ID="01HZ3K5R4X9Y2V6QF8TJ7W0CDN"
curl "https://api.indexhog.com/api/user/organizations/${ORG_ID}/projects" \
-H "X-Api-Key: tkn_AbCdEf0123456789XyZ..."

const apiKey = '<your-api-key>'; // load this from a secure env var — never hardcode
const organizationId = '01HZ3K5R4X9Y2V6QF8TJ7W0CDN';
const res = await fetch(
`https://api.indexhog.com/api/user/organizations/${organizationId}/projects`,
{ headers: { 'X-Api-Key': apiKey } },
);

import os, requests

organization_id = '01HZ3K5R4X9Y2V6QF8TJ7W0CDN'
res = requests.get(
f'https://api.indexhog.com/api/user/organizations/{organization_id}/projects',
headers={'X-Api-Key': os.environ['API_KEY']},
)

Request Bodies

Bodies are JSON. Write endpoints reject Content-Type values other than application/json. Request bodies are capped at 10 MiB — anything larger returns 400 Bad Request.

ORG_ID="01HZ3K5R4X9Y2V6QF8TJ7W0CDN"
curl -X POST "https://api.indexhog.com/api/user/organizations/${ORG_ID}/projects" \
-H "Content-Type: application/json" \
-H "X-Api-Key: tkn_AbCdEf..." \
-d '{
  "name": "Acme Studio",
  "slug": "acme-studio",
  "website": "https://acme.example"
}'

const apiKey = '<your-api-key>'; // load this from a secure env var — never hardcode
const organizationId = '01HZ3K5R4X9Y2V6QF8TJ7W0CDN';
const res = await fetch(
`https://api.indexhog.com/api/user/organizations/${organizationId}/projects`,
{
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'X-Api-Key': apiKey,
  },
  body: JSON.stringify({
    name: 'Acme Studio',
    slug: 'acme-studio',
    website: 'https://acme.example',
  }),
},
);

organization_id = '01HZ3K5R4X9Y2V6QF8TJ7W0CDN'
res = requests.post(
  f'https://api.indexhog.com/api/user/organizations/{organization_id}/projects',
  headers={'X-Api-Key': os.environ['API_KEY']},
  json={
      'name': 'Acme Studio',
      'slug': 'acme-studio',
      'website': 'https://acme.example',
  },
)

Response Envelope

Every JSON response — success or error — uses the same envelope.

Success

{
"success": true,
"status": 201,
"code": "OK",
"message": "Project created successfully",
"data": {
  "id": "01HZ3KA7V0J9Z8Q2G5B1T7XWDN",
  "name": "Acme Studio",
  "slug": "acme-studio",
  "website": "https://acme.example",
  "status": "active",
  "createdAt": "2026-04-05T10:00:00.000Z",
  "updatedAt": "2026-04-05T10:00:00.000Z"
}
}

Error

{
"success": false,
"status": 400,
"code": "VALIDATION_ERROR",
"message": "Validation failed for fields: website, slug",
"meta": {
  "errors": [
    { "field": "website", "error": "Invalid url",            "location": "body" },
    { "field": "slug",    "error": "The slug must be unique", "location": "body" }
  ]
}
}

Each entry in meta.errors has field (the offending field path), error (the message), and location (body, query, or params).

Fields

Pagination

List endpoints use offset-based pagination. The query parameters are offset and limit; the response meta returns total, offset, limit, and hasMore.

Some endpoints add their own filters on top — a q search query, a status filter, etc. See the API Reference for endpoint-specific parameters.

ORG_ID="01HZ3K5R4X9Y2V6QF8TJ7W0CDN"
curl "https://api.indexhog.com/api/user/organizations/${ORG_ID}/projects?offset=40&limit=20" \
-H "X-Api-Key: tkn_AbCdEf..."

const apiKey = '<your-api-key>'; // load this from a secure env var — never hardcode
const organizationId = '01HZ3K5R4X9Y2V6QF8TJ7W0CDN';
const res = await fetch(
`https://api.indexhog.com/api/user/organizations/${organizationId}/projects?offset=40&limit=20`,
{ headers: { 'X-Api-Key': apiKey } },
);
const body = await res.json();
console.log(body.meta.total, body.meta.hasMore);

organization_id = '01HZ3K5R4X9Y2V6QF8TJ7W0CDN'
res = requests.get(
  f'https://api.indexhog.com/api/user/organizations/{organization_id}/projects',
  params={'offset': 40, 'limit': 20},
  headers={'X-Api-Key': os.environ['API_KEY']},
)
body = res.json()
print(body['meta']['total'], body['meta']['hasMore'])

Paginated response

{
"success": true,
"status": 200,
"code": "OK",
"message": "Projects fetched successfully",
"data": [
  {
    "id": "01HZ3KA7V0J9Z8Q2G5B1T7XWDN",
    "name": "Acme Studio",
    "slug": "acme-studio",
    "status": "active"
  }
],
"meta": {
  "total": 156,
  "offset": 40,
  "limit": 20,
  "hasMore": true
}
}

HTTP Status Codes

Dates and IDs

• Dates — ISO 8601 with UTC (2026-04-05T10:00:00.000Z). Parse with new Date(...) in JS or datetime.fromisoformat(...) in Python.
• IDs — UUID v7 strings. They are time-sortable, so ordering by id descending roughly matches createdAt descending.

Field Naming

• camelCase for every field.
• Booleans use is, has, or needs prefixes (isActive, isVerified, hasMore).
• Date fields end in At (createdAt, updatedAt, expiresAt, lastLoginAt).
• List endpoints return arrays in data and pagination in meta. Single-resource endpoints return an object in data and omit meta unless there is something to report.

A minimal API client

class ApiClient {
constructor({ apiKey, organizationId, baseUrl = 'https://api.indexhog.com' }) {
  this.apiKey = apiKey;
  this.organizationId = organizationId;
  this.baseUrl = baseUrl;
}

async request(path, { method = 'GET', body, searchParams } = {}) {
const url = new URL(this.baseUrl + path);
if (searchParams) {
for (const [k, v] of Object.entries(searchParams)) url.searchParams.set(k, v);
}

  const res = await fetch(url, {
    method,
    headers: {
      'Content-Type': 'application/json',
      'X-Api-Key': this.apiKey,
    },
    body: body ? JSON.stringify(body) : undefined,
  });

  const envelope = await res.json();
  if (!envelope.success) {
    const err = new Error(envelope.message);
    err.code = envelope.code;
    err.status = envelope.status;
    err.meta = envelope.meta;
    throw err;
  }
  return envelope;

}

listProjects({ offset = 0, limit = 20 } = {}) {
return this.request(
`/api/user/organizations/${this.organizationId}/projects`,
{ searchParams: { offset, limit } },
);
}
}

import os, requests

BASE_URL = 'https://api.indexhog.com'

def client():
s = requests.Session()
s.headers.update({'X-Api-Key': os.environ['API_KEY']})
return s

def call(session, method, path, **kwargs):
res = session.request(method, BASE_URL + path, **kwargs)
envelope = res.json()
if not envelope.get('success'):
raise RuntimeError(f"{envelope.get('code')}: {envelope.get('message')}")
return envelope

def list_projects(session, organization_id, offset=0, limit=20):
return call(
session,
'GET',
f'/api/user/organizations/{organization_id}/projects',
params={'offset': offset, 'limit': limit},
)

Best Practices

• Check envelope.success (or code === 'OK') before reading data: The HTTP status is also correct, but checking the body is cheaper than re-parsing the status.
• Use hasMore, not arithmetic: Trust the server's hasMore flag instead of comparing offset + limit against total; total can shift between paginated requests.
• Build URLs from the active organization id: Keep the organization id in one place (e.g., a client wrapper that prepends /api/user/organizations/{organizationId}/...) so callers cannot forget to scope their requests.
• Parse dates as timezone-aware: ISO 8601 with Z is UTC — do not truncate the trailing Z.
• Surface the code field in logs: It is stable across versions; the human message is not.
• Retry only idempotent methods: Safe to retry on GET, PUT, DELETE; be careful with POST unless the endpoint documents idempotency.

Next Steps

1. Handle failures: Read Error Handling for the full code list.
2. Plan for limits: See Rate Limits before batching calls.
3. Lock down scopes: Pick the right scopes in Scopes & Permissions.
4. Configure SSO (optional): Set up Enterprise SSO for domain-based authentication.
5. Browse endpoints: Jump to the API Reference and start integrating.