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
Omniful, Inc.

Omniful, Inc. Shipment Orders API

The Shipment Orders API from Omniful, Inc. — 18 operation(s) for shipment orders.

Documentation Provider Profile APIs.io OpenAPI GitHub

Omniful, Inc. Shipment Orders API is one of 34 APIs that Omniful, Inc. publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Shipment Orders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 20 operations across 18 paths. It is described by OpenAPI 3.0.3, at version v1.

Requests are made against a single base URL, https://prodapi.omniful.com.

20 operations 18 paths 0 schemas 10 GET6 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
v1
Base URL
https://prodapi.omniful.com
Authentication
HTTP Bearer
Contact
https://docs.omniful.tech
Resource Areas
1

Authentication & Security 1

Omniful, Inc. Shipment Orders API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 20

Across 18 paths, the API surfaces 20 operations — 10 GET, 6 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Shipment Orders 20
POST
/sales-channel/public/v1/seller/shipment_orders/{order_id}/return_orders
Create Return Shipment Order
postCreateReturnShipmentOrder 1 param body → 200
GET
/sales-channel/public/v1/seller/shipment_orders/return_orders
Get Return Shipment Orders
getGetReturnShipmentOrders → 200
GET
/sales-channel/public/v1/seller/shipment_orders/return_orders/{return_order_id}
Get Return Shipment Order By ID
getGetReturnShipmentOrderById 1 param → 200
POST
/sales-channel/public/v1/seller/shipment_orders/{order_id}/return_requests
Create Return Shipment Request
postCreateReturnShipmentRequest 1 param body → 200
GET
/sales-channel/public/v1/seller/shipment_orders/return_requests
Get Return Shipment Requests
getGetReturnShipmentRequests → 200
PUT
/sales-channel/public/v1/seller/shipment_orders/return_requests/{order_id}/approve
Approve Return Shipment Request
putApproveReturnShipmentRequest 1 param body → 200
PUT
/sales-channel/public/v1/seller/shipment_orders/return_requests/{return_request_id}/reject
Reject Return Shipment Request
putRejectReturnShipmentRequest 1 param → 200
GET
/sales-channel/public/v1/seller/shipment_orders
Get Shipment Orders
getGetShipmentOrders → 200
POST
/sales-channel/public/v1/seller/shipment_orders
Create Shipment Order
postCreateShipmentOrder body → 200
GET
/sales-channel/public/v1/seller/shipment_orders/{id}
Get Shipment Orders By ID
getGetShipmentOrdersById 1 param → 200
POST
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders/{order_id}/return_orders
Create Return Order
postCreateReturnOrder3 2 params body → 200
GET
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders/return_orders
Get Return Orders
getGetReturnOrders3 1 param → 200
GET
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders/return_orders/{return_order_id}
Get Return Order by Id
getGetReturnOrderById2 2 params → 200
POST
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders/{order_id}/return_requests
Create Return Request
postCreateReturnRequest3 2 params body → 200
GET
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders/return_requests
Get Return Request
getGetReturnRequest 1 param → 200
PUT
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders/return_requests/{return_request_id}/approve
Approve Return Request
putApproveReturnRequest4 2 params body → 200
PUT
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders/return_requests/{return_request_id}/reject
Reject Return Request
putRejectReturnRequest3 2 params → 200
GET
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders
Get Shipment Orders
getGetShipmentOrders2 1 param → 200
POST
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders
Create Shipment Order
postCreateShipmentOrder2 1 param body → 200
GET
/sales-channel/public/v1/tenants/sellers/{seller_code}/shipment_orders/{id}
Get Shipment Order By ID
getGetShipmentOrderById 2 params → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

omniful-inc-shipment-orders-api-openapi.yml Raw ↑

Other APIs Omniful, Inc. publishes across the network.

Omniful, Inc. Background Jobs API
AE Profile APIs.io
Omniful, Inc. Billing API
AE Profile APIs.io
Omniful, Inc. Courier Partners API
AE Profile APIs.io
Omniful, Inc. Customers API
AE Profile APIs.io
Omniful, Inc. Cycle Count API
AE Profile APIs.io
Omniful, Inc. Hubs API
AE Profile APIs.io
Omniful, Inc. Inventory API
AE Profile APIs.io
Omniful, Inc. Orders API
AE Profile APIs.io
Omniful, Inc. Orders (V2) API
AE Profile APIs.io
Omniful, Inc. Packaging Material API
AE Profile APIs.io
Omniful, Inc. Packaging Materials API
AE Profile APIs.io
Omniful, Inc. Pickup Locations API
AE Profile APIs.io
#Shipment Orders
← Back to O APIs
API Details
ID
omniful-inc:omniful-inc-shipment-orders-api
Base URL
https://prodapi.omniful.com
Docs
https://docs.omniful.tech
Provider
Omniful, Inc.
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=omniful-inc-shipment-orders-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/omniful-inc-shipment-orders-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 Omniful, Inc. Shipment Orders 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.