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

Sage Sales Invoices API

Sales invoice creation and management

Sage Sales Invoices API is one of 13 APIs that Sage publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 5 operations across 2 paths, and defines 11 schemas. It is described by OpenAPI 3.1.0, at version 3.1.0.

Requests are made against a single base URL, https://api.accounting.sage.com/v3.1.

5 operations 2 paths 11 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.1.0
Server
https://api.accounting.sage.com/v3.1
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Sage Sales Invoices API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 2 scopes. By default, every request must be authenticated.

Paths & Operations 5

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

Sales Invoices 5

Sales invoice creation and management

GET
/sales_invoices
List Sales Invoices
listSalesInvoices 6 params → 200
POST
/sales_invoices
Create Sales Invoice
createSalesInvoice body → 201
GET
/sales_invoices/{key}
Get Sales Invoice
getSalesInvoice 1 param → 200
PUT
/sales_invoices/{key}
Update Sales Invoice
updateSalesInvoice 1 param body → 200
DELETE
/sales_invoices/{key}
Delete Sales Invoice
deleteSalesInvoice 1 param → 204

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are SalesInvoice (13 properties), LineItem (9 properties), LineItemInput (5 properties), SalesInvoiceList (3 properties). Each schema is shown below with its type and property counts.

LineItem
object
9 properties
SalesInvoice
object
13 properties
LineItemInput
object
5 properties 4 required
SalesInvoiceList
object
3 properties
CurrencyRef
object
2 properties
TaxRateRef
object
2 properties
StatusRef
object
2 properties
UpdateSalesInvoiceRequest
object
1 property
ContactRef
object
2 properties
CreateSalesInvoiceRequest
object
1 property
LedgerAccountRef
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sage-sales-invoices-api-openapi.yml Raw ↑

Other APIs Sage publishes across the network.

Sage Intacct API
Sage X3 API
Sage 200 API
Sage 50 Accounts API
Sage Bank Accounts API
Sage Business API
Sage Contacts API
Sage Ledger Accounts API
Sage Payments API
Sage Products API
Sage Purchase Invoices API
Sage Tax Rates API
Where this information came from

This is an independent, third-party profile of Sage Sales Invoices 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.