Documentation

Getting Started

Base URLs, integration paths, and the shortest working flow.

Getting Started

Fleet Core exposes two integration paths.

  1. Admin and customer REST APIs use JWT auth through the public gateway.
  2. Customer-owned connectors use signed HTTP ingest with HMAC headers.

Base URLs

Gateway: https://api.outlog.serv.si/api/v1
Ingest:  https://ingest.outlog.serv.si
Local:   http://localhost:3000/api/v1

First REST Call

curl -sS \
  -X POST https://api.outlog.serv.si/api/v1/auth/login \
  -H 'content-type: application/json' \
  -d '{"email":"ops@example.com","password":"secret-password"}'

Use the returned access token as Authorization: Bearer <access-token>. Customer-scoped routes also require X-Customer-Id.

First Connector Call

Create a connector in admin-web, store the one-time secret, then sign every request to /ingest/http/* with the connector HMAC headers. Use the connector ingest tool in this portal to test signatures before writing code.