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 Solutions Customer API

The Customer API from ECI Solutions — 13 operation(s) for customer.

ECI Solutions Customer API is one of 194 APIs that ECI Solutions publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customers. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a support channel, authentication docs, and a changelog.

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

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

25 operations 13 paths 35 schemas 4 DELETE7 GET5 PATCH7 POST2 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-erp.integrations.ecimanufacturing.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

ECI Solutions Customer 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 25

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

Customer 25
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
GET
/api/v1/customers/{customerId}
Get a single customer by Id
GetCustomer 1 param → 200404
PATCH
/api/v1/customers/{customerId}
Update a single customer by Id
patchApiV1CustomersByCustomerId 1 param body → 200
GET
/api/v1/customers/{customerId}/addresses
Get a list of customer addresses
GetAddresses 5 params → 200
POST
/api/v1/customers/{customerId}/addresses
Create an address for a customer by Id
CreateAddress 1 param body → 200
PATCH
/api/v1/customers/{customerId}/addresses/{addressId}
Update an address for a customer
UpdateAddress 2 params body → 200
PUT
/api/v1/customers/{customerId}/contract-pricing
Create or update the customer contract pricing
AddUpdateCustomerContractPricing 1 param body → 404204
GET
/api/v1/customers/{customerId}/product-aliases
Get a list of customer product aliases by Id
GetCustomerProductAliasesByCustomerId 4 params → 200
POST
/api/v1/customers/{customerId}/product-aliases
Create a customer product alias by Id
CreateCustomerProductAlias 1 param body → 200409
PUT
/api/v1/customers/{customerId}/product-aliases
Update a customer product alias by Id
UpdateCustomerProductAlias 1 param body → 200404
DELETE
/api/v1/customers/{customerId}/product-aliases
Delete a single customer product aliases by customer Id
DeleteCustomerProductAliases 3 params → 204

Schemas 35

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

CustomerRequestModel
object
8 properties 3 required
Address
object
6 properties
UpdateCustomerInvoiceRequestModel
object
9 properties
CreateCustomerInvoiceRequestModel
object
9 properties 5 required
CustomerSalesOrderResponse
object
14 properties
CustomerResponseListResponse
object
2 properties
UpdateCustomerSalesOrderRequestModel
object
9 properties
CustomerResponse
object
9 properties
CustomerInvoiceResponse
object
14 properties
UpdateCustomerRequestModel
object
8 properties
RestrictPayment
string
CreateCustomerSalesOrderRequestModel
object
9 properties 4 required
SkuOldNewValue
object
2 properties 2 required
EcommerceUpdateAddressRequest
object
11 properties
EcommerceCustomerUpdateRequest
object
9 properties 1 required
EcommerceCustomerProductAliasesResponseProductAliasesListResponse
object
3 properties
EcommerceCustomerRewardsStatus
integer
EcommerceCustomerAddressResponse
object
12 properties
EcommerceCustomerContractPricingRequest
object
4 properties 4 required
ProblemDetails
object
5 properties
EcommerceCustomerResponseListResponse
object
3 properties
EcommerceCustomerAddress
object
5 properties
EcommerceCustomerProductAliasRequest
object
2 properties 2 required
AliasOldNewValue
object
2 properties 2 required
EcommerceAddressType
integer
EcommerceCustomerProductAliasResponse
object
3 properties
EcommerceCustomerProductAliasesResponse
object
2 properties
EcommerceCustomerWithAddressResponse
object
7 properties
EcommerceUpdateCustomerProductAliasRequest
object
2 properties 2 required
EcommerceCustomerAddressResponseListResponse
object
3 properties
EcommerceCustomerRequest
object
10 properties 1 required
EcommerceAddress
object
11 properties 1 required
ProductPricing
object
3 properties 3 required
EcommerceAddressResponse
object
5 properties
EcommerceCustomerResponse
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eci-solutions-customer-api-openapi.yml Raw ↑

Other APIs ECI Solutions publishes across the network.

ECI Solutions Account API
ECI Solutions Account Vault API
ECI Solutions Activation Code API
ECI Solutions Addresses API
ECI Solutions Analytics API
ECI Solutions AP Checks API
ECI Solutions Application API
ECI Solutions AR Invoice Details API
ECI Solutions AR Invoices API
ECI Solutions Attendance Ticket Details API
ECI Solutions Attendance Tickets API
ECI Solutions Authentication API
Where this information came from

This is an independent, third-party profile of ECI Solutions Customer 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.