Britive Shared Signals - Catalog API

Manage shared signals catalog data

Operations 1

GET /api/ssf/admin/catalog Get supported shared signals events and Britive actions catalog #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/britive-shared-signals-catalog-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

britive-shared-signals-catalog-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Britive Services API Documentation Shared Signals - Catalog API
  version: v1
  description: API documentation for Users, Tags, Identity providers, Applications, Reporting, Audit logs, Tenants, SSO, Profiles, Password policies, MFA, Access Builder Settings, etc.
servers:
- url: https://{tenantURL}
  description: The primary server
  variables:
    tenantURL:
      default: test.britive-app.com
      description: The host of the server
security:
- bearerAuth: []
tags:
- name: Shared Signals - Catalog
  description: Manage shared signals catalog data
paths:
  /api/ssf/admin/catalog:
    get:
      tags:
      - Shared Signals - Catalog
      summary: Get supported shared signals events and Britive actions catalog
      operationId: getSsfCatalog
      responses:
        '200':
          description: Catalog of supported events and actions
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SsfCatalogResponse'
components:
  schemas:
    BritiveEventTypeDefinition:
      type: object
      required:
      - type
      - displayName
      properties:
        type:
          type: string
          description: EventType.type value (e.g., "user.disable")
        displayName:
          type: string
          description: Human-readable name (e.g., "Disable User")
        description:
          type: string
    SsfEventDefinition:
      type: object
      required:
      - type
      - uri
      - name
      properties:
        type:
          type: string
          description: CAEP or RISC
          enum:
          - CAEP
          - RISC
        uri:
          type: string
          format: uri
        name:
          type: string
        description:
          type: string
    SsfCatalogResponse:
      type: object
      required:
      - events
      - actions
      properties:
        events:
          type: array
          items:
            $ref: '#/components/schemas/SsfEventDefinition'
        actions:
          type: array
          items:
            $ref: '#/components/schemas/BritiveActionDefinition'
        britiveEventTypes:
          type: array
          description: Britive audit event types available for receiver mappings
          items:
            $ref: '#/components/schemas/BritiveEventTypeDefinition'
    BritiveActionDefinition:
      type: object
      required:
      - action
      properties:
        action:
          type: string
          description: Britive action identifier
        description:
          type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
x-api-evangelist:
  assembled_from: https://docs.britive.com/apidocs/ (one OpenAPI fragment per operation page, .md variant)
  assembled_on: '2026-08-08'
  fragments: 372
  note: Britive publishes this contract only as per-operation fragments inside its Document360 API reference. This file is the faithful union of those fragments; the verbatim assembly is in openapi/_original/.