Docs
Sign in
API

REST API

Use the REST API to manage Inth organizations and projects from a server, script, or CI job.

To connect Codex or another MCP client with your Inth account, use Inth MCP instead.

Authentication

The REST API uses organization API keys. These service credentials belong to an organization, not an individual user. Pass the key as a bearer token:

curl https://api.inth.com/v1/projects \
  -H "Authorization: Bearer inth_..."

Create a key in Organization settings > API keys. Inth shows the inth_... secret once. Store it like a deployment credential and never expose it in client-side code.

Each key has access to its organization. See rate limits for plan requirements and request limits.

Responses

Every endpoint wraps its result in a stable envelope:

{ "success": true, "data": {} }

List endpoints return data as an array plus a pagination object. Pass pagination.nextCursor as the cursor query parameter to fetch the next page:

{
	"success": true,
	"data": [{ "projectId": "prj_123" }],
	"pagination": { "nextCursor": "cHJqXzEyMw", "hasMore": true }
}

Errors use the same envelope with success: false and a machine-readable error.code. Validation errors may include an error.details array.

{
	"success": false,
	"error": {
		"code": "NOT_FOUND",
		"message": "Project not found"
	}
}

Every response carries an X-Request-Id header. Include it when reporting an issue.

Stability

Changes within v1 are additive. Clients should ignore fields they do not recognize. Breaking changes use a new version prefix.

Treat resource IDs as opaque strings.

Endpoints

System

Auth

Organizations

Projects