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 Identity Providers API

Manage identity providers and settings

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

Tagged areas include Identity Providers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

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

13 operations 7 paths 20 schemas 1 DELETE5 GET4 PATCH3 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
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 13

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

Identity Providers 13

Manage identity providers and settings

POST
/api/identity-providers
Create a identity provider
identityProviders_6 body → 200
GET
/api/identity-providers
Get a list of all identity providers
identityProviders_5 2 params → 200
GET
/api/identity-providers/password-policy
Get password policy details
getPasswordPolicy → 200
POST
/api/identity-providers/password-policy
Update password policy details
savePasswordPolicy body → 200
GET
/api/identity-providers/types
Get identity provider types
types → 200
DELETE
/api/identity-providers/{id}
Delete a specified identity provider
identityProviders 1 param → 204
GET
/api/identity-providers/{id}
Get details for a specified identity provider
identityProviders_1 1 param → 200
PATCH
/api/identity-providers/{id}
Update specified identity provider's details
identityProviders_3 1 param body → 204
PATCH
/api/identity-providers/{id}/mfa
Enable or disable Multi-factor Authentication (MFA) for users
mfa 1 param body → 200
PATCH
/api/identity-providers/{id}/scim-attribute-mappings
Adds SCIM mappings for an identity provider
scimAttributeMappings 1 param body → 200
POST
/api/identity-providers/{id}/scim-token
Create a token used for SCIM provisioning of users and groups
scimToken_1 1 param body → 201
GET
/api/identity-providers/{id}/scim-token
Get SCIM token details
scimToken 1 param → 200
PATCH
/api/identity-providers/{id}/scim-token
Update token expiration days for the existing SCIM token of an identity provider
scimToken_2 1 param body → 204

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are User (29 properties), Tenant (13 properties), IdentityProviderBeanResponse (13 properties), IdentityProviderBean (13 properties). Each schema is shown below with its type and property counts.

Tenant
object
13 properties
UserAttributeScimMappingHelper
object
4 properties
IdentityProviderBeanPatchRequest
object
4 properties
UserTag
object
12 properties
AdminRole
object
3 properties
PasswordExpirationPolicy
object
2 properties
UserAttributeScimMapping
object
5 properties
CustomUserAttribute
object
4 properties
PasswordPolicyBean
object
7 properties
IdentityProviderBeanMFA
object
2 properties
AttributeMap
object
Single identity provider attribute mapped to service identity custom attribute
2 properties 2 required
AccountLockoutPolicy
object
2 properties
User
object
29 properties
IdentityProviderBeanRequest
object
3 properties
ApiTokenBean
object
11 properties
IdentityProvider
object
6 properties 2 required
ApiToken
object
12 properties
IdentityProviderBeanResponse
object
13 properties
AuditStamp
object
3 properties
IdentityProviderBean
object
13 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

britive-identity-providers-api-openapi.yml Raw ↑

Other APIs Britive publishes across the network.

Britive Secrets Manager API
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
Where this information came from

This is an independent, third-party profile of Britive Identity Providers 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.