FinGoal · Authentication Profile

Fingoal Authentication

Authentication

FinGoal secures its APIs with oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

Financial-ServicesFintechTransaction EnrichmentData EnrichmentPersonal Financial ManagementBankingCategorizationWebhook
Methods: oauth2 Schemes: 2 OAuth flows: clientCredentials API key in:

Security Schemes

Authentication oauth2
· flows: clientCredentials
BearerAuth oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑
generated: '2026-07-19'
method: searched
source: openapi/fingoal-insights-openapi-original.json
docs: https://docs.fingoal.dev/
summary:
  types:
  - oauth2
  oauth2_flows:
  - clientCredentials
notes: >-
  The Insights API is declared as OAuth2 clientCredentials in the OpenAPI, but
  the token is minted by a custom endpoint: POST
  https://findmoney.fingoal.com/v3/authentication with a JSON body
  {"client_id","client_secret"} returns a JWT `access_token`. That JWT is then
  sent as `Authorization: Bearer <token>` on every request. Developer
  credentials are issued on request (24h turnaround) via
  https://fingoal.com/request-developer-account - there is no public self-serve
  signup. Dev credentials target the findmoney-dev host; production the
  findmoney host.
schemes:
- name: Authentication
  type: oauth2
  api: fingoal:fingoal-enrichment-api
  flows:
  - flow: clientCredentials
    tokenUrl: https://findmoney.fingoal.com/v3/authentication
    scopes: 1
  sources:
  - openapi/fingoal-insights-openapi-original.json
- name: BearerAuth
  type: oauth2
  api: fingoal:fingoal-link-money-api
  flows:
  - flow: clientCredentials
    tokenUrl: https://link-money-dev.fingoal.dev/api/oauth/token
    scopes: 1
    scope_names:
    - tenantId
  sources:
  - openapi/_original/fingoal-link-money-openapi-original.json
  notes: >-
    Link Money declares oauth2 clientCredentials but is not RFC 6749 shaped. POST
    /api/oauth/token takes a JSON body of CAMEL-cased {clientId, clientSecret,
    tenantId} and returns {token} - not {access_token, token_type, expires_in}.
    The single declared "scope" is tenantId, which is really a tenancy selector:
    the JWT is valid for 1 hour and grants access to exactly one tenant, so
    multi-tenant integrations must mint one token per tenant. Send it as
    Authorization: Bearer <token>. Tenant access itself is granted out of band -
    email support@fingoal.com; clients cannot create tenants.

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • 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 security artifact
curl "https://apis.io/api/v1/security/fingoal-authentication"
All security posture
curl "https://apis.io/api/v1/security?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.