By the end of this quickstart, an app key will be minted, Slack will be connected, and a message will be posted from application code — with no token ever touching that code. Total time: about 10 minutes.Documentation Index
Fetch the complete documentation index at: https://docs.alterauth.com/llms.txt
Use this file to discover all available pages before exploring further.
This quickstart uses Slack as the target API. Any of the 65+ OAuth providers in the provider catalog follows the same flow — only the API call at the end changes.
Sign up
Create a free account at portal.alterauth.com.
Create an app
In the portal sidebar, choose Apps → New App. Name it
quickstart and click Create.An app is the unit that owns API keys, provider configuration, and grants. See Apps & Organizations for the full model.Mint an API key
Open the new app, go to API Keys → Mint key, copy the value, and export it:The plaintext is shown once. If lost, mint a new key and revoke the old one.
Connect Slack
Run the snippet below once. It opens a browser, walks through the Slack OAuth flow, and prints the Export the printed grant ID:
grant_id used in the next step.What just happened
app.request() resolved the Slack grant, fetched a fresh token from the vault, injected it into the outgoing Slack call, and wrote the audit row. No token was ever stored, refreshed, or seen by application code.
What’s next
How Alter works
The mental model behind the call sequence above.
Call APIs on behalf of users
Drop the
grant_id and resolve users from JWTs in production.Give an agent scoped access
Per-agent identity for AI workloads.