FINOS

FINOS CertificateAuthentication API

The CertificateAuthentication API from FINOS — 2 operation(s) for certificateauthentication.

Documentation GitHub OpenAPI

Operations 2

POST /v1/authenticate Authenticate.

POST /v1/logout Logout.

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/finos-certificateauthentication-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  version: 20.14.1
  title: Authenticator Certificate Authentication API
  description: 'For bots and other on-premise processes to authenticate. Once

    authenticated, the bot will be able to use the methods described in

    serviceAPI.yaml and agentAPI.yaml.


    Connections to the servers will be over

    client authenticated TLS, the servers for this API will perform the

    authentication by inspecting the certificate presented by the

    SSLSocketClient.


    There will be two implementations of this API, one on your Pod

    and one on the Key Manager. In order to fully authenticate,

    an API client will have to call both of these implementations

    and pass both of the session tokens returned as headers in all

    subsequent requests to the Symphony API.

    '
tags:
- name: CertificateAuthentication
paths:
  /v1/authenticate:
    post:
      summary: Authenticate.
      description: 'Based on the SSL client certificate presented by the TLS layer, authenticate

        the API caller and return a session token.

        '
      tags:
      - CertificateAuthentication
      responses:
        '200':
          description: OK.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Token'
        '400':
          description: Client error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: 'Forbidden: Certificate authentication is not allowed for the requested user.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Server error, see response body for further details.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /v1/logout:
    post:
      summary: Logout.
      description: 'Logout a users session.

        '
      parameters:
      - name: sessionToken
        description: the session token to logout.
        in: header
        required: true
        schema:
          type: string
      tags:
      - CertificateAuthentication
      responses:
        '200':
          description: OK.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessResponse'
        '400':
          description: Client error.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: 'Forbidden: Certificate authentication is not allowed for the requested user.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '500':
          description: Server error, see response body for further details.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      properties:
        code:
          type: integer
          format: int32
        message:
          type: string
    Token:
      type: object
      properties:
        name:
          description: 'The name of the header in which the token should be presented on subsequent API calls.

            '
          type: string
        token:
          type: string
          description: 'Authentication token that should be passed as header in each API rest calls.

            This should be considered opaque data by the client. It is not intended to contain any data interpretable by the

            client. The format is secret and subject to change without notice.

            '
        authorizationToken:
          type: string
          description: "(Beta) Short lived access token built from a user session. This field is still on Beta, please continue using \nthe returned \"token\" instead.\n"
    SuccessResponse:
      type: object
      properties:
        message:
          type: string