How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Britive Secrets Manager API

The Britive Secret Manager API covers the Britive vault and secrets lifecycle — vault initialization, static and file secrets, secret versions, secret metadata, password policies, secret templates and secret rotation history — plus the shared policy-administration surface (policies, roles, permissions, actions, consumers), the approvals workflow and the notification-medium/notification service.

Britive Secrets Manager API is one of 79 APIs that Britive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Secrets Management, Vault, Policy, and Approvals. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 31 operations across 17 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://{tenantURL}.

31 operations 17 paths 13 schemas 4 DELETE15 GET5 PATCH7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://demo.britive-app.com/api/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Britive Secrets Manager API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 31

Across 17 paths, the API surfaces 31 operations — 4 DELETE, 15 GET, 5 PATCH, 7 POST. Each is listed below with its method, path, parameters, and response codes.

Secrets Manager 31
POST
/api/v1/secretmanager/keys/rotate
Rotate vault encryption key
rotateKey → 202
POST
/api/v1/secretmanager/pwdpolicies
Create password policy for alphanumeric password
createPasswordPolicy 1 param body → 201
GET
/api/v1/secretmanager/pwdpolicies
Get a list of password policies
getPasswordPolicies 2 params → 200
DELETE
/api/v1/secretmanager/pwdpolicies/{id}
Delete a specified password policy
deletePasswordPolicy 1 param → 204
GET
/api/v1/secretmanager/pwdpolicies/{id}
Get specified password policy's details
getPasswordPolicy 2 params → 200
PATCH
/api/v1/secretmanager/pwdpolicies/{id}
Update password policy details
updatePasswordPolicy 1 param body → 204
GET
/api/v1/secretmanager/resourceContainers
Get IDs of all container resources
getResourceContainers 1 param → 200
POST
/api/v1/secretmanager/secret-templates/static
Create StaticSecretTemplate for static secret
createSecretParam body → 201
GET
/api/v1/secretmanager/secret-templates/static
Get static secret template
getSecretParams 2 params → 200
DELETE
/api/v1/secretmanager/secret-templates/static/{id}
Delete static secret template
deleteSecretParam 1 param → 204
GET
/api/v1/secretmanager/secret-templates/static/{id}
Get a specified static secret template
getSecretParam 1 param → 200
PATCH
/api/v1/secretmanager/secret-templates/static/{id}
Update static secret template parameteres
updateSecretParam 1 param body → 204
POST
/api/v1/secretmanager/vault
Create a vault for the Secrets Manager
initializeVault body → 200400
GET
/api/v1/secretmanager/vault
Get details of current active vault
getVaults 2 params → 200
GET
/api/v1/secretmanager/vault/secrets
Get secret in vault hierarchy
getResource 1 param → 200
GET
/api/v1/secretmanager/vault/secrets/{id}
Get a specified secret details
getResourceById 1 param → 200
DELETE
/api/v1/secretmanager/vault/{id}
Delete a specified vault
deleteVault 1 param → 204
GET
/api/v1/secretmanager/vault/{id}
Get vault details
getVault 1 param → 200
PATCH
/api/v1/secretmanager/vault/{id}
Update a specified vault's details
updateVault 1 param body → 204400
POST
/api/v1/secretmanager/vault/{vaultId}/accesssecrets
Access secret at a given path
getSecretDataPost 2 params → 200
GET
/api/v1/secretmanager/vault/{vaultId}/accesssecrets
Get access secrets
getSecretData 2 params → 200
GET
/api/v1/secretmanager/vault/{vaultId}/downloadfile
Download secret file content
downloadFile 2 params → 200
GET
/api/v1/secretmanager/vault/{vaultId}/secret-metadata
Get secret metadata details
getSecretMetaData 2 params → 200
POST
/api/v1/secretmanager/vault/{vaultId}/secrets
Create a node/secret
createSecretData 2 params body → 200400
DELETE
/api/v1/secretmanager/vault/{vaultId}/secrets
Delete node/secret
deleteSecretData 2 params → 204
GET
/api/v1/secretmanager/vault/{vaultId}/secrets
Get Nodes/Secrets on one level under given parent
getOneLevelSecretData 7 params → 200
PATCH
/api/v1/secretmanager/vault/{vaultId}/secrets
Update / Move Secret
updateSecretData 4 params body → 204400403
POST
/api/v1/secretmanager/vault/{vaultId}/secrets/file
Create a secret file
createSecretFileData 3 params body → 200
PATCH
/api/v1/secretmanager/vault/{vaultId}/secrets/file
Update secret file
updateSecretFileData 3 params body → 200
GET
/api/v1/secretmanager/vault/{vaultId}/secrets/{secretId}/versions
List Secret Versions
listSecretVersions 4 params → 200404
GET
/api/v1/secretmanager/vault/{vaultId}/secrets/{secretId}/versions/{version}
Get Secret Data for Version
getSecretDataForVersion 3 params → 200404

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are SecretDataDTO (23 properties), VaultDTO (18 properties), SecretVersionDataDTO (14 properties), PasswordPolicyDTO (12 properties). Each schema is shown below with its type and property counts.

StaticSecretFieldParamsDTO
object
8 properties 3 required
VaultDTO
object
18 properties
Recipients
object
6 properties
SecretDataDTO
object
23 properties
RotationSettingsDTO
object
Rotation target and notification settings embedded in a secret
3 properties
TeamsAppChannels
object
2 properties
AccountDetailsDTO
object
Account on the target resource that receives the updated credential
2 properties
SecretVersionDataDTO
object
14 properties
PasswordPolicyDTO
object
12 properties
StaticSecretTemplateDTO
object
8 properties
RotationTemplateDTO
object
Defines the script/logic the Broker executes to update the credential on the target resource
3 properties
RotationTemplateVariableDTO
object
A single variable used by the rotation template
3 properties
RotationTargetDTO
object
The target resource and account that will be updated during rotation, along with the rotation template the Broker executes
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

britive-secrets-manager-api-openapi.yml Raw ↑

Other APIs Britive publishes across the network.

Britive MCP Server
Britive Access Request Tag Membership API
Britive API Tokens API
Britive Application Environments - Accounts API
Britive Application Environments API
Britive Application Profiles - Advanced Settings API
Britive Application Profiles API
Britive Application Profiles - Permission Constraint Manager API
Britive Application Profiles - Permissions API
Britive Application Profiles - Policies API
Britive Application Profiles - Scopes API
Britive Application Profiles - Session Attributes API
Where this information came from

This is an independent, third-party profile of Britive Secrets Manager API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.