FinCore Engine API

Manage multi-tenant accounting data via FinCore Engine REST endpoints.

Updated Sep 1, 2025
One-click install
npx skills add https://github.com/Bendomey/fincore-engine --skill fincore-engine-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: FinCore Engine API
Source: https://github.com/Bendomey/fincore-engine/tree/main/api
Command: npx skills add https://github.com/Bendomey/fincore-engine --skill fincore-engine-api

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline integration with FinCore Engine API to enable programmatic access to multi-tenant accounting operations from your applications.

Core Features & Use Cases

  • Manage tenants (clients) via registration and authentication, and perform CRUD on accounts with hierarchical structure.
  • Record and manage double-entry journal entries with draft/post lifecycle, including line-level validation.
  • Retrieve data and integrate with fintech/ERP workflows, generate audit-friendly records, and automate accounting tasks.

Quick Start

Register a client to obtain credentials, then create accounts and a journal entry and finally post it.

Frequently Asked Questions about FinCore Engine API

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authenticate REST API requests for double-entry accounting operations?

Authenticate double-entry accounting REST API requests by including the X-FinCore-Client-Id and X-FinCore-Client-Secret headers in every call to manage clients, accounts, and journal entries.

Can I manage multi-tenant accounting data through a REST API?

Yes, you can manage multi-tenant accounting data via REST endpoints to perform CRUD operations on hierarchical accounts and handle tenant registration directly from your applications.

How do I post double-entry journal entries with line-level validation?

Post double-entry journal entries by first drafting them with line-level validation, then transitioning the entry to the post lifecycle state via the FinCore Engine API.

Does the FinCore Engine API use a production base URL by default?

Yes, the FinCore Engine API uses the production base URL by default, requiring authenticated headers to access your multi-tenant accounting data and post journal entries.

What's the best way to automate fintech workflows with double-entry validation?

Automate fintech workflows by using the FinCore Engine API to register clients, create hierarchical accounts, and post journal entries with built-in double-entry validation for audit-friendly records.

Why do my journal entries need a draft and post lifecycle?

The draft and post lifecycle ensures journal entries undergo line-level validation before being finalized, generating audit-friendly records suitable for automated accounting and ERP workflows.