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

ECI AP/AR Commerce Automation API

Accounts payable and accounts receivable invoice payment through Nuvei's Commerce Portal: customers, vendors, customer payments and vendor payments, with top/skip paging.

ECI AP/AR Commerce Automation API is one of 15 APIs that ECI Solutions publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments, Accounts Payable, and Accounts Receivable. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 31 operations across 18 paths, organized into 4 resource areas, and defines 32 schemas. It is described by OpenAPI 3.0.1, at version v1.

Requests are made against the base URL https://api-commerce.integrations.ecimanufacturing.com.

31 operations 18 paths 32 schemas 6 DELETE12 GET5 PATCH8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
v1
Base URL
https://api-commerce.integrations.ecimanufacturing.com
Authentication
OAuth 2.0
Resource Areas
4

Authentication & Security 1

ECI AP/AR Commerce Automation API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (Bearer) using the clientCredentials flow, exposing 1 scope. By default, every request must be authenticated.

  • Bearer — OAuth 2.0 Client Credentials Flow with API Users issued from Integration Engine Management Console

Paths & Operations 31

Across 18 paths, the API surfaces 31 operations — 6 DELETE, 12 GET, 5 PATCH, 8 POST. They span 4 resource areas: Customer, CustomerPayment, Vendor, VendorPayment. Each is listed below with its method, path, parameters, and response codes.

Customer 15
GET
/api/v1/customers
Get a list of customers.
GetCustomers 3 params → 200
POST
/api/v1/customers
Create a customer.
CreateCustomer body → 200
GET
/api/v1/customers/{id}
Get a Customer record by customer id.
GetCustomerById 1 param → 200
PATCH
/api/v1/customers/{id}
Update a customer.
UpdateCustomer 1 param body → 200
DELETE
/api/v1/customers/{id}
Delete a customer by customer id.
DeleteCustomer 1 param → 204
POST
/api/v1/customers/{id}/invoices
Create a customer invoice.
CreateCustomerInvoice 1 param body → 201
GET
/api/v1/customers/{id}/invoices/{invoiceId}
Get a Customer Invoice record.
GetCustomerInvoiceById 2 params → 200
PATCH
/api/v1/customers/{id}/invoices/{invoiceId}
Update a customer invoice.
UpdateCustomerInvoice 2 params body → 200
DELETE
/api/v1/customers/{id}/invoices/{invoiceId}
Delete a customer invoice by invoice id.
DeleteCustomerInvoice 2 params → 204
POST
/api/v1/customers/{id}/invoices/{invoiceId}/upload-file
Upload an invoice file.
UploadFileToCustomerInvoice 2 params body → 200
POST
/api/v1/customers/{id}/sales-orders
Create a customer sales order.
CreateCustomerSalesOrder 1 param body → 201
GET
/api/v1/customers/{id}/sales-orders/{salesOrderId}
Get a Customer Sales Order record.
GetCustomerSalesOrderById 2 params → 200
PATCH
/api/v1/customers/{id}/sales-orders/{salesOrderId}
Update a customer sales order.
UpdateCustomerSalesOrder 2 params body → 200
DELETE
/api/v1/customers/{id}/sales-orders/{salesOrderId}
Delete a customer sales order by sales order id.
DeleteCustomerSalesOrder 2 params → 204
POST
/api/v1/customers/{id}/sales-orders/{salesOrderId}/upload-file
Upload a sales order file.
UploadFileToSalesOrders 2 params body → 200
CustomerPayment 2
GET
/api/v1/customer-payments
Get a list of customer payments.
GetCustomerPayments 5 params → 200
GET
/api/v1/customer-payments/{id}
Get a customer's payment record by payment id.
GetCustomerPaymentById 1 param → 200404
Vendor 10
GET
/api/v1/vendors
Get a list of vendors.
GetVendors 4 params → 200
POST
/api/v1/vendors
Create a vendor.
CreateVendor body → 200
GET
/api/v1/vendors/{id}
Get a vendor record by vendor id.
GetVendorById 1 param → 200
PATCH
/api/v1/vendors/{id}
Update a vendor.
UpdateVendor 1 param body → 200
DELETE
/api/v1/vendors/{id}
Delete a vendor by vendor id.
DeleteVendor 1 param → 204
POST
/api/v1/vendors/{id}/invoices
Create a vendor invoice.
CreateVendorInvoice 1 param body → 200
GET
/api/v1/vendors/{id}/invoices/{invoiceId}
Get a Vendor Invoice record.
GetVendorInvoiceById 2 params → 200
PATCH
/api/v1/vendors/{id}/invoices/{invoiceId}
Update a vendor invoice.
UpdateVendorInvoice 2 params body → 200
DELETE
/api/v1/vendors/{id}/invoices/{invoiceId}
Delete a vendor invoice by invoice id.
DeleteVendorInvoice 2 params → 204
POST
/api/v1/vendors/{id}/payments
Create vendor payments.
CreatePayment 1 param body → 200
VendorPayment 4
GET
/api/v1/vendor-payment-methods
Get a list of payment methods and their lead times.
GetPaymentMethods → 200
GET
/api/v1/vendor-payments
Get a list of payments.
GetPayments 5 params → 200
GET
/api/v1/vendor-payments/{id}
Get a vendor's payment record by payment id.
GetPaymentById 1 param → 200404
DELETE
/api/v1/vendor-payments/{id}
Delete a vendor payment by payment id.
DeleteVendorPayment 1 param → 204

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are CustomerSalesOrderResponse (14 properties), CustomerInvoiceResponse (14 properties), VendorInvoiceResponse (12 properties), VendorPaymentResponse (12 properties). Each schema is shown below with its type and property counts.

Address
object
6 properties
CreateCustomerInvoiceRequestModel
object
9 properties 5 required
CreateCustomerSalesOrderRequestModel
object
9 properties 4 required
CreateVendorInvoiceRequestModel
object
9 properties 4 required
CreateVendorPaymentModel
object
6 properties 3 required
CustomerInvoiceResponse
object
14 properties
CustomerPaymentInvoice
object
3 properties
CustomerPaymentPreAuthDetails
object
4 properties
CustomerPaymentResponse
object
11 properties
CustomerPaymentResponseListResponse
object
2 properties
CustomerPaymentSalesOrder
object
3 properties
CustomerRequestModel
object
8 properties 3 required
CustomerResponse
object
9 properties
CustomerResponseListResponse
object
2 properties
CustomerSalesOrderResponse
object
14 properties
InvoiceRequestModel
object
2 properties 2 required
ProblemDetails
object
5 properties
RestrictPayment
string
UpdateCustomerInvoiceRequestModel
object
9 properties
UpdateCustomerRequestModel
object
8 properties
UpdateCustomerSalesOrderRequestModel
object
9 properties
UpdateVendorInvoiceRequestModel
object
9 properties
UpdateVendorRequestModel
object
7 properties
VendorInvoiceResponse
object
12 properties
VendorPaymentInvoice
object
2 properties
VendorPaymentMethodResponse
object
2 properties
VendorPaymentMethodResponseListResponse
object
2 properties
VendorPaymentResponse
object
12 properties 1 required
VendorPaymentResponseListResponse
object
2 properties
VendorRequestModel
object
8 properties 3 required
VendorResponse
object
9 properties
VendorResponseListResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eci-solutions-apar-commerce-openapi.json Raw ↑

Other APIs ECI Solutions publishes across the network.

ECI Manufacturing ERP API
JobBOSS² Public API
M1 Public API
ECI MFG Integration Management API
ECI Authentication API
ECI MFG Payment API
ECI Financial Integration API
ECI EvolutionX Ecommerce API
ECI Einvoice API
ECI Shipping API
ECI Currency Data API
ECI Office Integration API
Where this information came from

This is an independent, third-party profile of ECI AP/AR Commerce Automation 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.