[Curated public integration surface]

API Integrations

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.

What the public surface includes

Public integration guidance is intentionally narrow and stable.

Identity and app registration

Register approved apps, review scopes, and manage governance without exposing tenant-wide internals.

OAuth and service tokens

Use supported token flows for user-delegated access or automation that runs without an interactive user.

Event delivery and webhooks

Create, test, and monitor outbound webhook subscriptions for approved integration workflows.

GraphQL transport contract

Connect to the shared GraphQL transport with bearer auth and tenant scoping, without publishing the full schema.

Public contract example

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 } }"}'

Integration principles

Public where stable

Anything documented publicly is meant to be stable enough for approved third-party integration work.

Reviewed where sensitive

Advanced platform workflows, curated GraphQL bundles, and environment-specific delivery planning stay behind review.

Machine-readable by default

The same public contract is available through `/api/docs`, `llms.txt`, and `llms-full.txt` for automation and indexing.

Need the public contract details?

Open the API reference for the supported surface, or use the integration guide if your workflow needs reviewed access.