Authdog
Console

API

Last updated Jul 11, 2026
View as Markdown

The Authdog REST API lets you manage identity resources programmatically — everything the console does, plus provisioning and event streams. This page is the map; the live per-endpoint reference lives at api.authdog.com.

Base URL and authentication

All endpoints live under /v1/.... The base URL for your environment comes from NEXT_PUBLIC_API_ENDPOINT; requests proxy through to the platform. Authenticate every call with a Bearer token:

Bash
curl "$NEXT_PUBLIC_API_ENDPOINT/v1/users" \
  -H "Authorization: Bearer $AUTHDOG_API_TOKEN"

Tokens are scoped to a single environment, so keys, users, and connections never leak across environments.

Resource families

The core resources mirror the console:

  • Users — accounts, profiles, credentials, sessions. See Users.
  • Organizations — tenants your users belong to and their memberships. See Organizations.
  • Roles & permissions — the RBAC objects you assign to users and orgs.
  • Connections — social OAuth2 and enterprise SSO configurations.
  • Events — the Events API lists identity events (sign-ins, provisioning changes, and more) for auditing and sync.

Provisioning endpoints

For automated user lifecycle from external systems:

  • SCIM 2.0 at /v1/scim/v2, authenticated with adscim_ tokens — standard provisioning from IdPs like Okta and Entra ID.
  • HRIS at /v1/hris/v1, authenticated with adhris_ tokens — inbound employee and department sync from HR systems.

Both are covered in Provisioning and configured per environment in the console.

Webhooks

Subscribe to identity events and Authdog delivers them to your endpoint. Each request is HMAC-signed with an X-Authdog-Signature: t=...,v1=... header — verify it before trusting the payload. Delivery uses durable retry, so a temporary outage on your side won't drop events.

Next steps