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 Financial Integration API

Accounting-system integration for ECI ERP products. v1 integrates QuickBooks Online, MYOB, Xero and Sage; v2 integrates Xero and ECI Financials and covers purchase, sales and general ledger flows. v2 is the only ECI contract that declares 429 Too Many Requests and 501 Not Implemented responses with an RFC 7807-shaped Problem body.

ECI Financial Integration 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 Accounting, Financial, Integration, QuickBooks, and Xero. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 17 operations across 17 paths, organized into 4 resource areas, and defines 30 schemas. It is described by OpenAPI 3.0.1, at version v2.

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

17 operations 17 paths 30 schemas 6 GET11 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

ECI Financial Integration 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 17

Across 17 paths, the API surfaces 17 operations — 6 GET, 11 POST. They span 4 resource areas: Features, General, Purchase, Sales. Each is listed below with its method, path, parameters, and response codes.

Features 1
GET
/api/v2/features
Get the features of the Financial Package
→ 200202
General 2
POST
/api/v2/general-journal-entries
Create (or update) general journal entry.
1 param body → 200202400409429500501
GET
/api/v2/tax-codes
Get a list of tax codes.
→ 200202429500501
Purchase 7
POST
/api/v2/bills
Create (or update) a bill.
1 param body → 200202400409429500501
POST
/api/v2/bills/{billId}/attachments
Upload a single file and attach to a bill.
1 param body → 200202400404429500501
POST
/api/v2/paymentblockstatus
Update the payment block status of a bill.
body → 200202400404429500501
POST
/api/v2/purchase-journal-entries
Create (or update) a purchase journal entry.
1 param body → 200202400409429500501
GET
/api/v2/purchase-outstanding-items
Get a list of outstanding items for purchases.
2 params → 200202429500501
GET
/api/v2/purchase-paymentinfo/{docNumber}
Get payment information for a purchase invoice.
1 param → 200202400404429500501
POST
/api/v2/suppliers
Create a new supplier.
1 param body → 200202400409429500501
Sales 7
POST
/api/v2/customers
Create a new customer, or update an existing one.
1 param body → 200202400409429500501
POST
/api/v2/invoices
Create (or update) a sales invoice.
1 param body → 200202400409429500501
POST
/api/v2/invoices/{invoiceId}/attachments
Uploads the data of a single attachment and adds it to the invoice.
1 param body → 200202400404429500501
POST
/api/v2/orders
Create (or update) an order.
1 param body → 200202400429500501
POST
/api/v2/sales-journal-entries
Create (or update) sales journal entry.
1 param body → 200202400409429500501
GET
/api/v2/sales-outstanding-items
Get a list of outstanding items for sales.
2 params → 200202429500501
GET
/api/v2/sales-paymentinfo/{docNumber}
Get payment information for a sales invoice.
1 param → 200202400404429500501

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are Customer (25 properties), Supplier (25 properties), Invoice (17 properties), FinancialPackageFeatures (17 properties). Each schema is shown below with its type and property counts.

Address
object
Represents an address
10 properties
AsyncAcceptedResponse
object
Represents the response returned when an asynchronous request is accepted for processing.
1 property
Attachment
object
A attachment info object.
6 properties
BankAccount
object
Represents a bank account of a supplier or customer.
9 properties
Bill
object
Represents a supplier Bill to be saved to the financial system.
15 properties
BillLine
object
Represents a supplier Bill line to be saved to the financial system.
8 properties
Contact
object
Represents the contact details of a supplier or customer
14 properties
Customer
object
Model for customer data, also known as debtor. Code: + ECI Financials: Company.OldDebtorCode + Xero: Accountnumber + PowerOfficeGo: n/a + TripleTex: Customer.C…
25 properties 1 required
Entity
object
2 properties
FinancialPackageFeatures
object
17 properties
GeneralJournalEntry
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: J…
10 properties
Invoice
object
This class is used for sales invoices. Id Unique id of the invoice. Xero: Invoice.InvoiceId / CreditNote.CreditNoteId TripleTex: Invoice.Id PowerOfficeGo: Invo…
17 properties
InvoiceLine
object
Line item details for customer invoices and credits.
8 properties
JournalEntryLine
object
Represents an individual line of a GL Journal to be saved to or existing in the financial system.
10 properties
Links
object
3 properties
ListContext
object
1 property 1 required
Order
object
An order object, sometimes also used for projects.
11 properties
PaymentBlockStatus
object
The payable state. At least docNumber or billId should be filled, to be able to lookup the bill.
4 properties
PaymentCondition
object
Model for payment conditions code + ECI Financials: Customer.PaymentTerms / Supplier.PaymentTerms + Xero: n/a + TripleTex: n/a + AccountView: Customer.PaymentT…
3 properties
PaymentInfo
object
Information about payment of an invoice
2 properties
Problem
object
Definition of [RFC7807](https://tools.ietf.org/html/rfc7807) problem detail
5 properties 2 required
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
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
PurchaseOutstandingItemList
object
2 properties 2 required
SalesJournalEntry
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
SalesOutstandingItem
object
Outstanding liabilities for customers. These are the invoices that still have to be paid by customers. In the V1 API, this is called CreditMemoModel.
15 properties
SalesOutstandingItemList
object
2 properties 2 required
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
TaxCode
object
Model for Tax data, also known as VAT.
4 properties 1 required
TaxRate
object
Model for Tax rate data, wich contains a name and a percentage.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eci-solutions-financial-v2-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 EvolutionX Ecommerce API
ECI Einvoice API
ECI Shipping API
ECI Currency Data API
ECI AP/AR Commerce Automation API
ECI Office Integration API
Where this information came from

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