HTTP Endpoint

HTTP endpoints connect Eve to REST and GraphQL APIs so users, applications, and agents can call external services through a governed path.

Endpoint Kind

Use http as the endpoint kind when creating this endpoint through the API or dashboard.

What Eve Uses HTTP Endpoints For

Route REST and GraphQL API calls through Eden RBAC.
Centralize API base URLs, headers, and authentication material.
Expose selected external APIs to Adam and approved tools.
Audit outbound API calls from users, applications, and agents.
Build workflows that combine internal data, LLM calls, and external service calls.

Basic Endpoint Shape

json

{
  "endpoint": "billing-api",
  "kind": "http",
  "config": {
    "base_url": "https://api.example.com/v1",
    "auth": {
      "type": "bearer",
      "token": "secret"
    }
  },
  "description": "Billing service API"
}

Create it with the endpoint API:

bash

curl -sS -X POST "$EDEN/endpoints" \
  -H "$AUTH_HEADER" \
  -H "Content-Type: application/json" \
  -d '{
    "endpoint": "billing-api",
    "kind": "http",
    "config": {
      "base_url": "https://api.example.com/v1",
      "auth": {
        "type": "bearer",
        "token": "secret"
      }
    },
    "description": "Billing service API"
  }'

Configuration Fields

Field	Purpose
`base_url`	Base URL for the API.
`token`	Bearer token or API key when the service uses token authentication.
`graphql`	Optional flag for GraphQL-style endpoints.

Operating Notes

Treat outbound API calls as production side effects unless the endpoint is explicitly read-only.
Create separate endpoints for staging, sandbox, and production APIs.
Keep service tokens out of client applications and local scripts; route calls through Eve when governance or audit is required.
Document allowed paths, methods, and payload shapes before exposing an HTTP endpoint to agents.