How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Agicap Card expenses bank journal API

The Card expenses bank journal API from Agicap — 1 operation(s) for card expenses bank journal.

Agicap Card expenses bank journal API is one of 52 APIs that Agicap publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Card expenses bank journal. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 1 operation across 1 path, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 2 base URLs: https://api.agicap.com, https://api.agicap.internal.

1 operations 1 paths 7 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.agicap.com
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Agicap Card expenses bank journal API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). It accepts HTTP bearer tokens (OPAQUE) (bearerAuth).

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.

Card expenses bank journal 1
GET
/public/card-expenses-bank-journal/v1/entities/{entityId}/accounting-transactions
Retrieve your card expense bank journal entries
GetAccountingTransactionLines 4 params → 200401403429500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are AccountingTransactionLine (6 properties), ProblemDetails (5 properties), AccountingTransactionDebit (5 properties), AccountingTransactionCredit (5 properties). Each schema is shown below with its type and property counts.

PagedResult_1_PreAccounting.Queries.BankJournal.AccountingTransactionLine
object
2 properties 2 required
Pagination
object
5 properties 5 required
AccountingTransactionCredit
object
5 properties 5 required
AccountingTransactionLine
object
6 properties 6 required
AccountingTransactionAccountType
string
AccountingTransactionDebit
object
5 properties 5 required
ProblemDetails
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

agicap-card-expenses-bank-journal-api-openapi.yml Raw ↑

Other APIs Agicap publishes across the network.

Agicap Account reports API
Agicap Accrued interests API
Agicap Analytical Plan API
Agicap Anything API
Agicap Authentication API
Agicap Bank accounts API
Agicap Bank files API
Agicap Beta API
Agicap Causales API
Agicap Client addresses API
Agicap Client Credit Notes API
Agicap Client Invoices API
Where this information came from

This is an independent, third-party profile of Agicap Card expenses bank journal API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.