Identity and app registration
Register approved apps, review scopes, and manage governance without exposing tenant-wide internals.
Knogin publishes a curated external integration contract for auth, tokens, webhooks, and GraphQL transport. Advanced control-plane workflows and curated bundles move into reviewed access instead of being published as a full blueprint.
Public integration guidance is intentionally narrow and stable.
Register approved apps, review scopes, and manage governance without exposing tenant-wide internals.
Use supported token flows for user-delegated access or automation that runs without an interactive user.
Create, test, and monitor outbound webhook subscriptions for approved integration workflows.
Connect to the shared GraphQL transport with bearer auth and tenant scoping, without publishing the full schema.
This example stays inside the reviewed public contract: obtain a token, then call the GraphQL transport.
# Exchange client credentials for a bearer token
curl -X POST https://auth.knogin.com/v1/oauth/token \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "grant_type=client_credentials&client_id=<client-id>&client_secret=<client-secret>&scope=webhooks:write"
# Call the shared GraphQL transport
curl https://api.knogin.com/graphql \
-H "Authorization: Bearer <access-token>" \
-H "X-Tenant-Id: <tenant-id>" \
-H "Content-Type: application/json" \
-d '{"query":"query HealthCheck { viewer { id } }"}'Anything documented publicly is meant to be stable enough for approved third-party integration work.
Advanced platform workflows, curated GraphQL bundles, and environment-specific delivery planning stay behind review.
The same public contract is available through `/api/docs`, `llms.txt`, and `llms-full.txt` for automation and indexing.