Boxc Inbound API
The Inbound resource is part of the fulfillment component and allows customers to restock their products at warehouses operated by BoxC. An inbound shipment's products can't be modified after creation, but the warehouse, carrier, tracking number, and notes can be modified.### Inbound StatusThe following table lists all possible states of an inbound shipment indicated by its `status` property. Only the system or warehouse can modify a shipment's status.| Status | Description ||--------|-------------|| Pending | The inbound shipment was created and may be en route to the warehouse. Default state. || Received | The inbound shipment arrived at the warehouse. It can no longer be updated or deleted. || Processed | The inbound shipment was processed and inventoried by the warehouse. |
Boxc Inbound API is one of 22 APIs that Boxc publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Inbound. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 5 operations across 2 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 1.123.
Requests are made against a single base URL, https://api.boxc.com/v1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Boxc Inbound API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT).
It accepts HTTP bearer tokens (PrivilegedClient).
JWT— All operations require a JSON Web Token after completing an [OAuth2 flow](tag/Authentication).PrivilegedClient— Some clients require special privileges to use operations. No additional scope is needed.
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.
The Inbound resource is part of the fulfillment component and allows customers to restock their products at warehouses operated by BoxC. An inbound shipment's products can't be mo…
Schemas 21
The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are inbound (10 properties), inbound-shipments (9 properties), warehouse (7 properties), inbound-product (7 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Boxc 12
Other APIs Boxc publishes across the network.
This is an independent, third-party profile of Boxc Inbound 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.