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
Geniemode

Geniemode Shipment Controller API

Shipment Controller

Documentation Provider Profile APIs.io OpenAPI GitHub

Geniemode Shipment Controller API is one of 95 APIs that Geniemode publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include shipment-controller. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 26 operations across 23 paths, and defines 45 schemas. It is described by OpenAPI 3.2.0, at version API V.

Requests are made against a single base URL, https://portal.geniemode.com.

26 operations 23 paths 45 schemas 13 GET3 POST10 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
API V
Base URL
https://portal.geniemode.com
Contact
Mani Bhushan
License
License of API
Terms of Service
View terms
Resource Areas
1

Paths & Operations 26

Across 23 paths, the API surfaces 26 operations — 13 GET, 3 POST, 10 PUT. Each is listed below with its method, path, parameters, and response codes.

shipment-controller 26

Shipment Controller

PUT
/api/v1/order/shipments/assign/bulk/shipments/{userId}
assignBulkShipments
assignBulkShipmentsUsingPUT 1 param body → 200
PUT
/api/v1/order/shipments/assign/{entityType}/{entityId}/{userId}
getOrderShipments
getOrderShipmentsUsingPUT_1 3 params → 200
GET
/api/v1/order/shipments/auditor-list
getShipmentAuditorList
getShipmentAuditorListUsingGET → 200403500
GET
/api/v1/order/shipments/backfill/{type}
backfill
backfillUsingGET 1 param → 200403500
POST
/api/v1/order/shipments/checkForInvoice
checkForInvoice
checkForInvoiceUsingPOST body → 200
GET
/api/v1/order/shipments/dashboard/docs
getShipmentDashboardDocs
getShipmentDashboardDocsUsingGET 2 params → 200403500
GET
/api/v1/order/shipments/dashboard/invoice/{invoiceId}
getInvoiceShipment
getInvoiceShipmentUsingGET 1 param → 200403500
GET
/api/v1/order/shipments/doc-types
getPossibleShipmentDocTypes
getPossibleShipmentDocTypesUsingGET 3 params → 200403500
GET
/api/v1/order/shipments/docs/{orderId}
getShipmentDocs
getShipmentDocsUsingGET 1 param → 200403500
GET
/api/v1/order/shipments/find-similar-shipment-hops
findSimilarShipmentHops
findSimilarShipmentHopsUsingGET 2 params → 200403500
PUT
/api/v1/order/shipments/hop/{docId}/removeDoc
removeDocFromShipment
removeDocFromShipmentUsingPUT 1 param → 200
PUT
/api/v1/order/shipments/hop/{shipmentId}/audit/{hopId}
updateShipmentHopAudit
updateShipmentHopAuditUsingPUT 2 params body → 200
GET
/api/v1/order/shipments/hops/audit
getShipmentHopsForAudit
getShipmentHopsForAuditUsingGET 3 params → 200403500
PUT
/api/v1/order/shipments/invoice/{invoiceId}/hops
editInvoiceShipmentHop
editInvoiceShipmentHopUsingPUT 1 param body → 200
GET
/api/v1/order/shipments/logistics/cost
getShipmentLogisticsCost
getShipmentLogisticsCostUsingGET 1 param → 200403500
GET
/api/v1/order/shipments/partners
getShipmentPartners
getShipmentPartnersUsingGET → 200403500
GET
/api/v1/order/shipments/pos
getPos
getPosUsingGET 1 param → 200403500
PUT
/api/v1/order/shipments/unassign/bulk/shipments/{userId}
unassignBulkShipments
unassignBulkShipmentsUsingPUT 1 param body → 200
PUT
/api/v1/order/shipments/unassign/{entityType}/{entityId}
unassignShipmentEntity
unassignShipmentEntityUsingPUT 2 params → 200
GET
/api/v1/order/shipments/{orderId}
getShipments
getShipmentsUsingGET 1 param → 200403500
POST
/api/v1/order/shipments/{orderId}
createShipments
createShipmentsUsingPOST 1 param body → 200
PUT
/api/v1/order/shipments/{orderId}
updateShipments
updateShipmentsUsingPUT 1 param body → 200
GET
/api/v1/order/shipments/{shipmentId}/dashboard
getShipment
getShipmentUsingGET 1 param → 200403500
POST
/api/v1/order/shipments/{shipmentId}/hops
addShipmentHop
addShipmentHopUsingPOST 1 param body → 200
PUT
/api/v1/order/shipments/{shipmentId}/hops
editShipmentHop
editShipmentHopUsingPUT 1 param body → 200
PUT
/api/v1/order/shipments/{shipmentId}/refresh/hops
refreshHops
refreshHopsUsingPUT_1 1 param → 200

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are LogisticsDashboardShipmentResponse (59 properties), LogisticsDashboardInvoiceShipmentResponse (31 properties), ShipmentHopRequestPayload (25 properties), InvoiceVariantsDto (22 properties). Each schema is shown below with its type and property counts.

ShipmentSingleDocTypeResponsePayload
object
3 properties
ShipmentHopRequestPayload
object
25 properties
CheckForInvoiceRequestPayload
object
1 property
LeadGenerationLiteResponse
object
14 properties
ShipmentsRequestPayload
object
1 property
BrandVpDto
object
4 properties
OrderRmLogisticsCostResponsePayload
object
12 properties
VariantBuyerPoMappingRequestPayload
object
5 properties
OrderDocDto
object
9 properties
InvoiceVariantBuyerPoMappingDto
object
10 properties
FinalInvoiceInInvoiceDto
object
11 properties
PoMinDto
object
5 properties
OrderBuyerPoBaseDto
object
2 properties
VariantRequestPayload
object
16 properties
ShipmentInvoiceDto
object
6 properties
UpdateShipmentHopAuditRequestPayload
object
2 properties
ShipmentHopDto
object
11 properties
GeniemodeEntityDto
object
11 properties
DocDto
object
4 properties
ShipmentDocTypeResponsePayload
object
8 properties
InvoiceShipmentsResponsePayload
object
2 properties
ShipmentLogisticCostsResponsePayload
object
5 properties
ShipmentDto
object
18 properties
CompanyDTO
object
7 properties
BrandCategoryDto
object
3 properties
ShipmentVariantBuyerPoMappingDto
object
6 properties
FinalInvoiceDiscountDto
object
3 properties
LogisticsDashboardInvoiceShipmentResponse
object
31 properties
ShipmentPartnersDto
object
2 properties
LeadProjectionMiniDTO
object
5 properties
BulkShipmentAssignmentRequestPayload
object
1 property
ShipmentDocDto
object
3 properties
ShipmentInInvoiceOrderDto
object
18 properties
LogisticsDashboardShipmentResponse
object
59 properties
InvoiceShipmentHopRequestPayload
object
20 properties
ShipmentPacketsDto
object
4 properties
InvoiceVariantsDto
object
22 properties
OrderCustomDuty
object
14 properties
BrandResponse
object
13 properties
ShipmentInInvoiceDto
object
14 properties
ShipmentHopDocsDTO
object
1 property
ShipmentRequestPayload
object
11 properties
ShipmentHopMiniDto
object
8 properties
ShipmentVariantDto
object
6 properties
AddressSubmitResponsePayload
object
14 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

geniemode-shipment-controller-api-openapi.yml Raw ↑

Other APIs Geniemode publishes across the network.

Geniemode Admin API
AE Profile APIs.io
Geniemode Admin Controller API
AE Profile APIs.io
Geniemode Admin Qc Audio Recording Controller API
AE Profile APIs.io
Geniemode Audit Controller API
AE Profile APIs.io
Geniemode Audit Order Product Attribution Controller API
AE Profile APIs.io
Geniemode Authorisation API
AE Profile APIs.io
Geniemode Back Fill Controller API
AE Profile APIs.io
Geniemode Bank Controller API
AE Profile APIs.io
Geniemode Business Owner Controller API
AE Profile APIs.io
Geniemode Carton Controller API
AE Profile APIs.io
Geniemode Change Tna Request Controller API
AE Profile APIs.io
Geniemode Client Controller API
AE Profile APIs.io
#shipment-controller
← Back to G APIs
API Details
ID
geniemode:geniemode-shipment-controller-api
Base URL
https://portal.geniemode.com
Docs
https://portal.geniemode.com/
Provider
Geniemode
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=geniemode-shipment-controller-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/geniemode-shipment-controller-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 Geniemode Shipment Controller 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.