Connect2id Server API

Name: Connect2id Server API
Brand: Connect2id Server API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationbearer, basic18 EndpointsREST

For Agents

Issue and introspect OAuth 2.0 / OIDC tokens, register OIDC clients, and manage authorization sessions on a Connect2id server. Useful for agents that automate IdP client onboarding or token validation.

Install Jentic One Beta

Connect the Connect2id Server API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Connect2id Server API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Connect2id Server API.

Update OIDC client metadata such as redirect URIs, grant types, and token endpoint auth method

Introspect a bearer token to confirm it is active and read its scopes and subject

GET STARTED

Start building with Connect2id Server API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Connect2id Server API for, with concrete tasks.

★ Headless OIDC Client Provisioning

Provision OIDC clients automatically as new services are deployed. The agent calls POST /clients with the client metadata (redirect URIs, grant types, response types) and stores the returned client_id and client_secret in the deployment secret manager. Updates and deletes follow the standard registration endpoints, so client lifecycle stays in lockstep with infrastructure-as-code without operator intervention.

Call POST /clients with redirect_uris=[https://app.example.com/callback] and grant_types=[authorization_code, refresh_token], then write the returned client_secret to the secret store.

Token Introspection in a Resource Gateway

When an API gateway receives a request with a bearer token, it calls POST /token/introspect on the Connect2id server to confirm the token is active and to extract the subject and scopes for authorization decisions. This is the recommended pattern when stateless JWT validation is not enough and you need real-time revocation behavior.

Call POST /token/introspect with token=<access_token> and client credentials, and route the request based on the returned active and scope claims.

Token Revocation on Sign-Out

On user-initiated sign-out, the agent calls POST /token/revoke to invalidate the user's refresh token and POST /session/end (or the discovered end_session endpoint) to terminate their SSO session. This closes the loop on logout in a way that JWT expiry alone cannot, which is important for shared-device scenarios.

Call POST /token/revoke with token=<refresh_token> followed by GET /session/end with id_token_hint=<id_token> to complete sign-out.

AI Agent IdP Operations via Jentic

Wire Connect2id management into an AI assistant used by platform engineers. The agent searches Jentic for register an oidc client, loads the POST /clients schema, and executes it with the master API token isolated in the Jentic vault. The same flow covers updates, deletes, and introspection, so the assistant becomes a thin layer over the IdP control plane.

Through Jentic, search register an oidc client, load the POST /clients schema, and execute it with redirect_uris and grant_types for the new service.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for connect2id server api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/clients

PUT

/clients/{clientId}

Update an OIDC client registration

DELETE

/clients/{clientId}

Delete an OIDC client

POST

/token

Token endpoint (issue access/refresh tokens)

POST

/token/introspect

Token introspection (RFC 7662)

POST

/token/revoke

Token revocation (RFC 7009)

GET

/.well-known/openid-configuration

OpenID Connect Discovery

POST

/clients

PUT

/clients/{clientId}

Update an OIDC client registration

DELETE

/clients/{clientId}

Delete an OIDC client

POST

/token

Token endpoint (issue access/refresh tokens)

POST

/token/introspect

Token introspection (RFC 7662)

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Connect2id master API tokens and client credentials are stored encrypted in the Jentic vault. Agents call operations through scoped Jentic tokens; raw tokens and client secrets never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (for example, register an oidc client) and Jentic returns the matching Connect2id operation with its input schema, so the agent picks the right endpoint without reading the docs portal.

Time to first call

Direct Connect2id integration: 1-2 days to wire client registration, token issuance, and introspection. Through Jentic: under 1 hour for a single workflow — search, load schema, execute.

FAQs

Specific to using Connect2id Server API through Jentic.

Why is there no official OpenAPI spec for Connect2id Server API?

Connect2id documents the API as standards-based REST endpoints in HTML pages but does not ship a single OpenAPI 3 specification. Jentic generates and maintains this spec so that AI agents and developers can call Connect2id Server API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Connect2id Server API use?

Two schemes are supported: HTTP Bearer with a master API token or an access token for management endpoints, and HTTP Basic with client_id and client_secret for client-authenticated calls (token endpoint, introspection, revocation). Through Jentic the credential is held in the vault and inserted server-side.

Can I introspect a bearer token through this API?

Yes. POST /token/introspect implements RFC 7662 and returns whether the token is active along with its scope, sub, exp, and other claims. This is the recommended endpoint for resource servers that need real-time revocation checks rather than relying on JWT expiry alone.

Can I dynamically register OIDC clients?

Yes. POST /clients implements OIDC dynamic client registration. The response returns a client_id and (for confidential clients) a client_secret, plus a registration_access_token that can be used with PUT and DELETE on /clients/{clientId} for subsequent updates.

Where do I get the JWKS for token verification?

GET /jwks.json returns the server's public JSON Web Key Set, which clients use to verify access token and ID token signatures locally. The JWKS URL is also published in the discovery document at GET /.well-known/openid-configuration.

How do I provision an OIDC client through Jentic?

Run pip install jentic, then await client.search('register an oidc client'), load the matching operation schema, and execute it. The underlying call is POST /clients with the client metadata you supply at runtime.

Connect2id Server API

Connect the Connect2id Server API to your agent

Capabilities

Start building with Connect2id Server API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs