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 Shared Signals - Issuers API

Manage shared signals issuers

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

Tagged areas include Shared Signals - Issuers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

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

7 operations 3 paths 7 schemas 1 DELETE3 GET1 PATCH1 POST1 PUT

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 Shared Signals - Issuers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 7

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

Shared Signals - Issuers 7

Manage shared signals issuers

POST
/api/ssf/admin/issuers
Create a shared signals issuer
createSsfIssuer body → 201
GET
/api/ssf/admin/issuers
List configured shared signals issuers for tenant
listSsfIssuers → 200
DELETE
/api/ssf/admin/issuers/{issuerId}
Delete a shared signals issuer
deleteSsfIssuer 1 param → 204
GET
/api/ssf/admin/issuers/{issuerId}
Get a shared signals issuer
getSsfIssuer 1 param → 200
PATCH
/api/ssf/admin/issuers/{issuerId}
Update a shared signals issuer
updateSsfIssuer 1 param body → 200
GET
/api/ssf/admin/issuers/{issuerId}/mappings
Get event-to-action mappings for a shared signals issuer
getIssuerMappings 1 param → 200
PUT
/api/ssf/admin/issuers/{issuerId}/mappings
Replace event-to-action mappings for a shared signals issuer
putIssuerMappings 1 param body → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Issuer (7 properties), CreateIssuerRequest (4 properties), IssuerMappings (3 properties), UpdateIssuerRequest (3 properties). Each schema is shown below with its type and property counts.

PutIssuerMappingsRequest
object
1 property 1 required
Issuer
object
7 properties 5 required
ListIssuersResponse
object
1 property 1 required
UpdateIssuerRequest
object
3 properties
CreateIssuerRequest
object
4 properties 1 required
EventActionMapping
object
2 properties 2 required
IssuerMappings
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

britive-shared-signals-issuers-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 Shared Signals - Issuers 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.