Humans API

This reference covers the current IAM human-management APIs in Eve.

Overview

Humans are organization-scoped user accounts with credentials, profile data, and RBAC access levels.

Create User

Create a new user in your organization.

Request

http
POST /api/v1/iam/humans
Content-Type: application/json
Authorization: Bearer <token>

Body Parameters

FieldTypeRequiredDescription
idstringYesUser identifier (email or ID)
passwordstringYesUser password

Example

bash
curl http://{host}:8000/api/v1/iam/humans \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $TOKEN" \
  -d '{
    "id": "developer@company.com",
    "password": "secure_password_123"
  }'

Response

json
{
  "status": "success",
  "data": {
    "message": "User created successfully"
  }
}

Get User

Retrieve details for a specific user.

Request

http
GET /api/v1/iam/humans/{human}
Authorization: Bearer <token>

Path Parameters

ParameterTypeDescription
userstringUser identifier

Example

bash
curl http://{host}:8000/api/v1/iam/humans/developer@company.com \
  -H "Authorization: Bearer $TOKEN"

Response

json
{
  "status": "success",
  "data": {
    "username": "developer@company.com",
    "uuid": "550e8400-e29b-41d4-a716-446655440000",
    "email": "developer@company.com",
    "created_at": "2024-01-15T10:30:00Z",
    "updated_at": "2024-01-15T10:30:00Z"
  }
}

Update User

Update an existing user's information.

Request

http
PATCH /api/v1/iam/humans/{human}
Content-Type: application/json
Authorization: Bearer <token>

Body Parameters

FieldTypeRequiredDescription
passwordstringNoNew password

Example

bash
curl http://{host}:8000/api/v1/iam/humans/developer@company.com \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $TOKEN" \
  -X PATCH \
  -d '{
    "password": "new_secure_password_456"
  }'

Response

json
{
  "status": "success",
  "data": {
    "message": "User updated successfully"
  }
}

Delete User

Remove a user from your organization.

Request

http
DELETE /api/v1/iam/humans/{human}
Authorization: Bearer <token>

Path Parameters

ParameterTypeDescription
userstringUser identifier

Example

bash
curl http://{host}:8000/api/v1/iam/humans/developer@company.com \
  -H "Authorization: Bearer $TOKEN" \
  -X DELETE

Response

Returns 204 No Content on success.

User Identification

Eden supports two formats for user identification:

By User ID (String)

Use email addresses or custom user identifiers:

json
{
  "id": "john.doe@company.com"
}

By UUID

Use UUID format for user identification:

json
{
  "id": "550e8400-e29b-41d4-a716-446655440000"
}

The system automatically detects the format:

  • If parseable as UUID → treated as User UUID
  • Otherwise → treated as User ID string

Access Control

OperationRequired Access
Create userAdmin
Get userAdmin
Update userAdmin
Delete userAdmin

Error Responses

User Already Exists

json
{
  "error": "Conflict",
  "message": "User already exists"
}

User Not Found

json
{
  "error": "Not Found",
  "message": "User not found"
}

Invalid Password

json
{
  "error": "Bad Request",
  "message": "Password does not meet requirements"
}

Insufficient Permissions

json
{
  "error": "Forbidden",
  "message": "Admin access required to manage users"
}

Related

Last updated: July 10, 2026