From ef7e834557c21eeb02f19eb801f801ff153c1154 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 9 Jul 2026 19:39:24 +0000 Subject: [PATCH] docs: fix SAT quick-start example to match the real OpenAPI spec MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The README's "Enroll a User" example posted to a nonexistent `/sat/v1/users` endpoint with an `{email, group_id}` body — SAT has no such route or schema. It also implied a shared `api.hailbytes.com` host, but SAT is self-hosted (openapi server is the relative `/api`). Replaced it with a real, spec-matching example: adding a target via `POST /groups/`. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01K3DKc79upGPwzKoHaeLxFd --- README.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 5feb8bc..f454a7d 100644 --- a/README.md +++ b/README.md @@ -54,13 +54,18 @@ curl -X GET "https://api.hailbytes.com/asm/v1/assets" \ -H "Content-Type: application/json" ``` -### SAT — Enroll a User +### SAT — Add a Target to a Group + +SAT is self-hosted, so requests go to your own SAT deployment rather than a +shared `api.hailbytes.com` endpoint — replace the host below with your +instance's URL. There is no `/users` enrollment endpoint; targets are added +by creating (or updating) a group: ```bash -curl -X POST "https://api.hailbytes.com/sat/v1/users" \ +curl -X POST "https://sat.yourcompany.com/api/groups/" \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ - -d '{"email": "user@example.com", "group_id": "grp_abc123"}' + -d '{"name": "New Hires", "targets": [{"email": "user@example.com", "first_name": "Jane", "last_name": "Doe"}]}' ``` ---