Date: 2026-03-31 Status: Research complete
Agicap is a cloud-based treasury and cash flow management platform serving 8,000+ SMB/mid-market customers across 10+ European countries and the US. It is not an accounting system — it sits alongside ERPs and accounting software as a cash management overlay, handling cash forecasting, payment automation, bank reconciliation, and AP invoice management.
Agicap has a public REST API (api.agicap.com) with OAuth2 client_credentials authentication. The documented API surface is currently narrow — the primary public API is the Treasury Bank Journal API for exporting bank accounting entries. However, Agicap also has a Card Expenses Bank Journal API, and their integrations page advertises full public API access for custom connectors. The full API scope behind the developer portal (which requires authentication) likely includes additional endpoints.
For Orcha, the most viable integration paths are: (1) Chift unified API — Agicap is an active Chift customer, and Chift's accounting API covers invoice import and journal export across multiple accounting systems; (2) Celigo iPaaS — has a dedicated Agicap connector with pre-built operations; (3) Direct API — for bank journal export and potentially other endpoints discoverable after obtaining API credentials.
| Capability | Available? | Method | Confidence | Notes |
|---|---|---|---|---|
| Bank journal export | Via REST API v1 | GET/POST /public/treasury-bank-journal/v1/entities/{entityId}/exports |
High | Documented in official API guide with Python examples. Up to 5000 entries per export. |
| Card expenses journal export | Via REST API v1 | Endpoint at api.agicap.com/api-details/card-expenses-bank-journal-v1 |
Medium | Endpoint referenced in developer portal URL, but no public documentation found. |
| Invoice import (into Agicap) | Via email, mobile scan, PDF upload, bulk upload, or third-party tools | UI + OCR; API endpoint not publicly documented | Medium | Agicap has built-in OCR for invoice capture. GetMyInvoices pushes invoices via API. No public endpoint docs for direct invoice submission. |
| Invoice export (to accounting) | Via Chift unified API or native connectors | Purchase journals exported to ERPs via Chift or built-in connectors | High | Confirmed by Chift case study: pre-accounting data (purchase + bank journals) flows to accounting software. |
| Chart of accounts sync | Automatic tagging per supplier/cost center | Built-in feature; API access not documented | Medium | Product page states "Automatically tag every expense to the correct chart of accounts." API access unclear. |
| Supplier master data | Created during import via Chift | Chift creates supplier accounts in accounting software | Medium | Chift case study confirms supplier account creation. Direct API endpoint not documented. |
| Entity/organization listing | Via REST API v1 | GET /public/organizations/v1/{organizationId}/entities |
High | Documented in Bank Journal API guide. |
| DATEV integration | Native connector | Pre-posting + one-click export via DATEV API | High | Agicap has a dedicated DATEV interface for the German market. |
| Webhooks / event notifications | Not found in documentation | — | Low | No evidence of webhook support in any source reviewed. |
| SFTP data exchange | Supported | SFTP connections for bank statements, payment files | High | Product page confirms "two-way data sync through API or SFTP." |
| Multi-currency support | Yes | Built into OCR and payment processing | High | Product page confirms currency detection during OCR. |
| Rate limits | Not documented | — | Low | No rate limit information found in any public source. |
Agicap is a cloud-only SaaS platform for cash flow management and treasury operations, founded in 2016 in Lyon, France.
"The AI-powered platform connecting your banking and accounting flows to unlock trapped liquidity." — agicap.com
"leading cash flow management software for SMBs and mid-market companies" — agicap.com
"more than 8,000 customers across international markets" — GlobeNewsWire
Core capabilities:
Market presence: France, Germany (DACH), Italy, UK & Ireland, Spain, Netherlands, US. ~650 employees. Over EUR 150M raised.
Role in accounting workflow: Agicap is explicitly a treasury/cash flow overlay, not an accounting system. It connects to banks (via SWIFT, H2H, EBICS) and ERPs/accounting software (via API, SFTP) for bidirectional data exchange.
"Cash management, cash forecasting, payments and transfers, collections, and bank reconciliation. All on one platform." — agicap.com
Confidence: High — based on official product pages and press releases.
Agicap is an active Chift customer, using Chift's unified accounting API to handle integrations with accounting software across multiple countries.
"Building integrations involves development costs but even higher maintenance costs... Strategically it makes more sense to partner with experts." — Nicolas Mille, Product Manager, Agicap (Chift case study)
Connected accounting systems via Chift: Pennylane, ACD, Cegid, MyUnisoft, Sage, Horus.
Data flows through Chift:
Implementation: Agicap uses Chift's "no-code Sync" approach — pre-built integration flows rather than coding against Chift's API directly.
"The setup and integration process is very simple for our clients on each supported software." — Hind Bidal, Product Manager, Agicap (Chift case study)
Confidence: High — first-party case study with named Agicap employees.
Celigo added an Agicap connector in their November 2024 release.
Authentication setup: Sign into Agicap → Organization settings → Advanced settings → API settings → Generate new credentials → Copy Client ID and Client Secret.
Capabilities: Pre-built flow steps for Agicap API operations. If an endpoint isn't listed as a pre-built operation, users can switch to HTTP mode and configure endpoints from Agicap's API documentation manually.
Confidence: High — documented in Celigo Help Center (connection setup, available APIs). Note: the specific list of pre-built Agicap operations in Celigo returned 403 when fetched — the exact operations are unconfirmed.
No Agicap connector found. Maesn's integrations page lists ERPs and accounting systems (DATEV, Business Central, Abacus, sevDesk, etc.) but does not list Agicap. This is expected — Maesn focuses on ERP/accounting unified APIs, while Agicap is a treasury tool, not an accounting system.
Confidence: Medium — based on reviewing Maesn's integrations page. Agicap is absent from their listed integrations.
No dedicated Agicap connectors found on Make.com or Zapier. Neither platform lists Agicap as a native integration.
Confidence: Medium — based on search results. Agicap could potentially be connected via HTTP/webhook modules using the public API.
Codeless Platforms offers an Agicap connector for their BPA Platform (enterprise iPaaS).
"automatically retrieve open supplier invoices from expenses systems to feed cash flow forecasts with expenses in real time" — Codeless Platforms
Confidence: Medium — based on product page. No technical details about operations supported.
GetMyInvoices has a direct integration to push invoices into Agicap via API.
"Using an API interface, you can automatically import invoices from GetMyInvoices into Agicap." — GetMyInvoices
This confirms that Agicap has an API endpoint for invoice import, even though it isn't publicly documented.
Confidence: High — partnership confirmed on both sides.
Agicap uses OAuth2 client_credentials grant for API authentication.
Token endpoint: POST https://api.agicap.com/public/auth/v1/token
Parameters:
client_id: <your_client_id>
client_secret: <your_secret_client>
grant_type: client_credentials
scope: agicap:public-api
Content-Type: application/x-www-form-urlencoded
Token usage: Bearer token in Authorization header for all subsequent API calls.
Token lifetime: Limited validity (typically a few hours). Check expires_in in the authentication response and renew before expiry.
Credential generation:
https://app.agicap.com/fr/app/organization-advanced-settings/public-api/clientsEach credential set has a configurable scope (visible as "1 scope" in the UI screenshot from the documentation).
Developer portal: https://api.agicap.com/ — requires authentication to view full API documentation.
Sandbox/trial: No sandbox environment referenced in any documentation. The API tracker at apitracker.io also lists sandbox as unavailable.
Confidence: High — documented in official Bank Journal API guide (PDF) with code examples.
Agicap supports multiple methods for getting invoices into the system:
UI-based methods:
"Automatically separate invoices when uploading in bulk. Extract the information you need with industry-leading OCR technology." — agicap.com/en/products/account-payable/
OCR and data extraction:
API-based import:
Approval workflows:
"Set up approval flows based on supplier, amount, or cost centre. Instantly notify the right people to keep everything running smoothly." — agicap.com
Agicap's pre-accounting feature prepares purchase and bank journals, then exports them to accounting software:
"Automatically export entries to your ERP and keep your chart of accounts in sync." — agicap.com
Export methods:
Confidence: Medium-High. Invoice import API exists (proven by GetMyInvoices integration) but endpoint is not publicly documented. Invoice/journal export is well-documented via Bank Journal API and Chift.
Agicap maintains internal category structures for cash flow categorization and can sync with ERP chart of accounts.
"Automatically tag every expense to the correct chart of accounts based on supplier or cost centre." — agicap.com
No public API endpoint found for reading or writing chart of accounts data. The sync appears to happen through native ERP connectors or Chift.
Supplier data exists within Agicap's AP module. When using Chift, new supplier accounts can be created in the connected accounting software during invoice import.
No public API endpoint found for supplier CRUD operations.
Agicap supports cost center-based categorization and approval workflows. No public API endpoint for cost center management found.
The one documented master data endpoint is entity listing:
GET /public/organizations/v1/{organizationId}/entities
Returns entities associated with an Agicap organization, with pagination support (pageNumber, pageSize).
Confidence: Low-Medium for most master data. The entity listing endpoint is confirmed (High), but chart of accounts, suppliers, and cost centers have no documented API access. These may exist behind the authenticated developer portal.
The primary documented API for accessing historical data. Allows exporting bank accounting entries from Agicap.
Base URL: https://api.agicap.com/public/treasury-bank-journal/v1/entities
Endpoints:
| Method | Path | Description |
|---|---|---|
| GET | /{entityId}/exports |
List history of all previous exports (identifiers, dates, entry counts, year indices, writing index ranges) |
| GET | /{entityId}/exports/{exportId} |
Get full contents of a specific export (metadata + detailed list of writings) |
| POST | /{entityId}/exports/{exportId} |
Create new export — exports all "Ready to export" entries, upgrades them to "Exported" status |
Key details:
exportId for POST must be a UUID generated by the callerafter/before parameters (ISO8601 dates)currentExportCounts parameter for first export of the year (to ensure numbering continuity with journals created outside Agicap):
currentBankJournalsCountInYear: Number of bank journals already created this yearcurrentBankJournalEntriesCountInYear: Number of entries already created this yearAn endpoint exists at api.agicap.com/api-details/card-expenses-bank-journal-v1 for retrieving card expense bank journal entries. No public documentation found beyond the URL reference.
Confidence: High for Treasury Bank Journal API (official PDF guide with code examples). Medium for Card Expenses API (URL exists but no docs).
The Bank Journal API has a built-in status model:
This provides synchronous feedback on export operations.
No webhook or callback mechanism found in any documentation reviewed. The API appears to be purely request-response (synchronous).
Agicap tracks payment status internally (AP automation includes payment scheduling and execution), but no API endpoint for querying payment status was found in public documentation.
Confidence: High for export status model. Low for webhooks (no evidence found). Low for payment status API.
| Question | Why It Matters | What Was Tried | Next Step |
|---|---|---|---|
| What additional API endpoints exist behind the developer portal? | The portal likely has invoice, supplier, and category endpoints that aren't publicly visible. This determines whether direct API integration is viable beyond journal export. | Attempted to fetch api.agicap.com/apis and api.agicap.com/guides — both returned only portal shell (requires auth). Searched for specific endpoint names. | Obtain Agicap API credentials (requires admin account) and review the full OpenAPI spec / Postman collection behind the developer portal. |
| What are the specific Celigo pre-built Agicap operations? | Celigo's operation list would reveal which Agicap API endpoints are production-ready. | Attempted to fetch Celigo help article (403). Found connection setup docs but not operation list. | Access Celigo docs with an authenticated account, or contact Celigo support for the Agicap connector operation list. |
| Does Agicap have an API endpoint for invoice submission? | GetMyInvoices proves one exists, but the endpoint/schema is unknown. Critical for pushing Orcha-extracted invoices into Agicap. | Searched for invoice API endpoints. GetMyInvoices confirms API import works. No public endpoint docs found. | After obtaining API credentials, check the Postman collection at postman.com/agicap-data-int for invoice-related endpoints. |
| Does Agicap support webhooks or event notifications? | Would enable event-driven integration (e.g., notify when a payment is executed or an invoice is approved). | Searched for "Agicap webhook", "Agicap callback", "Agicap notification". No results. | Ask Agicap support directly whether webhook/event mechanisms exist or are planned. |
| What fields are included in bank journal export entries? | Determines whether exported data contains enough detail for Orcha's needs (account numbers, amounts, dates, references, tax codes). | The Bank Journal API guide documents the endpoints but not the response schema/fields. | Perform a test export with API credentials and inspect the response JSON. |
Agicap does not appear to offer a sandbox environment. Testing requires a live Agicap account with admin access.
Obtain API credentials: Log into Agicap admin → Organization settings → Advanced settings → API settings → Generate new credentials.
Authenticate: POST to https://api.agicap.com/public/auth/v1/token with client_credentials grant. Verify token is returned.
List entities: GET https://api.agicap.com/public/organizations/v1/{orgId}/entities — confirm entity IDs are returned.
Explore developer portal: With authentication, browse api.agicap.com/apis to discover the full API surface. Download the OpenAPI spec if available.
Test bank journal export:
/{entityId}/exports — list existing exports/{entityId}/exports/{newUUID} — trigger a new export/{entityId}/exports/{exportId} — inspect the full response schemaInvestigate Postman collection: Access postman.com/agicap-data-int/agicap-public with a Postman account to browse all available endpoints.
Test invoice import: If an invoice endpoint is found in the developer portal, test submitting a structured invoice payload and verify it appears in Agicap's AP module.