canonical: https://jentic.com/apis/quickfile.co.uk/quickfile # QuickFile Accounting API UK based cloud accounting software. Manage your accounts and bookkeeping in the cloud. QuickFile is simple to use, fast and free! All requests are POST with JSON bodies to method-named endpoints. The API exposes 55 endpoints secured with apiKey authentication. ## For AI agents Programmatically search bank transactions, create a bank account. Covers 55 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for finance and accounting only. ## Capabilities - Search bank transactions - Create a bank account - Get bank accounts - Delete a client - Access QuickFile Accounting API finance resources via REST API ## Use cases ### Finance and Accounting Operations Use the QuickFile Accounting API to perform finance operations programmatically. The API provides 55 endpoints covering core functionality including search bank transactions, create a bank account, create bank transaction. Example prompt: Call POST `/d/v1_2/Bank_Search` to search bank transactions ### Automated Bank Management Automate bank operations by combining multiple QuickFile Accounting API endpoints. Agents can create a bank account and then create bank transaction in a single workflow. Example prompt: Call POST `/d/v1_2/Bank_CreateAccount` to create a bank account, then verify the result ### AI Agent Integration via Jentic AI agents discover and call QuickFile Accounting API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually. Example prompt: Search Jentic for 'search bank transactions', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/d/v1_2/Bank_Search` | Search bank transactions | | POST | `/d/v1_2/Bank_CreateAccount` | Create a bank account | | POST | `/d/v1_2/Bank_CreateTransaction` | Create bank transaction | | POST | `/d/v1_2/Bank_GetAccounts` | Get bank accounts | | POST | `/d/v1_2/Bank_GetAccountBalances` | Get bank account balances | | POST | `/d/v1_2/Client_Create` | Create a client | | POST | `/d/v1_2/Client_Delete` | Delete a client | | POST | `/d/v1_2/Client_Get` | Get a client | ## Key resources - **Bank** — Bank account and transaction methods - **Client** — Client management methods - **Document** — Document upload methods - **Estimate** — Estimate management methods - **Invoice** — Invoice management methods ## Why Jentic - **Setup:** Wiring the QuickFile Accounting API by hand means building its MD5 hash of account number, API key, and submission number, registering an Application ID, and shaping each RPC-style POST to api.quickfile.co.uk yourself. Through Jentic you install once, import the QuickFile Accounting API from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** QuickFile exposes RPC-style operations like Bank_Search and Client_Create rather than a resource id in the path, so scope by operations: limit the agent to the operations it needs, such as searching bank transactions or creating a client. You choose which operations are in that set, so destructive ones like deleting a client are not included unless you add them. - **Credential handling:** Your QuickFile API key and Application ID are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'search bank transactions' or 'create a client', and Jentic returns the matching QuickFile operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Plaid** — Alternative finance API - **Xero** — Alternative finance API ## FAQ ### What authentication does the QuickFile Accounting API use? The QuickFile Accounting API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I search bank transactions with the QuickFile Accounting API? Yes. Use the POST `/d/v1_2/Bank_Search` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the QuickFile Accounting API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I search bank transactions through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search bank transactions'. Jentic returns the matching QuickFile Accounting API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the QuickFile Accounting API have? The QuickFile Accounting API exposes 55 endpoints covering bank, client, document operations. ### Can I limit what my agent is allowed to do with the QuickFile Accounting API? Yes. Because Jentic One is self-hosted by you, your own rules decide which QuickFile operations and credentials the agent may use. Since QuickFile exposes RPC-style operations such as Bank_Search, Bank_CreateAccount, and Client_Create rather than resource ids in the path, you scope by operation and grant the agent only the ones it needs, like searching bank transactions or creating a client. Destructive operations such as Client_Delete stay out of that set unless you deliberately add them.