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

AxleHire (Jitsu) Shipping Information API

Shipment specific calls

AxleHire (Jitsu) Shipping Information API is one of 5 APIs that AxleHire (Jitsu) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Shipping Information. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 28 operations across 22 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 3.0.0.

Requests are made against 2 base URLs: https://api.staging.gojitsu.com, https://api.gojitsu.com.

28 operations 22 paths 20 schemas 2 DELETE8 GET5 PATCH9 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.0
Base URL
https://api.gojitsu.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

AxleHire (Jitsu) Shipping Information API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Authorization). By default, every request must be authenticated.

  • Authorization — Authorization header for all calls in format: 'Authorization : Token {YOURTOKEN}'

Paths & Operations 28

Across 22 paths, the API surfaces 28 operations — 2 DELETE, 8 GET, 5 PATCH, 9 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Shipping Information 28

Shipment specific calls

POST
/v3/shipments
Submit Shipment
create body → default2XX
GET
/v3/shipments/{shipment_id}/label
Retrieve Shipment Label
label 2 params → default2XX
GET
/v3/shipments/{shipment_id}
Retrieve Shipment
retrieve_1 1 param → default2XX
PUT
/v3/shipments/{shipment_id}
Update Shipment
updateShipment 1 param body → default2XX
PUT
/v3/shipments/{shipment_id}/parcels/{id}
Update Individual Parcel
updateParcel 2 params body → default2XX
DELETE
/v3/shipments/{shipment_id}/parcels/{id}
Delete Individual Parcel
deleteParcel 2 params body → default2XX
GET
/v3/shipments/{shipment_id}/parcels
Retrieve Parcels
getParcelsByShipmentId 1 param → default2XX
PUT
/v3/shipments/{shipment_id}/parcels
Add Parcels
updateAndAddParcels 2 params body → default2XX
POST
/v3/shipments/{shipment_id}/parcels
Create Parcels
createParcels 1 param body → default2XX
DELETE
/v3/shipments/{shipment_id}/parcels
Delete All Parcels
deleteParcels 1 param → default2XX
PATCH
/v3/shipments/{shipment_id}/parcels
Delete/Update Parcels
updateOrDeleteParcel 2 params body → default2XX
PATCH
/v3/shipments/{shipment_id}/pickup_address
Update Pickup Address
updatePickupAddress 1 param body → default2XX
PATCH
/v3/shipments/{shipment_id}/dropoff_address
Update Dropoff Address
updateDropoffAddress 1 param body → default2XX
PATCH
/v3/shipments/{shipment_id}/customer
Update Customer
updateCustomer 1 param body → default2XX
PATCH
/v3/shipments/{shipment_id}/notes
Update Instruction Notes
notes 1 param body → default2XX
POST
/v3/shipments/mark-shipped
Mark Shipments Shipped
markAsShippedBulk body → default2XX
POST
/v3/shipments/{shipment_id}/dropoff-time
Update Dropoff Time
updateShipmentTimeWindow 1 param body → default2XX
GET
/v3/shipments/{shipment_id}/fee
Retrieve Shipment Fee
getShipmentDeliveryFee 1 param → default2XX
GET
/v3/shipments/{shipment_id}/history
Get history of a shipment
retrieveHistory 1 param → default2XX
GET
/v3/shipments/{shipment_id}/parcels/label
Retrieve Parcel Labels
labelParcels 3 params → default2XX
POST
/v3/shipments/{shipment_id}/cancel
Cancel Shipment
cancelShipment 1 param body → default2XX
POST
/v3/shipments/{shipment_id}/ready
Signal Shipment Readiness
readyShipment 1 param → default2XX
POST
/v3/shipments/{shipment_id}/mark-shipped
Mark Shipment Shipped
markAsShipped 1 param body → default2XX
POST
/v3/shipments/{shipment_id}/workload
Update Shipment Workload
updateShipmentWorkload 1 param body → default2XX
GET
/v3/shipments/{shipment_id}/parcels/{jitsu_parcel_id}/label
Retrieve Parcel Label
labelParcel 4 params → default2XX
PUT
/v3/shipments/{shipment_id}/dropoff-location-info
Update Dropoff Location Info
updateShipmentDropoffLocationInfo 2 params body → default2XX
POST
/v3/shipments/rating
Estimated fee
getEstimatedFee body → default2XX
GET
/v3/shipments/{shipment_id}/pod
Retrieve Shipment Photos and Signature
getPod 2 params → default2XX

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are Shipment (46 properties), Parcel (15 properties), Address (8 properties), Dimension (5 properties). Each schema is shown below with its type and property counts.

NewShipmentResponse
object
2 properties
DeliveryPod
object
Proof of delivery information
3 properties
TimeWindow
object
2 properties 2 required
Address
object
An address is a structured entity that contains address components
8 properties
MarkAsShippedRequest
object
4 properties
Customer
object
A customer represents the essential information we should know about your customer or the recipient.
3 properties 1 required
Email
string
Properly formatted email address
Phone-Number
string
10 digit phone number
ParcelId
integer
Unique Jitsu identifier for Parcel
ShipmentDeliveryInfo
object
Shipment delivery info
2 properties
Parcel
object
15 properties
CancelShipmentRequest
object
1 property
NotesRequest
object
2 properties
ShipmentId
integer
Unique identifier for a Shipment
Dimension
object
Size of parcel typically using height, width, and length
5 properties
Price
object
4 properties
DropoffInfo
object
2 properties
Shipment
object
Base shipment model
46 properties 6 required
Remark
object
3 properties
Weight
object
Parcel weight
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

axlehire-shipping-information-api-openapi.yml Raw ↑

Other APIs AxleHire (Jitsu) publishes across the network.

AxleHire (Jitsu) Assignment Information API
AxleHire (Jitsu) Driver Information API
AxleHire (Jitsu) Partner Information API
AxleHire (Jitsu) Tracking Information API
Where this information came from

This is an independent, third-party profile of AxleHire (Jitsu) Shipping Information 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.