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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Xentral

Xentral Sales Order API

SalesOrders are an outbound orders, meaning that someone has bought from you.

Documentation Provider Profile APIs.io OpenAPI GitHub

Xentral Sales Order API is one of 85 APIs that Xentral publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sales Order. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 32 operations across 21 paths. It is described by OpenAPI 3.2.0, at version v0.1.

Requests are made against 2 base URLs: https://{xentralId}.xentral.biz, https://{domain}.

32 operations 21 paths 0 schemas 5 DELETE7 GET13 PATCH7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v0.1
Base URL
https://xentral.xentral.biz
Authentication
HTTP Bearer
Contact
Xentral
Resource Areas
1

Authentication & Security 1

Xentral Sales Order API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

  • BearerAuth — Bearer token obtained in POST /tokens endpoint or pregenerated in the system.

Paths & Operations 32

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

Sales Order 32

SalesOrders are an outbound orders, meaning that someone has bought from you.

GET
/api/v1/salesOrders
List sales orders
salesOrder.list 3 params → 200403406429
POST
/api/v1/salesOrders/actions/import
Import sales order
salesOrder.import body → 201400403406
POST
/api/v1/salesOrders/{id}/actions/dispatch
Dispatch sales order
salesOrder.actions.dispatch 1 param → 204400401403404406429
POST
/api/v1/salesOrders/{id}/actions/cancel
Cancel sales order
salesOrder.actions.cancel 1 param body → 204401403404409429
PATCH
/api/v1/salesOrders/{id}/actions/createPartialSalesOrder
Create partial sales order
salesOrder.actions.createPartialSalesOrder 1 param → 201400401403404409429
GET
/api/v1/salesOrders/{id}
View sales order
salesOrder.view 1 param → 200401403404406429
PATCH
/api/v1/salesOrders/{id}
Update sales order
salesOrder.update 1 param body → 204400403404406
DELETE
/api/v1/salesOrders/{id}
Delete sales order
salesOrder.delete 1 param → 204401403404409429
POST
/api/v1/salesOrders/{id}/documents
Create sales order document
salesOrder.createDocument 1 param body → 201400403404415429
PATCH
/api/v1/salesOrders/{id}/documents
Update multiple sales order documents
salesOrder.updateMultiple 1 param body → 204400403404415429
DELETE
/api/v1/salesOrders/{id}/documents
Delete multiple sales order documents
salesOrder.deleteMultiple 1 param body → 204400403404415429
GET
/api/v1/salesOrders/{id}/documentsdeprecated
List sales order documents
salesOrder.listDocument 3 params → 200403404406415429
GET
/api/v1/salesOrders/{id}/documents/{documentId}deprecated
View sales order document
salesOrder.viewDocument 3 params → 200403404406429
GET
/api/v3/salesOrders
List sales orders V3
GET::api-v3-salesorders 8 params → 200401403429
POST
/api/v3/salesOrders
🔒 Create sales order V3
POST::api-v3-salesorders body → 201400401403429
GET
/api/v3/salesOrders/{id}
View sales order V3
GET::api-v3-salesorders-id 2 params → 200401403404429
DELETE
/api/v3/salesOrders/{id}
Delete sales order V3
DELETE::api-v3-salesorders-id 1 param → 204401403404409429
PATCH
/api/v3/salesOrders/{id}
🔒 Update sales order V3
PATCH::api-v3-salesorders-id 1 param body → 200400401403404409429
PATCH
/api/v3/salesOrders/{id}/actions/cancel
Cancel sales order V3
PATCH::api-v3-salesorders-id-actions-cancel 1 param → 204401403404409429
PATCH
/api/v3/salesOrders/{id}/actions/complete
Complete sales order V3
PATCH::api-v3-salesorders-id-actions-complete 1 param → 204401403404409429
PATCH
/api/v3/salesOrders/{id}/actions/logActivity
Log custom sales order activity V3
PATCH::api-v3-salesorders-id-actions-logactivity 1 param body → 204400401403404429
PATCH
/api/v3/salesOrders/{id}/actions/release
Release sales order V3
PATCH::api-v3-salesorders-id-actions-release 1 param body → 204400401403404409429
PATCH
/api/v3/salesOrders/{id}/actions/removeWriteProtection
Remove sales order write protection V3
PATCH::api-v3-salesorders-id-actions-removewriteprotection 1 param → 204401403404409429
PATCH
/api/v3/salesOrders/{id}/actions/send
Send sales order V3
PATCH::api-v3-salesorders-id-actions-send 1 param body → 204400401403404409429
PATCH
/api/v3/salesOrders/{id}/actions/setWriteProtection
Set sales order write protection V3
PATCH::api-v3-salesorders-id-actions-setwriteprotection 1 param → 204401403404409429
POST
/api/v3/salesOrders/{id}/files
Attach file to sales order V3
POST::api-v3-salesorders-id-files 1 param body → 201400401403404429
DELETE
/api/v3/salesOrders/{id}/files/{fileId}
Delete file from sales order V3
DELETE::api-v3-salesorders-id-files-fileid 2 params → 204401403404429
PATCH
/api/v3/salesOrders/{id}/files/{fileId}
Update file on sales order V3
PATCH::api-v3-salesorders-id-files-fileid 2 params body → 204400401403404429
POST
/api/v3/salesOrders/{id}/lineItems
🔒 Create sales order line item V3
POST::api-v3-salesorders-id-lineitems 1 param body → 201400401403404409429
GET
/api/v3/salesOrders/{id}/lineItems/{lineItemId}
View sales order line item V3
GET::api-v3-salesorders-id-lineitems-lineitemid 3 params → 200401403404429
DELETE
/api/v3/salesOrders/{id}/lineItems/{lineItemId}
Delete sales order line item V3
DELETE::api-v3-salesorders-id-lineitems-lineitemid 2 params → 204401403404409429
PATCH
/api/v3/salesOrders/{id}/lineItems/{lineItemId}
🔒 Update sales order line item V3
PATCH::api-v3-salesorders-id-lineitems-lineitemid 2 params body → 200400401403404409429

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xentral-sales-order-api-openapi.yml Raw ↑

Other APIs Xentral publishes across the network.

Xentral Account API
AE Profile APIs.io
Xentral Accounting Export API
AE Profile APIs.io
Xentral AuthPlatform API
AE Profile APIs.io
Xentral Collection API
AE Profile APIs.io
Xentral Collective Bill API
AE Profile APIs.io
Xentral Credit API
AE Profile APIs.io
Xentral Credit Note API
AE Profile APIs.io
Xentral Credit Note Tag API
AE Profile APIs.io
Xentral Customer Address API
AE Profile APIs.io
Xentral Customer API
AE Profile APIs.io
Xentral Customer - Contact Person API
AE Profile APIs.io
Xentral Customer Delivery Address API
AE Profile APIs.io
#Sales Order
← Back to X APIs
API Details
ID
xentral:xentral-sales-order-api
Base URL
https://xentral.xentral.biz
Docs
https://developer.xentral.com/reference/intro
Provider
Xentral
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=xentral-sales-order-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/xentral-sales-order-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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