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

Basware AccountingDocuments API

The AccountingDocuments API from Basware — 9 operation(s) for accountingdocuments.

Basware AccountingDocuments API is one of 41 APIs that Basware publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include AccountingDocuments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a getting-started guide.

This API exposes 10 operations across 9 paths, and defines 17 schemas. It is described by OpenAPI 3.0.2, at version 1.0.0.

Requests are made against the base URL https://api.basware.com.

10 operations 9 paths 17 schemas 1 DELETE4 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.2
API Version
1.0.0
Base URL
https://api.basware.com
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Basware AccountingDocuments API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (HTTPBasic).

Paths & Operations 10

Across 9 paths, the API surfaces 10 operations — 1 DELETE, 4 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

AccountingDocuments 10
GET
/v1/accountingDocuments
Returns invoices approved for transfer to accounting.
6 params → 200302401404500
DELETE
/v1/accountingDocuments
Deletes data from Basware API. For manual one-time operations.
body → 200202400401500
GET
/v1/accountingDocuments/{invoiceId}
Returns single approved invoice by invoiceId -identifier.
1 param → 200302401404500
POST
/v1/accountingDocuments/{invoiceId}/acknowledge
Acknowledged invoices are no longer offered for next GET operation. Done right after GET, before transferResponse.
2 params → 200400401404405500
POST
/v1/accountingDocuments/{invoiceId}/enrichmentResponses
Marks invoice transfer P2P as accepted / rejected by receiving system. Used with invoices having 'p2pProcessingMode' = 'InvoiceEnrichment' which are not approved for payment.
2 params body → 200400401404500
POST
/v1/accountingDocuments/{invoiceId}/prebookResponses
Marks invoice prebooking as accepted / rejected by receiving system.
2 params body → 200401404409500400
POST
/v1/accountingDocuments/{invoiceId}/transferResponses
Marks invoice transfer as accepted / rejected by receiving system. Used with invoices having 'p2pProcessingMode' = 'Standard' which are approved for payment.
2 params body → 200400401404500
POST
/v1/accountingDocuments/{invoiceId}/paymentResponses
Updates invoice payment information, including payment date.
2 params body → 200401404409500400
GET
/v1/accountingDocuments/status
Returns high level invoice status by search criteria such as company code, invoice number and invoice date.
5 params → 200401404500
GET
/v1/accountingDocuments/{invoiceId}/attachments/{attachmentExternalCode}
Returns invoice attachment(s) by attachmentExternalCode identifier.
2 params → 200302401404500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are AccountingDocumentEntity (190 properties), StandardCodingEntity (149 properties), InvoiceLine (50 properties), PaymentResponseEntity (15 properties). Each schema is shown below with its type and property counts.

TransferResponseEntity
object
8 properties 4 required
TransferParameterEntity
object
2 properties 2 required
AccountingDocumentResponse
object
1 property 1 required
DeleteRequest
object
2 properties
DeleteResponse
object
3 properties
AccountingDocumentEntity
object
190 properties 6 required
PrebookResponseEntity
object
8 properties 4 required
DisputeInfo
object
3 properties
EnrichmentResponseEntity
object
enrichment response entity
5 properties 3 required
InvoiceLine
object
50 properties
Attachment
object
5 properties
StandardCodingEntity
object
149 properties 1 required
ErrorEntity
object
5 properties
PaymentResponseEntity
object
15 properties 3 required
ResponseEntityList
object
Errors returned here are returned synchronously from Basware API middle layer. Additional errors coming from target system(s) may be returned through errorFeed…
3 properties
AccountingDocumentsStatusResponseEntity
object
5 properties
RemoveResponseEntity
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

basware-accountingdocuments-api-openapi.yml Raw ↑

Other APIs Basware publishes across the network.

Basware Data Access API
Basware SmartPDF API
Basware Accounts API
Basware AdvancedPermissions API
Basware AdvancedValidations API
Basware ApplicationGroups API
Basware Companies (deprecated) API
Basware Contracts API
Basware CostCenters API
Basware Data extract API
Basware Directory France lookup API
Basware Document Import API API
Where this information came from

This is an independent, third-party profile of Basware AccountingDocuments 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.