Developer Resources
Headless Auron
Running Auron as a backend with no Auron-built front end involved.
This is the same topic covered in Auron as a Headless Backend: running Auron purely as an API, with no Auron-built interface anywhere in the request path.
Why this matters for a developer specifically
Beyond a person choosing to build their own UI, headless usage also covers backend-to-backend cases with no interface at all: a scheduled job that syncs records, a service that reacts to a webhook and calls back into Auron's API, a pipeline that only ever runs unattended.
Authentication for unattended access
OAuth2 client-credentials grants are what make this practical. A service account gets a token scoped to exactly what it needs, with no human sign-in step required each time it runs.
See API Reference for the endpoints themselves.