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

Invendor Journals API

The Journals API from Invendor — 10 operation(s) for journals.

Invendor Journals API is one of 42 APIs that Invendor publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Journals. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 13 operations across 10 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.invendor.com.

13 operations 10 paths 20 schemas 1 DELETE4 GET7 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.invendor.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Invendor Journals API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

Paths & Operations 13

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

Journals 13
GET
/v1/Journals
GetJournals 10 params → 200400401403
GET
/v1/Journals/{journalId}
Returns journal details by journalId
GetJournalById 2 params → 200400401403
PUT
/v1/Journals/{journalId}
Updates journal details. Description is always updated. Date, OperationId and LocationId are updated only if journal has no lines.
UpdateJournalDetails 2 params body → 200400401403
POST
/v1/Journals/{journalId}
Adds new line to journal (Not allowed for counting journal)
AddJournalLine 2 params body → 200400401403
DELETE
/v1/Journals/{journalId}
Delete journal by journalId
DeleteJournal 2 params → 204400401403
GET
/v1/Journals/{journalId}/lines
Returns journal lines by journalId
GetJournalLines 7 params → 200400401403
POST
/v1/Journals/{journalId}/lines/recreate
Re-creates counting journal lines
ReCreateCountingLines 2 params body → 200400401403
POST
/v1/Journals/counting
Create counting journal
CreateCountingJournal 1 param body → 201400401403
POST
/v1/Journals/correction
Create correction journal
CreateCorrectionJournal 1 param body → 201400401403
POST
/v1/Journals/{journalId}/post
Post journal journal
PostJournal 2 params body → 204400401403
POST
/v1/Journals/confirmation
Creates new confirmation journal
CreateConfirmationJournal 1 param body → 204201400401403
POST
/v1/Journals/confirmation/{journalId}/lines
Save all journal lines
SaveConfirmationJournalLines 2 params body → 200400401403
GET
/v1/Journals/{journalId}/lines/xlsx
Create xlsx file including journal lines
Export journal lines 2 params → 200204400401403

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are CreateConfirmationJournalRequest (13 properties), JournalLineResponse (12 properties), JournalResponse (12 properties), CreateCorrectionJournalRequest (11 properties). Each schema is shown below with its type and property counts.

UpdateJournalDetailsRequest
object
5 properties
PostJournalRequest
object
1 property
CreateCountingJournalRequest
object
8 properties
InventDimResponse
object
5 properties
CreateCorrectionJournalRequest
object
11 properties
JournalLineResponse
object
12 properties
JournalResponsePagedResult
object
5 properties
JournalLineResponsePagedResult
object
5 properties
CreateConfirmationJournalRequestLine
object
8 properties
JournalType
integer
Error
object
2 properties
CreateConfirmationJournalRequest
object
13 properties
Int32ResourceCreatedResponse
object
1 property
CreateCorrectionJournalRequestLine
object
8 properties
CreateJournalLineRequest
object
6 properties
ApiErrorResponse
object
1 property
ConfirmationJournalLine
object
10 properties
JournalProcessType
integer
ReCreateJournalLinesRequest
object
3 properties
JournalResponse
object
12 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

invendor-journals-api-openapi.yml Raw ↑

Other APIs Invendor publishes across the network.

Invendor Accounts API
Invendor Auth API
Invendor Barcodes API
Invendor Consumption API
Invendor DataJobs API
Invendor Devices API
Invendor Dimensions API
Invendor DimensionValues API
Invendor Doors API
Invendor DynamicScanContent API
Invendor ExtendedProperties API
Invendor FlagTypes API
Where this information came from

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