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 Purchase API

The Purchase API from ECI Solutions — 7 operation(s) for purchase.

ECI Solutions Purchase 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 Purchase. 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 7 operations across 7 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version v2.

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

7 operations 7 paths 19 schemas 2 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://api-erp.integrations.ecimanufacturing.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

ECI Solutions Purchase 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 — Use the Authentication API OAuth endpoints

Paths & Operations 7

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

Purchase 7
POST
/api/v2/bills
Create (or update) a bill
postApiV2Bills 1 param body → 200202400409429500501
POST
/api/v2/bills/{billId}/attachments
Upload a single file and attach to a bill
postApiV2BillsByBillIdAttachments 1 param body → 200202400404429500501
POST
/api/v2/paymentblockstatus
Update the payment block status of a bill
postApiV2Paymentblockstatus body → 200202400404429500501
POST
/api/v2/purchase-journal-entries
Create (or update) a purchase journal entry
postApiV2PurchaseJournalEntries 1 param body → 200202400409429500501
GET
/api/v2/purchase-outstanding-items
Get a list of outstanding items for purchases
getApiV2PurchaseOutstandingItems 2 params → 200202429500501
GET
/api/v2/purchase-paymentinfo/{docNumber}
Get payment information for a purchase invoice
getApiV2PurchasePaymentinfoByDocNumber 1 param → 200202400404429500501
POST
/api/v2/suppliers
Create a new supplier
postApiV2Suppliers 1 param body → 200202400409429500501

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are Supplier (25 properties), PurchaseOutstandingItem (16 properties), PurchaseJournalEntry (15 properties), Bill (15 properties). Each schema is shown below with its type and property counts.

JournalEntryLine
object
Represents an individual line of a GL Journal to be saved to or existing in the financial system.
10 properties
AsyncAcceptedResponse
object
Represents the response returned when an asynchronous request is accepted for processing.
1 property
PaymentInfo
object
Information about payment of an invoice
2 properties
Attachment
object
A attachment info object.
6 properties
BankAccount
object
Represents a bank account of a supplier or customer.
9 properties
PurchaseJournalEntry
object
Represents a GL Journal to be saved to or existing in the financial system. - Id: Unique id of the journal. Provide when updating the record. ECI Financials: n…
15 properties
Supplier
object
Model for supplier data, also known as vendor or creditor. Code: + ECI Financials: Company.OldCreditorCode + Xero: Contact.AccountNumber + PowerOfficeGo: n/a +…
25 properties 1 required
BillLine
object
Represents a supplier Bill line to be saved to the financial system.
8 properties
Problem
object
Definition of [RFC7807](https://tools.ietf.org/html/rfc7807) problem detail
5 properties 2 required
Bill
object
Represents a supplier Bill to be saved to the financial system.
15 properties
ListContext
object
1 property 1 required
PurchaseOutstandingItem
object
Outstanding expenses for vendors. These are the bills that still have to be paid by you. In the V1 API, this is called VendorCreditModel.
16 properties
Address
object
Represents an address
10 properties
Contact
object
Represents the contact details of a supplier or customer
14 properties
Links
object
3 properties
PaymentBlockStatus
object
The payable state. At least docNumber or billId should be filled, to be able to lookup the bill.
4 properties
Entity
object
2 properties
PurchaseOutstandingItemList
object
2 properties 2 required
PaymentCondition
object
Model for payment conditions code + ECI Financials: Customer.PaymentTerms / Supplier.PaymentTerms + Xero: n/a + TripleTex: n/a + AccountView: Customer.PaymentT…
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eci-solutions-purchase-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 Purchase 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.