Orchestra Internal API Mapping

Order

Order management operations with 3-layer architecture: API Gateway -> Order Management Orchestrator -> Core Microservices

View Postman Documentation

3-Layer Architecture

API Gateway Public (Internet)
Order Management Internal Orchestration
Core Microservices Internal Services

List Orders

Search & Filter

Retrieve paginated list of customer orders with filtering and sorting (2 steps)

POST
API Gateway Layer 1 - Public
POST /orders
Order Management Layer 2 - Orchestration
POST /orders

Orchestrates 2 service calls

Layer 3 - Service Calls (2 Steps)
1 Order Service Core Microservices
POST /api/orders/search

Returns paginated order list with basic info

2 Order Service Core Microservices
POST /api/orders/stats

Returns counts by status (pending, shipped, delivered, cancelled, returned)

Get Order Details

Full Details

Retrieve complete order details including items, addresses, payment, shipping (2 steps)

GET
API Gateway Layer 1 - Public
GET /orders/:order_id
Order Management Layer 2 - Orchestration
GET /orders/:order_id

Orchestrates 2 service calls (with caching)

Layer 3 - Service Calls (2 Steps)
⚡ Step 1: Get from cache first - return if available
1 Order Service Core Microservices (if not in cache)
GET /api/orders/:order_id

Returns full order with items, addresses, payment summary

2 Caching Service Shared Services
POST /api/caching/set

Cache order for future requests

Track Order

Real-time Tracking

Get real-time tracking information with shipment status and delivery timeline (2 steps)

GET
API Gateway Layer 1 - Public
GET /orders/:order_id/fulfillments/:fulfillment_id/track
Order Management Layer 2 - Orchestration
GET /orders/:order_id/fulfillments/:fulfillment_id/track

Orchestrates 2 service calls (with caching)

Layer 3 - Service Calls (2 Steps)
⚡ Step 1: Get from cache first - return if available
1 Order Service Core Microservices (if not in cache)
GET /api/orders/:order_id

Get fulfillment object from order, validate order exists and belongs to customer

2 Caching Service Shared Services
POST /api/caching/set

Cache order tracking for future requests

Delete Order

Hide/Delete

Hide/delete order from customer's order history (1 step)

DELETE
API Gateway Layer 1 - Public
DELETE /orders/:order_id
Order Management Layer 2 - Orchestration
DELETE /orders/:order_id

Orchestrates 1 service call

Layer 3 - Service Calls (1 Step)
1 Order Service Core Microservices
DELETE /api/orders/:order_id/hide

Hide/delete order from customer view (soft delete)

Services Used in Order Module

📦

Order Service

Order CRUD, search, stats, fulfillments

⚡

Caching Service

Order and tracking cache

🎯

Order Management

Orchestration layer

Order Module - Orchestra Internal API Mapping | 4 APIs | 7 Total Steps