> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/developers-api/sales-order-management/release-sales-order.md).

# Release Sales Order

Run the release workflow for salesorder records in Xorosoft ERP. This operation is typically used after the related transaction already exists and the external system needs to advance its processing status.

```json
{"openapi":"3.0.3","info":{"title":"Xorosoft ERP Public API","version":"2026.07"},"tags":[{"name":"Sales Order Management","description":"Use Sales Order Management APIs to create, retrieve, release, close, cancel, and inspect sales orders. These endpoints support order integrations from ecommerce, marketplace, EDI, B2B, and customer-service systems. Sales order payloads commonly include customer, store, shipping, billing, payment terms, order dates, line items, quantities, pricing, taxes, discounts, and third-party reference fields."}],"servers":[{"url":"https://res.xorosoft.io","description":"Xorosoft ERP API server"}],"security":[{"basic":[]}],"components":{"securitySchemes":{"basic":{"scheme":"basic","type":"http"}},"schemas":{"XoroApiResponse":{"type":"object","description":"Standard Xorosoft ERP API response envelope used by most endpoints.","properties":{"Result":{"type":"boolean","description":"True when the operation completed successfully."},"Message":{"type":"string","description":"Human-readable success or error message."},"Data":{"description":"Endpoint-specific payload.","type":"object","additionalProperties":true,"nullable":true},"Page":{"type":"integer","description":"Current page number when paging is enabled.","nullable":true},"TotalPages":{"type":"integer","description":"Total page count when paging is enabled.","nullable":true}}},"PostSalesorderReleaseRequest":{"type":"object","properties":{"SoEstimateHeader":{"type":"object","description":"Sales order header values for the shipment or release workflow.","properties":{"ThirdPartyRefNo":{"type":"string"},"CustomerName":{"type":"string"}}},"SoEstimateItemLineArr":{"type":"array","description":"Sales order item lines included in the shipment or release workflow.","items":{"type":"object","properties":{"ItemNumber":{"type":"string"},"Qty":{"type":"integer"}}}}},"description":"Request body for Release.","additionalProperties":true}}},"paths":{"/api/xerp/salesorder/release":{"post":{"tags":["Sales Order Management"],"summary":"Release Sales Order","description":"Run the release workflow for salesorder records in Xorosoft ERP. This operation is typically used after the related transaction already exists and the external system needs to advance its processing status.","operationId":"post_salesorder_release","responses":{"200":{"description":"Request processed successfully.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/XoroApiResponse"}}}},"400":{"description":"Invalid request, failed validation, or business rule error.","content":{"text/plain":{"schema":{"type":"string"}}}},"401":{"description":"Missing or invalid private app credentials."},"403":{"description":"Private app does not have permission for this request."}},"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/PostSalesorderReleaseRequest"}}}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xorosoft.com/developers-api/sales-order-management/release-sales-order.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.