Supported integration interfaces
Finsaku supports the MCP server for defined platform operations, configured outbound event-action webhooks, and provider-specific callbacks such as banklink payment confirmations. Finsaku does not provide a general-purpose REST API for customer-built frontends or other third-party applications.
Choose an interface
| Need | Supported interface | Guidance |
|---|---|---|
| Let an authorised AI client inspect or change supported Finsaku configuration | MCP server | Use Finsaku through an MCP client and Configure MCP access for AI agents. |
| Notify a customer-controlled system after a Finsaku event | Custom event-action webhook | Event actions and Integration data flows. |
| Receive a payment-provider result | Provider-specific callback | Configure the supported provider under Administration → Integrations. The callback address and signing behaviour belong to that provider setup. |
| Extract data for lists or reporting | Saved query export or the configured business-intelligence connection | Lists, search, and export and Portfolio and income views. |
| Build a third-party frontend or call a general REST API | Not supported | Finsaku does not provide a public REST API for third-party applications. |
MCP access
The standard MCP server address is https://mcp.finsaku.com/mcp. A tenant with a custom domain must use its supplied tenant-specific address. The client must support remote MCP, OAuth discovery, dynamic client registration, and PKCE.
MCP calls use the signed-in user's tenant, affiliation, and effective permissions. The available tool set is narrower than the complete browser interface. Read the current tool descriptions instead of assuming that every screen action is available.
Outbound webhooks
A custom webhook can use GET, POST, PUT, PATCH, DELETE, HEAD, or OPTIONS, with configured headers, an expected response status, and a Handlebars request body. Use the payload preview to inspect resolved data before enabling the action.
The receiving system should:
- authenticate the request using the approved configured header or network control;
- validate the method, path, media type, and expected schema;
- treat credentials and personal data in the request as protected information;
- recognise a repeated event without applying the business change twice;
- return only the configured success status after accepting the operation;
- retain a correlation reference that can be compared with Finsaku execution history.
Do not embed long-lived secrets or customer information directly in a reusable template when a protected integration setting or runtime value should supply it.
Compatibility and change control
For MCP, use the server's current tool descriptions and verify changes in a non-production or controlled tenant. For custom webhooks, the customer owns the receiving schema and should version it when a change is not backward compatible.
Where Finserio supplies an integration-specific API specification, that specification defines the supported authentication, permissions, environments, schemas, pagination, errors, idempotency, rate limits, and compatibility rules.