Agicap Integration Research

Date: 2026-04-01 Status: Research complete — connection provisioning remains the primary blocker

Table of Contents

• Summary
• Capability Matrix
• 1. System Overview
• 2. Integration Intermediaries & Middleware
• 3. Authentication & Connectivity
• 4. Invoice/Document Submission
• 5. Master Data Access
• 6. Historical Bookings / Journal Entries
• 7. Status & Feedback
• Unresolved Questions
• Suggested Hands-On Testing Plan
• Dead Ends
• Sources
• Retractions

Summary

Agicap is a cloud-only cash flow management and treasury SaaS serving 8,000+ SMB/mid-market clients across 12+ European countries. It sits alongside ERPs and accounting systems — not replacing them — handling cash flow forecasting, accounts receivable tracking, and accounts payable automation including pre-accounting. Its three modules are Agicap Cashflow, Agicap CashCollect, and Agicap Payment.

Agicap's Business Documents API v2 supports write operations for supplier invoices, client invoices, purchase orders, and credit notes. These endpoints are not publicly documented but were confirmed through hands-on API testing in February 2026, corroborated by Celigo's native connector which lists Import (write) support. The v2 DTO schema was reverse-engineered via validation error responses. All write endpoints require a connectionId — a provisioned integration source — which cannot currently be created via the API and must be set up through Agicap's onboarding or partner program. This is the primary blocker.

For reading data, the Treasury Bank Journal API (public, documented) provides cursor-based access to bank journal entries. Master data (chart of accounts, suppliers, cost centers) has no public API access. Categories and bank accounts are accessible only through the undocumented internal API (app.agicap.com/api/). Agicap has no webhook or event push system — all data access is pull-based. Celigo is the only iPaaS with a native Agicap connector; Maesn, Make, Zapier, Workato, and n8n have none.

Capability Matrix

1. System Overview

Agicap is a cash flow management and treasury SaaS platform, founded in Lyon (2016), serving 8,000+ clients across 12+ European countries with offices in Lyon (HQ), Paris, Berlin, Barcelona, Milan, London, and the Netherlands.

"Agicap is an AI-powered platform connecting your banking and accounting flows to unlock trapped liquidity." — agicap.com/en-us/

"The comprehensive solution consists of three key modules: Agicap Cashflow for efficient cash flow management, forecasting, and analysis; Agicap CashCollect for proactive customer receivables tracking and collection; and Agicap Payment for streamlined supplier invoice payments and centralization." — GetApp

Deployment & Architecture

Cloud-only SaaS. No on-premise option.

"Agicap is deployed as Cloud, SaaS, Web-Based software." — Software Advice

Market Position

"Since its Series B funding in 2021, Agicap has [...] solidified its leadership position in Europe by expanding into 4 regions (DACH, Italy, UK & Ireland, Spain). Other countries already account for over 50% of total revenue." — Agicap Series C announcement

Role in Accounting Workflow

Agicap is not a system of record for invoices or accounting. It sits alongside ERPs and accounting systems, pulling data in and pushing pre-accounting data back.

"Agicap is able to retrieve data from and push data into your ERP and accounting tools' systems for accurate real-time monitoring." — Agicap - Banking & ERP Connectivity

ERP / Accounting System (system of record)
    │
    │ pull: open invoices, journal entries, balances
    ▼
  AGICAP (cash flow layer)
    │
    │ push: pre-accounting entries, payment data
    ▼
ERP / Accounting System

Agicap uses Chift (unified accounting API) to maintain its integrations with European accounting systems:

"Since Agicap now also manages payments, their team identified the need to not only pull data from accounting software but also send over pre-accounting data reflecting payments and transfers." — Chift - Agicap case study

Pre-Accounting / AP Module ("Agicap Payment")

"Agicap's invoice processing includes pre-accounting convenience, allowing you to automatically generate entries in your purchase journal, group invoices by cost centre, and export all purchase entries to your other accounting systems or ERP system." — Agicap - Invoice Management

This module captures invoices (email forwarding, mobile scan, PDF upload), extracts data via OCR, runs validation/approval workflows, generates pre-accounting entries, and executes payments.

Multi-Entity Support

"Switch in one click from a consolidated group view to a detailed view of each entity." — Agicap - Consolidation

Multi-currency support with daily exchange rate conversion. The API uses per-entity entityId and connectionId in URL paths.

Confidence: HIGH — consistent across official sources, press, and review platforms.

2. Integration Intermediaries & Middleware

Celigo — Only iPaaS with Native Connector

Celigo released a native Agicap connector in November 2024 supporting both Export (read from Agicap) and Import (write to Agicap) flows. It uses the same OAuth 2.0 Client Credentials auth as the public API.

The definitive list of supported operations is at docs.celigo.com but is behind Cloudflare (HTTP 403) and could not be scraped.

Confidence: HIGH — connector existence confirmed; operation details blocked by Cloudflare.

Maesn — No Connector

Maesn supports 27 accounting/ERP systems (DATEV, sevdesk, QuickBooks, Sage, Xero, etc.). Agicap is not among them. Maesn targets bookkeeping/accounting backends, not treasury/cash-flow tools. No mention of Agicap on their roadmap.

Confidence: HIGH (95%) — Maesn Integrations

Chift — Dead End

Agicap is a customer of Chift, not a connector in Chift's catalog. Chift bridges Agicap to accounting tools (Sage, Pennylane, Cegid), not the reverse. There is no "Agicap connector" in Chift's 129-connector directory.

Confidence: HIGH (95%) — Chift Connectors

Other Platforms — None

Confidence: HIGH (90-95%) across all platforms.

3. Authentication & Connectivity

Public API — OAuth 2.0 Client Credentials

Tested and confirmed working. Standard client_id + client_secret exchange for a bearer token.

Confidence: Confirmed — tested hands-on.

Legacy API — Bearer API Token

"This api is deprecated [...] Please note that this API is deprecated and will be removed in early 2025." — Legacy OpenAPI swagger.json

Despite the deprecation notice, the swagger spec is still live as of April 2026. The legacy API has write endpoints not available on the public API (notably POST /api/connections which only requires a name field).

Confidence: HIGH that it's accessible. MEDIUM that endpoints still function.

Internal App API — Username/Password

Used by community notebooks (naas) to access categories, bank accounts, and Excel exports. Fragile and unsupported.

Developer Portal & Sandbox

• Developer portal: api.agicap.com (JS SPA, content not scrapable)
• No public sandbox environment
• Credentials generated from production Agicap account
• Partner program: agicap.com/en/partners/become-partner/

Confidence: HIGH

4. Invoice/Document Submission

Business Documents API v2 (Primary Path)

Write endpoints confirmed through hands-on testing (HTTP 400 validation errors prove endpoint existence and parse requests). Both v1 and v2 exist; v2 is recommended for its richer schema.

Base URL: https://api.agicap.com/public/business-documents/v2/entities/{entityId}/connections/{connectionId}/

V2 DTO Schema (Reverse-Engineered)

Required fields (supplier/client invoices):

Optional fields (confirmed parsed by DTO):

Valid status values:

• Supplier invoices: none, draft, due, paid, cancelled, deleted, paymentExecuted
• Client invoices: none, draft, due, paid, cancelled, deleted

Fields confirmed NOT on the DTO (silently ignored): description, costCenter (top-level), category, account, tags, lineItems, notes, paymentTerms, reference, lines, items, allocations, payments, attachments, supplier, contact, bankAccount, paymentMethod

Request format: Array of DTOs:

[{
  "externalId": "orcha-001",
  "invoiceNumber": "INV-2024-001",
  "currency": "EUR",
  "amounts": {"totalAmount": 119.00, "taxesAmount": 19.00, "dueAmount": 119.00},
  "status": "draft",
  "issueDate": "2024-01-15",
  "dueDate": "2024-02-15",
  "counterParty": {"id": "supplier-001", "name": "Test Supplier GmbH"},
  "metadata": {"costCenter": "CC-001", "glAccount": "4200"}
}]

Connection Provisioning Blocker

All write endpoints require a valid connectionId (GUID) in the URL path. This represents a configured integration source in Agicap.

Current state: The test entity (211584) has zero connections. GET /connections returns []. POST attempts to non-existent connections return HTTP 500 (backend NullReferenceException).

The API's POST /entities/{entityId}/connections endpoint expects a CreateConnectionDto but returns HTTP 500 for all field combinations tested. Connection creation appears to require Agicap-side provisioning.

Possible resolution paths:

1. Contact Agicap via partner program to request connection provisioning
2. Use Celigo free tier to create a connection (Celigo's setup flow may auto-provision)
3. Try the legacy API POST /api/connections which only requires {"name": "..."} — the legacy API is still live despite its deprecation notice
4. Agicap UI: Forecast > cogwheel > "Banks and integrations" > "Connect a bank"

PDF Attachment

The attachments field was confirmed not on the DTO (silently ignored). No other mechanism for attaching PDF files to submitted invoices was found.

Confidence: HIGH (95%) for endpoint existence and schema. Connection blocker is confirmed.

5. Master Data Access

Master data access via the public API is severely limited. Most master data entities return 404.

Chart of Accounts / GL Accounts

Not available. No endpoint exists on any API surface. GL accounts are not a first-class entity in Agicap — it's a cash management tool, not an accounting system.

Can potentially attach GL account references to invoices via metadata: {"glAccount": "4200"}, but the exact key names Agicap recognizes are unconfirmed.

Confidence: HIGH (95%) — extensively tested, 404 on public API.

Business Partners / Suppliers / Customers

No read endpoint. /entities/{entityId}/contacts and /entities/{entityId}/suppliers both return 404.

Suppliers/customers are implicitly created when invoices reference them via counterParty.id and counterParty.name. No way to list existing suppliers.

Confidence: HIGH (95%)

Cost Centers

No read endpoint. /entities/{entityId}/cost-centers returns 404.

Potentially attachable via metadata on invoices. Cannot be listed or managed via API.

Confidence: HIGH (95%)

Categories

Available via internal API only:

• GET https://app.agicap.com/api/categories/v1/hierarchy/outflow — expense categories
• GET https://app.agicap.com/api/categories/v1/hierarchy/inflow — revenue categories

Requires internal auth (username/password + EntrepriseId header). Returns hierarchical JSON. Documented in naas notebooks.

Confidence: MEDIUM (70%) — working in community notebooks, but undocumented and fragile.

Bank Accounts

Available via internal API only:

• GET https://app.agicap.com/api/banque/GetAll — all bank accounts for a company

Same internal auth caveats.

Confidence: MEDIUM (70%)

Entity Discovery

Available via public API:

• GET /public/organizations/v1/{organization_id}/entities — lists entities with pagination

Documented in the Treasury Bank Journal PDF guide. Useful for multi-entity customers to programmatically discover entity IDs.

Confidence: HIGH (85%)

6. Historical Bookings / Journal Entries

Treasury Bank Journal API (Public, Documented)

The primary read path for historical transaction data.

• Endpoint: GET /public/treasury-bank-journal/v1/entities/{entityId}/exports
• Parameters: size (required, max 5000), after or before (cursor-based, DateTimeOffset)
• Response: {items: [...], cursor: {before, after, size}}
• Auth: OAuth 2.0 bearer token

Tested and confirmed working (returned empty results for test account with no bank connections).

Confidence: Confirmed

Card Expenses Bank Journal API

• Endpoint: GET /public/card-expenses-bank-journal/v1/entities/{entityId}/...
• Returns card expense journal entries
• Endpoint responds but no test data available

Confidence: HIGH (85%)

Internal API — Treasury Plan Exports

Available via the undocumented internal API:

• POST https://app.agicap.com/api/exportexcel/ExportExcelSimple — consolidated treasury plan by month
• POST https://app.agicap.com/api/exportexcel/ExportExcelBanque — treasury plan by bank account by month

Returns Excel binary data. Richer than the public API (includes categories, per-account breakdown). Requires internal auth.

Confidence: MEDIUM (70%) — documented in naas notebooks, undocumented by Agicap.

Legacy API — Companies

• GET https://openapi.agicap.com/api/companies — lists all companies linked to the account

Uses legacy bearer token auth. API is deprecated but still responding.

Confidence: MEDIUM — endpoint may stop working without notice.

7. Status & Feedback

Synchronous Response to Writes

Invoice POST requests return HTTP status codes synchronously:

• 200 — accepted (expected when connection exists)
• 400 — validation errors (returns detailed field-level messages)
• 500 — backend error (e.g., non-existent connection)

No evidence of async processing queues or delayed rejection.

Confidence: HIGH (90%) — based on testing patterns, but no successful write-through-to-UI has been verified yet.

No Webhooks

Agicap has no webhook or event push system. No webhook endpoints found in any API surface, no webhook configuration in the UI, no mention in documentation. The Celigo connector uses polling.

Confidence: HIGH (95%)

No Status Polling Endpoint

No endpoint was found to check the status of a previously submitted document beyond the initial synchronous response.

Implications

After submitting invoices, the only way to confirm they appeared in Agicap is:

1. Manual check in the Agicap UI
2. Poll the Treasury Bank Journal API for corresponding entries (indirect)
3. Use the internal API for Excel exports (fragile)

Confidence: HIGH

Unresolved Questions

Suggested Hands-On Testing Plan

Prerequisites

• Provisioned connectionId for entity 211584 (via Agicap, Celigo, or legacy API)

Test 1: Legacy API Connection Creation

# Try creating a connection via the deprecated-but-live legacy API
curl -X POST https://openapi.agicap.com/api/connections \
  -H "Authorization: Bearer {legacy_api_token}" \
  -H "Content-Type: application/json" \
  -d '{"name": "Orcha Integration"}'

Check if a connection appears in GET /public/business-documents/v1/entities/211584/connections.

Test 2: Invoice Submission (once connection exists)

curl -X POST "https://api.agicap.com/public/business-documents/v2/entities/211584/connections/{connectionId}/supplier-invoices" \
  -H "Authorization: Bearer {oauth_token}" \
  -H "Content-Type: application/json" \
  -d '[{
    "externalId": "orcha-test-001",
    "invoiceNumber": "TEST-INV-001",
    "currency": "EUR",
    "amounts": {"totalAmount": 119.00, "taxesAmount": 19.00, "dueAmount": 119.00},
    "status": "draft",
    "issueDate": "2026-04-01",
    "dueDate": "2026-05-01",
    "counterParty": {"id": "test-supplier-001", "name": "Test Supplier GmbH"}
  }]'

Verify invoice appears in Agicap UI.

Test 3: Metadata Fields

Repeat Test 2 with metadata:

"metadata": {"costCenter": "CC-001", "glAccount": "4200", "department": "Engineering"}

Check which keys persist and display in Agicap.

Test 4: Batch + Status Transitions

• POST array of 5 invoices in one request
• PUT to update status from draft → due → paid
• Verify each transition reflects in Agicap UI

Test 5: Entity Discovery

curl "https://api.agicap.com/public/organizations/v1/{org_id}/entities?pageNumber=1&pageSize=100" \
  -H "Authorization: Bearer {oauth_token}"

Confirm multi-entity enumeration works.

Dead Ends

Sources

Agicap Official

• Developer Portal
• Authentication Guide
• Business Documents Guide
• Business Documents v2
• Treasury Bank Journal Guide
• Treasury Bank Journal PDF
• Banking Documents v1
• Card Expenses Bank Journal v1
• Legacy API Docs
• Legacy Swagger Spec
• Integration Marketplace
• Banking & ERP Connectivity
• Invoice Management
• Consolidation / Multi-Entity
• Partner Program
• Series C Announcement
• General Terms & Conditions

Celigo

• Agicap Connection Setup
• Available Agicap APIs (behind Cloudflare, HTTP 403)
• November 2024 Release Notes
• Pricing

Chift

• Agicap Case Study
• Connectors Directory

Middleware (No Connector)

• Maesn Integrations — 27 systems, Agicap not listed
• Maesn Docs
• Make.com Integrations — no Agicap module
• Zapier Apps — no Agicap app
• Workato Integrations — no Agicap connector
• n8n Integrations — no Agicap node

Community & Third-Party

• Postman Collection (new)
• Postman Collection (legacy)
• naas Agicap Notebooks — categories, bank accounts, companies, treasury exports
• API Tracker — 0 APIs indexed

Review Platforms

• G2 Reviews
• GetApp
• Software Advice

Press

• TechCrunch - Series C
• EU-Startups - Series C

Retractions

No claims were retracted during the self-audit. All findings in this document are either:

• Confirmed via hands-on API testing (Feb 2026)
• Sourced from official Agicap pages, review platforms, or press with extracted quotes
• Explicitly marked with confidence levels when based on indirect evidence (e.g., metadata field for cost centers)

The February 2026 hands-on testing was performed against entity 211584. API behavior for other entities or accounts may differ.