DbSecure API

Name: DbSecure API API
Brand: DbSecure API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationbasic, apiKey3 EndpointsREST

For Agents

Mint, introspect, and revoke OAuth 2.0 access tokens for Larcier Group's DbSecure identity provider so an agent can authenticate against downstream Larcier services.

Quickstart

Get started with DbSecure API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"mint a DbSecure access token"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with DbSecure API API.

Exchange client credentials for an OAuth 2.0 access token at /oauth2/token

Retrieve the user record associated with a bearer token via /oauth2/info

Revoke an issued access token through /oauth2/revoke

Authenticate the token endpoint with HTTP Basic using client_id and client_secret

GET STARTED

Start building with DbSecure API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for DbSecure API, keeping it validated and agent-ready.

DbSecure is Larcier Group's identity provider, exposing a small OAuth 2.0 surface for issuing, inspecting, and revoking access tokens used by Larcier's legal information products. The API supports the client credentials flow with HTTP Basic at the token endpoint, then bearer tokens for follow-on calls. It is a minimal three-endpoint surface focused purely on token lifecycle and userinfo retrieval, not full identity management.

Use Cases

Patterns agents use DbSecure API API for, with concrete tasks.

★ Server-to-server token issuance for Larcier clients

Backend services that consume Larcier legal data products need short-lived access tokens before calling protected endpoints. DbSecure issues these via the OAuth 2.0 client credentials grant at /oauth2/token, authenticated with HTTP Basic over the client_id and client_secret. Tokens are bearer-format and the response carries the standard expiry, making rotation straightforward for scheduled jobs and integration workers.

POST to /oauth2/token with grant_type=client_credentials and an HTTP Basic header, then store the returned access_token and expires_in for reuse.

Userinfo lookup for downstream authorisation

When a Larcier-integrated app receives a bearer token, it can call /oauth2/info to retrieve the user record that the token represents. This is used for mapping the upstream Larcier identity into a local session, applying entitlements, or auditing which user performed an action. The endpoint requires the Bearer scheme with the issued access token in the Authorization header.

POST to /oauth2/info with Authorization: Bearer {access_token} and parse the returned user object into the local session.

Token revocation on logout or compromise

When a user signs out of a Larcier-integrated workflow or a token is suspected of leakage, the issuing system must revoke it explicitly. DbSecure exposes /oauth2/revoke for this purpose, immediately invalidating the access token so any subsequent userinfo or downstream call fails. This is the recommended path for compliance-sensitive deployments where token lifetime alone is insufficient.

POST to /oauth2/revoke with the token to invalidate and confirm the 200 response before clearing local session state.

AI agent authenticating to Larcier through Jentic

An AI agent that needs to query Larcier legal content can use Jentic to discover DbSecure's token endpoint, fetch credentials from the encrypted vault, and exchange them for a bearer token without ever placing the client secret in the model context. The agent then attaches the access token to follow-on calls and revokes it cleanly when the workflow finishes, keeping every credential interaction inside Jentic's MAXsystem.

Search Jentic for 'mint a DbSecure access token', execute /oauth2/token, attach the bearer token to the next downstream call, and revoke it via /oauth2/revoke when done.

Key Endpoints

3 endpoints — dbsecure is larcier group's identity provider, exposing a small oauth 2.

METHOD

PATH

DESCRIPTION

POST

/oauth2/token

Generate access token via client credentials

POST

/oauth2/info

Retrieve user data for a bearer token

POST

/oauth2/revoke

Revoke an issued access token

POST

/oauth2/token

Generate access token via client credentials

POST

/oauth2/info

Retrieve user data for a bearer token

POST

/oauth2/revoke

Revoke an issued access token

Why though Jentic?

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

Credential isolation

DbSecure client_id and client_secret are stored encrypted in the Jentic vault (MAXsystem). Agents call the token endpoint through Jentic and receive scoped access tokens — the raw client secret never enters the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g., 'mint a DbSecure access token') and Jentic returns the matching /oauth2 operation with its input schema, so the agent calls the right endpoint without browsing Larcier's docs.

Time to first call

Direct DbSecure integration: half a day for OAuth 2.0 client credentials, token caching, and revocation hooks. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auth0 Management API

General-purpose identity platform with full user management, social logins, and enterprise SSO.

Choose Auth0 when you need user signup, MFA, or multi-tenant identity rather than just token issuance for one vendor's products.

Alternative

Okta API

Enterprise identity and SSO platform with directory services and lifecycle management.

Choose Okta for enterprise workforce identity and SCIM-driven provisioning that DbSecure does not cover.

Complementary

Salesforce API

CRM that legal-tech workflows often pair with Larcier content for matter and contact management.

Use alongside DbSecure when a legal content workflow needs to read or write matter and contact records in Salesforce.

FAQs

Specific to using DbSecure API API through Jentic.

What authentication does the DbSecure API use?

DbSecure uses two schemes. The /oauth2/token endpoint authenticates with HTTP Basic over your Larcier client_id and client_secret, and the /oauth2/info and /oauth2/revoke endpoints take a Bearer token in the Authorization header. Through Jentic, both credential pairs stay in the encrypted vault and never enter the agent's context window.

Can I introspect a DbSecure token to see who it belongs to?

Yes. POST to /oauth2/info with Authorization: Bearer {access_token} and DbSecure returns the user record associated with that token. This is useful for mapping the Larcier identity into your local session or applying per-user entitlements.

What are the rate limits for the DbSecure API?

The published OpenAPI spec does not document explicit rate limits for DbSecure. Treat the token endpoint as a hot path and cache access tokens until their expires_in elapses rather than minting a new token per request.

How do I mint a DbSecure access token through Jentic?

Run pip install jentic, then search for 'mint a DbSecure access token'. Jentic returns the /oauth2/token operation with its input schema. Load the operation, supply grant_type=client_credentials, and execute. Jentic handles the HTTP Basic header from the stored credentials and returns the access_token directly.

Is the DbSecure API a general-purpose user management system?

No. The spec exposes only three endpoints, all under /oauth2: token issuance, userinfo, and revocation. There are no endpoints for creating users, resetting passwords, or managing groups. DbSecure is purely a token-issuance surface for downstream Larcier products.

How do I revoke a DbSecure token when a user logs out?

POST to /oauth2/revoke with the access token to invalidate. After a 200 response, any subsequent call to /oauth2/info with that token will fail. Pair this with clearing the local session to keep the lifecycle clean.