We provide the following REST APIs to help integrate Conjur into your development environments. Click a link below to view documentation for each API.
Most API calls require an authentication access token in the header. The majority of endpoints only accept access tokens, while passwords and API keys are typically supported for authentication-related operations. The different credentials are sent via the Authorization HTTP header. The format requirements for each authentication method are described in Authenticate with REST APIs.
The following APIs enable you manage DAP authentication tasks:
Gets the API key of a user given the username and password via HTTP Basic Authentication.
Gets a short-lived access token, which can be used to authenticate requests to (most of) the rest of the Conjur API.
Changes a user’s password.
Replaces your own API key with a new, securely random API key.
Replaces the API key of another role you can update with a new, securely random API key.
Allows you to check the status of your authenticator.
Provides information about the client making an API request.
A Variable is an access-controlled list of encrypted data values. The values in a Variable are colloquially known as “secrets”.
Only the twenty most recent values in a Variable are retained; this prevents the database from growing without bounds.
The following APIs enable you to manage secret values within specified Variables.
Creates a secret value within the specified Variable.
Fetches the value of a secret from the specified Variable.
Fetches multiple secret values in one invocation.
The following APIs help you to manage Conjur Policies.
Loads or replaces a Conjur policy document.
Adds data to the existing Conjur policy.
Modifies an existing Conjur policy.
The following APIs help you to manage Conjur role-based access controls.
Gets detailed information about a specific role, including the role members.
List members within a role.
Lists resources within an organization account.
The response to this method is a JSON document describing a single resource.
Lists the roles which have the named permission on a resource.
Checks whether a role has a privilege on a resource.
The following APIs enable you to manage Host Factory features.
Creates one or more tokens which can be used to bootstrap applications.
Revokes a token, immediately disabling it.
Creates an application (
The following API lets you manage public key settings.
Shows all public keys for a resource as newline delimited string for compatibility with the authorized keys SSH format.
Once an authenticator is configured and enabled, an authentication request can be sent to Conjur.
Enables you to send an authentication request after the OIDC Authenticator is configured.
When the Azure Authenticator is configured and enabled, an Azure instance can send an authentication request to Conjur.
When the GCP Authenticator is configured and enabled, a GCE instance can send an authentication request to Conjur.