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

ShipBob subpackage_receiving API

The subpackage_receiving API from ShipBob — 8 operation(s) for subpackage_receiving.

ShipBob subpackage_receiving API is one of 10 APIs that ShipBob publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, release notes, and rate-limit docs.

This API exposes 9 operations across 8 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.shipbob.com, https://sandbox-api.shipbob.com.

9 operations 8 paths 28 schemas 6 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.shipbob.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

ShipBob subpackage_receiving API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (PAT).

  • PAT — Authentication using Personal Access Token (PAT) token or OAuth2

Paths & Operations 9

Across 8 paths, the API surfaces 9 operations — 6 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

subpackage_receiving 9
POST
/2026-01/receiving
Create Warehouse Receiving Order
create-warehouse-receiving-order 1 param body → 201400401403404
GET
/2026-01/receiving
Get Multiple Warehouse Receiving Orders
get-multiple-warehouse-receiving-orders 12 params → 200401403404
GET
/2026-01/receiving/{id}
Get Warehouse Receiving Order
get-warehouse-receiving-order 2 params → 200401403404
GET
/2026-01/fulfillment-center
Get Fulfillment Centers
get-fulfillment-centers 1 param → 200401403
GET
/2026-01/receiving/{id}/boxes
Get Warehouse Receiving Order Boxes
get-warehouse-receiving-order-boxes 2 params → 200401403404
GET
/2026-01/receiving/{id}/labels
Get Warehouse Receiving Order Box Labels
get-warehouse-receiving-order-box-labels 2 params → 200400401403404
POST
/2026-01/receiving/{id}:cancel
Cancel Warehouse Receiving Order
cancel-warehouse-receiving-order 2 params → 200401403404422
POST
/2026-01/receiving:setExternalSync
Set ExternalSync flag for Wros
set-external-sync-flag-for-wros 1 param body → 200400401403
GET
/2026-01/receiving/{id}/distributions
Get Inventory Distributions by WRO ID
get-inventory-distributions-by-wro-id 2 params → 200400404500

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are Receiving.V2.WarehouseReceivingOrderViewModel (13 properties), Receiving.FulfillmentCenterViewModel (11 properties), Receiving.DistributionItem (10 properties), Receiving.BoxViewModel (8 properties). Each schema is shown below with its type and property counts.

Receiving.WarehousePickupRequestStatus
string
Receiving.Get.2.0.Receiving.Id.Labels.OK.String
string
Receiving.BoxStatus
string
Receiving.V2.WarehouseReceivingOrderViewModel
object
13 properties
Receiving.BoxItemViewModel
object
Information about an item contained inside a box as part of a receiving order
6 properties
Receiving.WroDistributionDetailsResponse
object
3 properties
Receiving.Post.2.0.Receiving.Id.Cancel.Unprocessable.Entity.Object
object
Receiving.Post.2.0.Receiving.Set.External.Sync.Bad.Request.Object
object
Receiving.PackageType
string
Receiving.AssignOrderToFulfillmentCenterModel
object
Model containing information that assigns a receiving order to a fulfillment center. If the fulfillment center provided is in a receiving hub region, then the…
1 property 1 required
Receiving.UpdateExternalSyncModel
object
2 properties
Receiving.Post.2.0.Receiving.Bad.Request.Object
object
Receiving.AddBoxToOrderModel
object
Information about a box shipment to be added to a receiving order
2 properties 2 required
Receiving.V2.WarehouseReceivingOrderViewModelArray
array
Receiving.FulfillmentCenterViewModelArray
array
Receiving.V2.InventoryQuantityViewModel
object
5 properties
Receiving.PackingType
string
Receiving.DistributionItem
object
10 properties
Receiving.AddBoxItemToBoxModel
object
Information about an inventory item contained inside a receiving order box
4 properties 2 required
Receiving.CreateReceivingOrderModel
object
Information to create a new receiving order
6 properties 5 required
Receiving.FulfillmentCenterViewModel
object
Information about a fulfillment center
11 properties
Receiving.BoxViewModel
object
Information about a box shipment included in a receiving order
8 properties
Receiving.BoxViewModelArray
array
Receiving.ReceivingStatus
string
Receiving.DistributionStatus
string
Receiving.ProblemDetails
object
Receiving.ValidationProblemDetails
object
6 properties
Receiving.V2.ReceivingOrderStatusHistoryViewModel
object
View model for receiving order status history
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

shipbob-subpackage-receiving-api-openapi.yml Raw ↑

Other APIs ShipBob publishes across the network.

ShipBob subpackage_billing API
ShipBob subpackage_channels API
ShipBob subpackage_inventory API
ShipBob subpackage_locations API
ShipBob subpackage_orders API
ShipBob subpackage_products API
ShipBob subpackage_returns API
ShipBob subpackage_simulations API
ShipBob subpackage_webhooks API
Where this information came from

This is an independent, third-party profile of ShipBob subpackage_receiving 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.