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

Invoice Ninja Bank Transactions API

The Bank Transactions API from Invoice Ninja — 3 operation(s) for bank transactions.

Invoice Ninja Bank Transactions API is one of 10 APIs that Invoice Ninja publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Bank Transactions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 3 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 5.0.

Requests are made against a single base URL, https://invoicing.co.

6 operations 3 paths 1 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.0
Base URL
https://invoicing.co
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Invoice Ninja Bank Transactions API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Api-Token (apiToken). By default, every request must be authenticated.

  • apiToken — API token created in the Invoice Ninja settings. Self-hosted installs may additionally require an X-Api-Secret header.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Bank Transactions 6
GET
/api/v1/bank_transactions
List bank transactions
listBankTransactions → 200
POST
/api/v1/bank_transactions
Create bank transaction
createBankTransaction body → 201
GET
/api/v1/bank_transactions/{id}
Get bank transaction
getBankTransaction 1 param → 200
PUT
/api/v1/bank_transactions/{id}
Update bank transaction
updateBankTransaction 1 param body → 200
DELETE
/api/v1/bank_transactions/{id}
Delete bank transaction
deleteBankTransaction 1 param → 204
POST
/api/v1/bank_transactions/match
Match bank transactions to invoices/payments
matchBankTransactions body → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is BankTransaction (10 properties). Each schema is shown below with its type and property counts.

BankTransaction
object
10 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

invoice-ninja-bank-transactions-api-openapi.yml Raw ↑

Other APIs Invoice Ninja publishes across the network.

Invoice Ninja Activities API
Invoice Ninja Authentication API
Invoice Ninja Bank Integrations API
Invoice Ninja Bank Transaction Rules API
Invoice Ninja Charts API
Invoice Ninja Client Gateway Tokens API
Invoice Ninja Companies API
Invoice Ninja Company Gateways API
Invoice Ninja Settings API
Where this information came from

This is an independent, third-party profile of Invoice Ninja Bank Transactions 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.