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

Procuros Incoming Transactions API

The Incoming Transactions API from Procuros — 3 operation(s) for incoming transactions.

Procuros Incoming Transactions API is one of 4 APIs that Procuros publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 3 paths, and defines 86 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against 2 base URLs: https://api.procuros.io/, https://api.procuros-staging.io/.

3 operations 3 paths 86 schemas 1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.procuros.io/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Procuros Incoming Transactions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (api_token). By default, every request must be authenticated.

  • api_token — The API Token of your ERP Connection.

Paths & Operations 3

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

Incoming Transactions 3
GET
/v2/transactions
List Incoming Transactions
v2_list_received_transactions 3 params → 2004224XX5XX
PUT
/v2/transactions/{procurosTransactionId}
Mark Transaction Processed
v2_mark_transaction_processed 1 param body → 2004224XX5XX
POST
/v2/transactions/bulk/mark-processed
Bulk Mark Transactions Processed
v2_bulk_mark_transactions_processed body → 2004224XX5XX

Schemas 86

The contract defines 86 schemas that model the data the API accepts and returns. The most detailed are ProductCatalogItem (75 properties), OrderItem (41 properties), CreditNoteItem (41 properties), OrderResponseItem (40 properties). Each schema is shown below with its type and property counts.

InventoryReport
object
2 properties 2 required
ProductCatalogItem
object
75 properties 3 required
Order
object
A purchase order is a formal request from a buying organization to a supplier to fulfill a contract.
3 properties 2 required
OrderResponse
object
3 properties 1 required
PostalAddress
object
Depending on the transaction different properties are required. Only on an invoice a full address is required.
7 properties
InventoryReportItem
object
21 properties
Certifications
object
Item certifications for various standards and organizations.
2 properties
Invoice
object
Invoices describe purchase orders, line items, partners involved, accounting distribution, payment terms, discounts, shipping and special handling, taxes, depo…
3 properties 2 required
ProductCatalogItemPackagingUnit
object
10 properties 1 required
Party
object
5 properties 1 required
DispatchInstructionItem
object
29 properties 5 required
PaymentTerm
object
2 properties 2 required
DispatchInstructionResponseTransportUnits
object
9 properties 1 required
CertificationsRequired
object
Indicates which certifications are required for the ordered item.
3 properties
CreditNote
object
A credit note is a document sent to a customer in order to correct a mistake on an order or an invoice, or to refund an amount paid for products or services.
3 properties 3 required
SalesReport
object
2 properties 2 required
PartyIdentifier
object
2 properties 2 required
ReceivalNoticeItem
object
14 properties
Currency
string
ISO 4217 standard three-letter currency code.
ReceivalNoticeTransportUnits
object
5 properties 1 required
CreditNoteItemWithSubSubItems
Contact
object
7 properties
ItemIdentifier
object
2 properties
ShippingNoticeHeader
object
32 properties 5 required
RemittanceAdviceItemCorrection
object
5 properties 2 required
UnitOfMeasure
string
Subset of the the UN/CEFACT Unit of Measure Common Codes.
Modification
object
One of percentage and amount is required.
7 properties
GeneralValidationErrorResponse
object
2 properties 2 required
ProductCatalogIdentity
object
Product identity containing sender partner ID, receiver partner ID, and GTIN.
3 properties
LineItemAttachment
object
Document attachment for a line item, such as technical datasheets, product labels, or compliance documents.
4 properties
ShippingNoticeTransportUnitWithSubTransportUnits
SalesReportHeader
object
10 properties 6 required
DispatchInstructionResponseHeader
object
26 properties 2 required
ShippingNoticeTransportUnit
object
If a TransportUnit does not contain sub items (like packages on a pallet), it must contain a nonempty list of items.
9 properties 1 required
InvoiceItem
object
40 properties 7 required
Batch
object
5 properties
IncoTerms
string
International Commercial Terms (INCOTERMS) as published by the International Chamber of Commerce (ICC).
InvoiceItemWithSubSubItems
DispatchInstruction
object
2 properties 2 required
CreditNoteHeader
object
32 properties 4 required
SalesReportLocationItem
object
28 properties 3 required
ShippingNoticeItem
object
40 properties 5 required
ErrorType
string
The type of the error. DATA indicates that the error is caused by invalid or insufficient data and can be resolved by a user. INTERNAL indicates a system-level…
ShippingNotice
object
2 properties 2 required
ProductCatalogItemWithSubItems
Date
string
DispatchInstructionResponse
object
2 properties 2 required
ReceivedTransaction
object
6 properties 4 required
DispatchInstructionHeader
object
22 properties 2 required
ShippingNoticeItemWithSubSubItems
OrderResponseItem
object
40 properties
SalesReportLocation
object
4 properties 2 required
TransactionContent
InvoiceItemWithSubItems
ModeOfTransport
string
Chosen mode of transport for the shipment.
ShippingNoticeItemWithSubItems
InvoiceHeader
object
29 properties 8 required
CreditNoteItem
object
41 properties 7 required
AdditionalOrderIdentifiers
object
Additional order identifiers for different parties in the transaction.
7 properties
ShipToParty
object
A party object where identifiers are optional, used specifically for shipTo fields.
5 properties
RemittanceAdvice
object
3 properties 3 required
ModificationGroup
object
3 properties 3 required
ReceivalNotice
object
2 properties 2 required
TransportUnitCarrier
object
Carrier information for a transport unit.
3 properties
DispatchInstructionResponseItem
object
26 properties
ProductCatalogHeader
object
10 properties 3 required
TransactionType
string
Type of transaction.
RemittanceAdviceItem
object
11 properties
DateTime
string
RemittanceAdviceSummary
object
3 properties
RemittanceAdviceHeader
object
13 properties 2 required
ShippingNoticePartyIdentifier
object
2 properties 2 required
CreditNoteItemWithSubItems
ProcurosTransactionId
string
Unique ID assigned to every transaction on the Procuros Network.
Tax
object
3 properties 2 required
ProductCatalog
object
2 properties 2 required
OrderHeader
object
24 properties 4 required
Attachment
object
3 properties
ProductCatalogItemWithSubSubItems
LineItemAttachmentType
string
Type/classification of the line item attachment document.
OrderItem
object
41 properties
OrderResponseHeader
object
27 properties 5 required
InventoryReportHeader
object
8 properties 4 required
ReceivalNoticeHeader
object
19 properties 4 required
InternalErrorResponse
object
1 property 1 required
ValidationError
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

procuros-incoming-transactions-api-openapi.yml Raw ↑

Other APIs Procuros publishes across the network.

Procuros All Transactions API
Procuros Misc API
Procuros Outgoing Transactions API
Where this information came from

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