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

Boxc Reshipments API

The Reshipments resource allows you to reship one or more returned packages at a time from a BoxC warehouse. When a reshipment is created the `status` of all included returns will change to "Reshipping". Only returns with the following status can be reshipped: Processed, Verifying, and Verified. If reshipping more than one return at a time then you must wait for a facility operator to provide an `estimated_reship_fee`. If reshipping one return then the estimate will be instantaneous. In both cases you must approve the estimate before the reshipment is sent and your account is charged.**Note:** All returns in a bulk reshipment (> 1 return) must reside in the same warehouse.### StatusWhen a reshipment is created its status is set to "Pending" by default. It will remain that way until the `estimated_reship_fee` is populated by the system or facility operator. Afterwards, you have the option to approve or decline the amount by [updating](/#tag/Reshipments/operation/updateReshipment) the status accordingly. If "Declined", it will not be reshipped. If "Approved" it will be reshipped, tracking information will be made available, and a final reship_fee will be provided. Reshipments with the status "Approved" cannot be deleted.**Important:** Reshipments that are "Pending" or "Declined" longer than 15 days will be deleted by the system.**Note:** The final reshipping fee may differ from the estimated reshipping fee.

Boxc Reshipments API is one of 22 APIs that Boxc publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Reshipments. 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 18 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.

5 operations 2 paths 18 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.123
Base URL
https://api.boxc.com/v1
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Boxc Reshipments 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.

Reshipments 5

The Reshipments resource allows you to reship one or more returned packages at a time from a BoxC warehouse. When a reshipment is created the status of all included returns will c…

GET
/reshipments
GET /reshipments
getReshipments 3 params → 200400401403429
POST
/reshipments
POST /reshipments
addReshipment body → 201400401403429500
GET
/reshipments/{id}
GET /reshipments/{id}
getReshipmentsById 1 param → 200401403404429
PUT
/reshipments/{id}
PUT /reshipments/{id}
updateReshipment 1 param body → 200400401402403404429500
DELETE
/reshipments/{id}
DELETE /reshipments/{id}
deleteReshipment 1 param → 200400401403404429500

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are reshipment (12 properties), to (10 properties), bad-request (4 properties), not-found (4 properties). Each schema is shown below with its type and property counts.

internal-server-error
object
Processing Error
4 properties
reshipment
object
12 properties 4 required
rate-limit
Too Many Requests
NotFound
forbidden
Forbidden
Reshipment
RateLimit
To
bad-request
object
Validation error with the request
4 properties
Forbidden
BadRequest
not-found
object
Object not found or not owned by the user
4 properties
unauthorized
Unauthorized
Unauthorized
InternalServerError
PaymentRequired
to
object
The recipient's shipping address. This may or may not be the same as the consignee. Countries have different formatting rules and element requirements for addr…
10 properties 4 required
payment-required
Payment Required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

boxc-reshipments-api-openapi.yml Raw ↑

Other APIs Boxc publishes across the network.

Boxc CalculateDuty API
Boxc Classify API
Boxc Credentials API
Boxc CustomsProducts API
Boxc EntryPoints API
Boxc Estimate API
Boxc Inbound API
Boxc Invoices API
Boxc Labels API
Boxc Manifests API
Boxc Orders API
Boxc Overpacks API
Where this information came from

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