Galileo Financial Technologies

Galileo Financial Technologies Events API

The Events API from Galileo Financial Technologies — 1 operation(s) for events.

Documentation GitHub OpenAPI

Operations 1

POST /pro/events/webhook-subscriptions #

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/galileo-fs/refs/heads/main/openapi/galileo-fs-events-api-openapi.yml

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/galileo-fs-events-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:
  title: Galileo Financial Technologies Pro Config Events API
  version: '2026-05-23'
  description: 'Best-effort OpenAPI 3.1 sketch of the Galileo Financial Technologies (Pro)

    REST API surface, covering Program (accounts and cards), Config, Dispute 3.0,

    Loan, Payment Hub, Risk, External Transactions, and the Events webhook.

    Endpoint detail is intentionally coarse because Galileo publishes its

    operation-level reference behind reference pages

    (/pro/reference/post_<functionname>); shapes here describe representative

    POST resources. Generated from public documentation; not an official spec.

    '
  contact:
    name: Galileo Pro Documentation
    url: https://docs.galileo-ft.com/pro/
servers:
- url: https://api-sandbox.cv.gpsrv.com
  description: Sandbox
security:
- basicAuth: []
tags:
- name: Events
paths:
  /pro/events/webhook-subscriptions:
    post:
      tags:
      - Events
      operationId: createWebhookSubscription
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/GalileoRequest'
      responses:
        '200':
          $ref: '#/components/responses/GalileoOk'
components:
  schemas:
    GalileoRequest:
      type: object
      description: Galileo Pro form-style request payload. Provider-specific fields apply.
      additionalProperties: true
      properties:
        providerId:
          type: string
          description: Galileo provider id
        username:
          type: string
        password:
          type: string
        productId:
          type: string
        transactionId:
          type: string
    GalileoResponse:
      type: object
      additionalProperties: true
      properties:
        status_code:
          type: integer
        status:
          type: string
        processing_time:
          type: number
        response_data:
          type: object
          additionalProperties: true
  responses:
    GalileoOk:
      description: Successful Galileo response
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/GalileoResponse'
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic
      description: 'HTTPS request authenticated with provider ID, username, password, and

        product ID as documented in the Galileo Pro tenant onboarding guide.

        '