The Airport Community System (ACS) is a digital platform designed by Pakistan Single Window (PSW) to modernize air cargo data processing throughout Pakistan. It seamlessly integrates both public sector entities, such as customs authorities and regulatory bodies, and private sector participants, including airlines, freight forwarders, and ground handlers, into a unified digital ecosystem.
\n1) Automated Submissions
\n\n\nCurrently, ground handlers must log into Weboc, a customs portal, to manually upload flight manifests on behalf of the airline. The ACS will automate these tasks, minimizing errors and enhancing operational efficiency.
\n
2) Faster Customs Clearance
\n\n\nIn Pakistan, airlines generally share their manifests with ground handlers rather than directly with customs authorities. This often causes delays, particularly when manifests are submitted late or with errors. The ACS integrates directly with the airline's cargo management system (CMS), allowing for earlier and more accurate manifest submissions, thereby speeding up the customs clearance process.
\n
3) Seamless Sales for Air Cargo Agents
\n\n\nAir cargo agents in Pakistan are responsible for a variety of tasks, including tracking AWB stock, managing shipments, processing bookings, and issuing air waybills. The ACS simplifies these processes, allowing agents to perform their duties more efficiently and with greater accuracy.
\n
What type of integration will be needed with the airline CMS?
\n\n\nWe support integrations with all CMS platforms (Cargospot, IBS iCargo, SmartKargo, CargoFlash, Accelya Skychain, Unisys, Wipro Croamis, etc). The integration required will depend on the airline's existing CMS (Cargo Management System). Typically, the ACS will need to connect with the airline's system for real-time data exchange, including flight status updates, manifest submissions, and cargo tracking. This integration can be achieved through APIs, and our team will work closely with your IT department to ensure seamless integration.
\n
What is the expected timeline for integration with our system?
\n\n\nIntegration with airlines will be starting in Q1 2026 and are expected to be completed with all airlines by Q4 2027. Our team will provide a detailed timeline based on your airline’s specific needs after conducting a system assessment.
\n
How will the ACS handle data security and privacy?
\n\n\nThe ACS adheres to the highest standards of data security, including encryption, secure data transfer protocols, and compliance with relevant regulations like GDPR and local data protection laws. We ensure that all sensitive information is securely stored and handled to protect the privacy of your data and passengers.
\n
Below are screenshots of the Airport Community System (ACS). Note that the ACS is currently being co-designed with various members of the air cargo community in Pakistan, and that these designs will likely change over the next several months.
\nAll API requests must include the following standard headers:
\nConditional Field Examples:
\n\n\n\n
insuranceDetails: Conditional (mandatory ifinsuranceRequired= true)
\n\n\n
dangerousGoodsDetails: Conditional (mandatory ifdangerousGoodsIndicator= true)
\n\n\n
temperatureRange: Conditional (mandatory if commodity requires temperature control)
\n\n","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","toc":[{"content":"Questions about ACS","slug":"questions-about-acs"},{"content":"Glossary & Standards","slug":"glossary-standards"}],"owner":"36739597","collectionId":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","publishedId":"2sBXVigV3j","public":true,"customColor":{"top-bar":"FFFFFF","right-sidebar":"303030","highlight":"FF6C37"},"publishDate":"2026-04-05T00:34:51.000Z"},"item":[{"name":"e-Quote module","item":[{"name":"AWB Stock Management","item":[{"name":"Create AWB Stock","id":"d75ab3ac-3d36-4dfe-b277-dcf70d5baec4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"\n
hawbNumbers: Conditional (mandatory ifshipmentType= \"CONSOLIDATED\")
Unique identifier for request tracing
\n","key":"X-Request-ID","value":"093651b8-e037-460f-b05d-15546edcc456"},{"description":"Identifier of the system making the request (POST, ANF, CUSTOMS, GHA)
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.786Z"}],"body":{"mode":"raw","raw":"{\n \"airlinePrefix\": \"176\",\n \"startingAWBNumber\": \"176-12345678\",\n \"endingAWBNumber\": \"176-12346767\",\n \"additionalNotes\": \"Test AWB Range\",\n \"range\": \"176-12345678-176-12346767\",\n \"totalAWB\": \"90\"\n}","options":{"raw":{"language":"json"}}},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/awb","description":"Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Create AWB Stock
\nIntegration Point: Airline pushes pre-defined AWB stocks
\nProcess Flow: Airline System → Airport Community System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["awb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"d75ab3ac-3d36-4dfe-b277-dcf70d5baec4"},{"name":"Allocate AWB Stock","id":"8605a769-ec3b-4bfb-87e6-50db3d7c3931","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"url":"","description":"Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Process AWB Stock Acquisition Request / Allocate AWB Stock
\nIntegration Point: Stock allocation processing
\nProcess Flow: Airline System → Airport Community System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"8605a769-ec3b-4bfb-87e6-50db3d7c3931"},{"name":"Delete Unallocated AWB Stocks","id":"a2068c3d-02e9-4df6-9eb9-27fe5da4c2d7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"DELETE","header":[],"url":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"a2068c3d-02e9-4df6-9eb9-27fe5da4c2d7"},{"name":"Reduce Allocated AWB Stocks","id":"7dba76ee-c928-402f-a1bd-61c3e3567f58","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"url":"","description":"Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Reduce Allocated AWB Stocks
\nIntegration Point: EQ.E1AL.3
\nProcess Flow: Airline System → Airport Community System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"7dba76ee-c928-402f-a1bd-61c3e3567f58"},{"name":"Withdraw Allocated AWB Stocks","id":"81ba7d9a-c8c5-4584-8107-a190dcc07ad9","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"url":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"81ba7d9a-c8c5-4584-8107-a190dcc07ad9"},{"name":"Extend Validity Period","id":"74059232-e15c-42b5-9cd4-b781fcdacb83","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"url":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"74059232-e15c-42b5-9cd4-b781fcdacb83"},{"name":"Upload Flight Schedule","id":"458cc76c-f9d0-417a-9217-dc896ba689bc","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"url":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"458cc76c-f9d0-417a-9217-dc896ba689bc"},{"name":"Process Shipment Booking","id":"1b857567-c7c0-4eeb-9816-360ad65fca0a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"url":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"1b857567-c7c0-4eeb-9816-360ad65fca0a"}],"id":"4479fdd5-c95d-4da2-a444-bc162f6b02b6","_postman_id":"4479fdd5-c95d-4da2-a444-bc162f6b02b6","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Quote Requests","item":[{"name":"Create Quote Request","id":"081cb9dd-66ab-4727-86ae-10a8ee6a94bc","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"accept":true,"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, ACA-ERP-001, AIRLINE-PK-SYS
\n","key":"X-Request-System","value":"ACA-ERP-SKY001"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-10T10:30:00.000Z"},{"key":"Accept","value":"application/json"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/quote-requests","description":"Requirement Reference: EQ.E1CGNR.1
\nUse Case: CGNR - Initiate Request for Shipment Quotation
\nDescription: Consignor creates shipment details in ACS for quote request. The consignor selects which ACAs (Air Cargo Agents) will receive the quote request. If consignor is using their own system, same information will be transferred to ACS via digital interface.
\nKey Activities:
\nConsignor creates shipment details for quote request
\nConsignor selects ACA(s) to receive the quote request (optional)
\nSystem allows partial shipment information save with timeout period
\nConsignor can advise ACA which airlines to exclude from quote
\nRequest Parameters:
\nDigital Information:
\nQuote ID (auto-generated)
\nShipping terms
\nPick-up address
\nDelivery address
\nOrigin airport code (3-letter IATA)
\nDestination airport code (3-letter IATA)
\nNumber of pieces
\nWeight with unit
\nDimensions (L x W x H)
\nCommodity description
\nDate for pick-up
\nACA selection (optional)
\nAirlines exclusion list (optional)
\nProcess Flow: E1CGNR → E1ACA
\nActors: Consignor, ACA
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n201 Created - Quote request created successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
422 Unprocessable Entity - Validation errors
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E1CGNR.1
\nUse Case: Consignor Contacts ACA System: CGNR - Reassign Submitted Request
\nDescription: Consignor reassigns an existing quote request from one ACA to another ACA, either keeping or deleting the previous assignment.
\nKey Activities:
\nConsignor reviews current quote request and assigned ACA
\nDecides to change ACA (better service, pricing, relationship, etc.)
\nSelects new ACA from available list
\nChooses whether to delete previous assignment or keep for reference
\nProvides reason for reassignment
\nSystem validates new ACA is different from current
\nSystem updates assignment and notifies all parties
\nPrevious ACA loses access if deletion requested
\nNew ACA receives request as pending
\nDigital Information:
\nQuote ID (from path parameter)
\nCurrent ACA (read-only):
\nACA ID
\nACA Name
\nNew ACA ID (required, must be different)
\nNew ACA Name (read-only after selection)
\nDelete Previous Assignment (boolean):
\ntrue - Previous ACA assignment removed completely
\nfalse - Previous ACA can still view but not act
\nReason (required) - Explanation for reassignment
\nReassigned by (captured automatically)
\nReassigned at (timestamp)
\nBusiness Rules:
\nOnly consignor can reassign their own requests
\nNew ACA must be different from current ACA
\nRequest must be in 'pending' or 'accepted' status
\nIf request already accepted, acceptance is revoked
\nReason is mandatory for audit trail
\nBoth ACAs are notified of the change
\nIf deletePreviousAssignment=true, previous ACA loses all access
\nIf deletePreviousAssignment=false, previous ACA retains read-only access
\nReassignment resets request status to 'pending'
\nProcess Flow: E1CGNR.1 → E2ACA.4 (new ACA)
\nActors: Consignor (initiator), Current ACA (notified), New ACA (recipient)
\nAuthentication: Required - OAuth 2.0 Bearer token (Consignor role)
\nResponse Codes:
\n201 Created - Reassignment successful
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not the consignor who created request)
404 Not Found - Quote request not found
409 Conflict - Request in wrong status for reassignment
422 Unprocessable Entity - Validation errors (same ACA, missing reason)
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E1CGNR.1
\nUse Case: Consignor Contacts ACA System: CGNR - Recall Submitted Request
\nDescription: Consignor recalls a submitted quote request before ACA has accepted or processed it, typically to make corrections or changes.
\nKey Activities:
\nConsignor identifies error or change needed in submitted request
\nRecalls the request before ACA commits to processing
\nProvides reason for recall
\nSystem validates request can be recalled (not yet accepted/processed)
\nStatus changes to 'recalled'
\nACA is notified of recall
\nRequest can be edited and resubmitted as new request
\nOriginal recalled request retained for audit
\nDigital Information:
\nQuote ID (from path parameter)
\nReason (required) - Explanation for recall
\nRecalled by (user ID, captured)
\nRecalled at (timestamp)
\nStatus change (pending → recalled)
\nBusiness Rules:
\nOnly consignor who created request can recall it
\nCan only recall requests in 'pending' status (before ACA acceptance)
\nCannot recall if ACA has already accepted and forwarded to airlines
\nReason is mandatory for audit trail
\nRecall is permanent - request cannot be un-recalled
\nACA must be notified immediately
\nRecalled requests are retained in system for history
\nConsignor can create new request with corrections
\nProcess Flow: E1CGNR.1 (recall action)
\nActors: Consignor (initiator), ACA (notified)
\nAuthentication: Required - OAuth 2.0 Bearer token (Consignor role)
\nResponse Codes:
\n201 Created - Recall successful
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not the consignor)
404 Not Found - Quote request not found
409 Conflict - Cannot recall (already accepted/processed)
422 Unprocessable Entity - Validation errors (missing reason)
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E1CGNR.1
\nUse Case: Consignor Contacts ACA System: CGNR - Recall Submitted Request
\nDescription: View history of all recalled quote requests that consignors pulled back before ACA acceptance, typically for corrections or modifications.
\nQuery Parameters:
\npage - Page number (default: 1)
limit - Items per page (default: 20, max: 100)
fromDate - Filter from date (ISO 8601)
toDate - Filter to date (ISO 8601)
consignorId - Filter by consignor
acaId - Filter by ACA
origin - Filter by origin city code
destination - Filter by destination city code
sort - Sort field (prefix with - for descending)
Process Flow: E1CGNR.1
\nActors: Consignor, ACA (read-only), System Administrator
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - Successfully retrieved list
401 Unauthorized - Missing or invalid authentication
500 Internal Server Error - Server-side error
Filter from date (ISO 8601)
\n","type":"text/plain"},"key":"fromDate","value":"2025-11-01"},{"description":{"content":"Filter to date (ISO 8601)
\n","type":"text/plain"},"key":"toDate","value":"2025-11-30"},{"description":{"content":"Filter by consignor
\n","type":"text/plain"},"key":"consignorId","value":"user-cgnr-789"},{"description":{"content":"Filter by ACA
\n","type":"text/plain"},"key":"acaId","value":"aca-12345"},{"description":{"content":"Filter by origin
\n","type":"text/plain"},"key":"origin","value":"KHI"},{"description":{"content":"Filter by destination
\n","type":"text/plain"},"key":"destination","value":"DXB"},{"description":{"content":"Sort by field (- for descending)
\n","type":"text/plain"},"key":"sort","value":"-recalledAt"}],"variable":[]}},"response":[{"id":"8e0538ec-f34b-4abc-83d9-1d603540e960","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E1CGNR.1
\nUse Case: Consignor Contacts ACA System: CGNR - View Shipment Quotation Request
\nDescription: Retrieve a paginated list of quote requests created by the authenticated consignor. Supports filtering by status, origin, destination, and date ranges.
\nQuery Parameters:
\npage (optional) - Page number, default: 1
limit (optional) - Items per page, default: 20, max: 100
sort (optional) - Sort field, prefix with - for descending (e.g., -createdAt)
status (optional) - Filter by status: pending, sent, cancelled
origin (optional) - Filter by origin airport code (3-letter IATA)
destination (optional) - Filter by destination airport code
createdAfter (optional) - ISO 8601 timestamp
createdBefore (optional) - ISO 8601 timestamp
Authentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - List retrieved successfully
401 Unauthorized - Missing or invalid authentication
500 Internal Server Error - Server-side error
Page number (default: 1)
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (default: 20, max: 100)
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-createdAt"},{"description":{"content":"Filter by status: pending, sent, cancelled
\n","type":"text/plain"},"key":"status","value":"pending"},{"description":{"content":"Filter by origin airport code
\n","type":"text/plain"},"key":"origin","value":"KHI"},{"description":{"content":"Filter by destination airport code
\n","type":"text/plain"},"key":"destination","value":"string"},{"description":{"content":"Filter by creation date (ISO 8601)
\n","type":"text/plain"},"key":"createdAfter","value":"string"},{"description":{"content":"Filter by creation date (ISO 8601)
\n","type":"text/plain"},"key":"createdBefore","value":"string"}],"variable":[]}},"response":[{"id":"8adb4273-befb-4652-813a-d42c0f8b3d87","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"0fdb49c4-b642-4894-95b4-829cb69613c4"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E1CGNR.1
\nUse Case: Consignor Contacts ACA System: CGNR - View Shipment Quotation Request
\nDescription: Retrieve detailed information about a specific quote request by its ID.
\nPath Parameters:
\nquoteId (required) - Unique identifier of the quote requestAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - Quote request details retrieved successfully
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to view this quote request
404 Not Found - Quote request not found
500 Internal Server Error - Server-side error
Quote request ID
\n","type":"text/plain"},"type":"any","value":"quote-abc123","key":"quoteId"}]}},"response":[{"id":"bd50f6db-0505-4016-9e96-da18016c56f1","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"62b3e6fb-ea13-4f00-9202-22ffc4415af7"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E1CGNR.1
\nUse Case: Consignor Contacts ACA System: CGNR - Cancel Submitted Request
\nDescription: Consignor cancels a quote request at any stage (pending, accepted, quoted) when shipment is no longer needed or requirements changed.
\nKey Activities:
\nConsignor determines quote request is no longer needed
\nInitiates cancellation with reason
\nSpecifies cancellation type (user requested, timeout, other)
\nSystem validates and processes cancellation
\nAll active RFQs to airlines are cancelled
\nAll involved parties (ACA, airlines) are notified
\nAny pending quotes are invalidated
\nRequest status changes to 'cancelled'
\nCancellation is logged for audit
\nDigital Information:
\nQuote ID (from path parameter)
\nReason (required) - Detailed explanation for cancellation
\nCancellation Type (required, enum):
\nuser_requested - User explicitly cancelled
\ntimeout - Request timed out without response
\nother - Other reason
\nCancelled by (user ID, captured)
\nCancelled at (timestamp)
\nStatus change (any → cancelled)
\nBusiness Rules:
\nOnly consignor who created request can cancel it
\nCan cancel at any stage before booking is finalized
\nCannot cancel if shipment booking is already confirmed
\nReason is mandatory for all cancellations
\nCancellation is permanent and cannot be undone
\nAll parties (ACA, airlines with pending RFQs) must be notified
\nAny quotes provided become invalid
\nCancellation fees may apply based on stage and timing
\nCancelled requests retained for historical analysis
\nProcess Flow: E1CGNR.1 (cancellation at any stage)
\nActors: Consignor (initiator), ACA (notified), Airlines (notified if RFQs pending)
\nAuthentication: Required - OAuth 2.0 Bearer token (Consignor role)
\nResponse Codes:
\n201 Created - Cancellation successful
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not the consignor)
404 Not Found - Quote request not found
409 Conflict - Cannot cancel (booking already confirmed)
422 Unprocessable Entity - Validation errors
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E2ACA.4, EQ.E3AL.7
\nUse Cases: Prepares Quotation for Consignor: ACA - Process Shipment Quotation Request, Airline System Informs Flight & Price Options: AL - Process Shipment Quotation Request
\nDescription: ACA accepts a quote request from consignor and forwards to selected airlines for RFQ, or Airline accepts an RFQ from ACA and commits to provide a quote.
\nKey Activities:
\nACA reviews incoming quote request from consignor
\nAccepts the request to handle the quotation process
\nSelects target airlines to send RFQ
\nOptionally prioritizes airlines
\nForwards request with any additional notes
\nSystem updates request status to 'accepted'
\nNotifications sent to consignor (confirmation) and airlines (RFQ)
\nFor Airline: accepts RFQ and commits to provide quote within timeframe
\nDigital Information:
\nQuote ID (from path parameter)
\nAccepted By (role: 'aca' or 'airline')
\nForward To (array, for ACA only):
\nAirline ID
\nAirline Name (read-only)
\nAirline Code (read-only)
\nPriority (optional, 1=highest)
\nNotes (optional)
\nAcceptance timestamp (generated)
\nStatus change (pending → accepted)
\nBusiness Rules:
\nOnly pending quote requests can be accepted
\nACA must forward to at least one airline
\nAirline can only accept if they received the RFQ
\nAcceptance creates RFQ records for each airline (ACA flow)
\nAcceptance commits airline to respond within configured timeframe
\nConsignor and relevant parties are notified
\nAcceptance cannot be undone (must use cancel/reject)
\nProcess Flow:
\nACA: E1CGNR.1 → E2ACA.4 → E3AL.7
\nAirline: E2ACA.4 → E3AL.7
\nActors: ACA (primary), Airline (alternative), Consignor (notified)
\nAuthentication: Required - OAuth 2.0 Bearer token (ACA or Airline role)
\nResponse Codes:
\n201 Created - Request accepted successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to accept this request
404 Not Found - Quote request not found
409 Conflict - Request already accepted or in wrong status
422 Unprocessable Entity - Validation errors
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E2ACA.4, EQ.E3AL.7
\nUse Cases: Prepares Quotation for Consignor: ACA - Process Shipment Quotation Request, Airline System Informs Flight & Price Options: AL - Process Shipment Quotation Request
\nDescription: ACA denies a quote request from consignor when unable or unwilling to handle, or Airline denies an RFQ from ACA when unable to provide competitive quote.
\nKey Activities:
\nACA or Airline reviews the request/RFQ
\nDetermines inability to fulfill (capacity, route, restrictions, etc.)
\nSelects denial reason from predefined list
\nProvides detailed notes explaining the denial
\nSystem updates status to 'denied'
\nRequestor is notified with reason
\nRequest/RFQ is closed and archived
\nDigital Information:
\nQuote ID (from path parameter)
\nReason (required, enum):
\ncapacity_unavailable - No capacity available
\nroute_not_serviced - Route not serviced
\ncommodity_restricted - Commodity restrictions apply
\npricing_not_competitive - Cannot provide competitive pricing
\noutside_service_area - Outside service coverage area
\ninsufficient_information - Insufficient information provided
\nother - Other reason (must provide notes)
\nNotes (required) - Detailed explanation
\nDenied by (user ID, captured automatically)
\nDenied at (timestamp, captured automatically)
\nBusiness Rules:
\nReason must be provided from allowed values
\nDetailed notes are mandatory for audit and customer service
\nDenial is final and cannot be undone
\nOriginal requestor must be notified
\nAlternative recommendations can be included in notes
\nDenied requests are retained for historical analysis
\nProcess Flow:
\nACA: E1CGNR.1 → E2ACA.4 (denied)
\nAirline: E2ACA.4 → E3AL.7 (denied)
\nActors: ACA (primary), Airline (alternative)
\nAuthentication: Required - OAuth 2.0 Bearer token (ACA or Airline role)
\nResponse Codes:
\n201 Created - Denial processed successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to deny this request
404 Not Found - Quote request not found
409 Conflict - Request in wrong status for denial
422 Unprocessable Entity - Validation errors (missing reason/notes)
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E1CGNR.1, EQ.E2ACA.4, EQ.E3AL.7
\nUse Cases: CGNR, ACA, AL - View Shipment Quotation Request
\nDescription: View complete chronological timeline of all actions, status changes, and events for a quote request from creation through completion or cancellation.
\nKey Activities:
\nRetrieve complete audit trail for quote request
\nDisplay all events in chronological order
\nShow actor information for each action
\nInclude status changes and transitions
\nTrack RFQ submissions and responses
\nLog quote submissions and approvals
\nRecord all modifications and updates
\nCapture system-generated events (timeouts, notifications)
\nProvide complete transparency for all stakeholders
\nDigital Information (per timeline event):
\nEvent ID
\nEvent Type (created, accepted, denied, forwarded, quoted, approved, etc.)
\nEvent Type Display (human-readable)
\nTimestamp
\nActor:
\nUser ID
\nUser Name
\nRole (consignor, aca, airline)
\nCompany/Organization
\nDescription (detailed event description)
\nStatus Change (if applicable):
\nPrevious Status
\nNew Status
\nAdditional Data (event-specific details):
\nAirlines forwarded to (for RFQ)
\nQuotes received
\nAmounts and pricing
\nReasons for actions
\nNotes and comments
\nSystem Event (boolean - true for automated events)
\nTimeline Event Types:
\nrequest_created - Initial quote request created
\nrequest_accepted - ACA accepted request
\nrequest_denied - ACA/Airline denied request
\nrfq_sent - RFQ forwarded to airlines
\nrfq_accepted - Airline accepted RFQ
\nrfq_denied - Airline denied RFQ
\nquote_received - Quote received from airline
\nproposal_created - ACA created price proposal
\nproposal_finalized - ACA finalized proposal
\nproposal_submitted - Proposal submitted to consignor
\nproposal_approved - Consignor approved proposal
\nproposal_rejected - Consignor rejected proposal
\nrequest_reassigned - Request reassigned to different ACA
\nrequest_recalled - Consignor recalled request
\nrequest_cancelled - Request cancelled
\nbooking_created - Booking created from approved quote
\nsystem_notification - Automated notification sent
\nsystem_timeout - Request/RFQ timed out
\nProcess Flow: All flows (E1CGNR.1 → E2ACA.4 → E3AL.7 → E4ACA.8 → E5CGNR.9)
\nActors: All (Consignor, ACA, Airline, System)
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - Successfully retrieved timeline
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to view this request
404 Not Found - Quote request not found
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E2AL.5
\nUse Case: Airline System Provides Schedule & Capacity Information
\nDescription: ACS allows ACA to use quote request information from Consignor to query flights in the routing that ACA chooses. ACS enables ACA to see multiple airline schedules on the same user screen. ACS enables ACA to exclude airlines from schedule query.
\nKey Activities:
\nQuery flight schedules for specific route and date
\nView multiple airline schedules simultaneously
\nFilter by specific airlines or exclude certain airlines
\nSupport for direct and transit routing
\nDigital Information:
\nOrigin airport code (3-letter IATA)
\nDestination airport code (3-letter IATA)
\nTransit point (optional)
\nDate for query
\nAirlines selection (optional - filter)
\nAirlines exclusion (optional - exclude list)
\nProcess Flow: E1ACA → E2ACA → E2AL
\nActors: ACA, Airline
\nData Source: For Airlines digitally integrated to ACS, ACS provides schedule information. For Airlines not integrated to ACS, ACS transfers information from other channels (email, business WhatsApp, etc.), subject to agreement with airline. Standard IATA SSIM (Standard Schedules Information Manual) format supported.
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - Flight schedules retrieved successfully
400 Bad Request - Invalid query parameters
401 Unauthorized - Missing or invalid authentication
404 Not Found - No flights found for criteria
500 Internal Server Error - Server-side error
Origin airport code (3-letter IATA) - Required
\n","type":"text/plain"},"key":"origin","value":"KHI"},{"description":{"content":"Destination airport code (3-letter IATA) - Required
\n","type":"text/plain"},"key":"destination","value":"DXB"},{"description":{"content":"Flight date (YYYY-MM-DD) - Required
\n","type":"text/plain"},"key":"date","value":"2025-11-05"},{"description":{"content":"Transit airport code (optional)
\n","type":"text/plain"},"key":"transitPoint","value":"string"},{"description":{"content":"Comma-separated airline codes to exclude
\n","type":"text/plain"},"key":"excludeAirlines","value":"QR,EY"},{"description":{"content":"Comma-separated airline codes to include (if specified, only these airlines will be shown)
\n","type":"text/plain"},"key":"includeAirlines","value":"string"}],"variable":[]}},"response":[{"id":"ad3a21f4-fac0-4a8a-84ff-45466950bd37","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"35034f6b-25b3-4e50-9767-40054f90705c"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E2AL.5
\nUse Case: Airline System Provides Schedule & Capacity Information
\nDescription: For Airlines that are digitally integrated to ACS, ACS provides schedule and capacity information. For Airlines that are not integrated to ACS, ACS will transfer information from other channels (e.g., email, business WhatsApp), subject to agreement with airline.
\nKey Activities:
\nQuery cargo capacity for specific flight and date
\nView projected or actual available cargo capacity
\nSupport for both integrated and non-integrated airlines
\nDigital Information:
\nFlight number
\nFlight date
\nAircraft type
\nCargo capacity (projected or actual) available per flight
\nOrigin and destination
\nProcess Flow: E2ACA → E2AL → E2ACA
\nActors: Airline, ACA
\nData Standards: IATA Standard Schedules Information Manual (SSIM)
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - Flight capacity retrieved successfully
400 Bad Request - Invalid query parameters
401 Unauthorized - Missing or invalid authentication
404 Not Found - Flight not found for criteria
500 Internal Server Error - Server-side error
Flight number (format: XX-NNN) - Required
\n","type":"text/plain"},"key":"flightNumber","value":"EK-602"},{"description":{"content":"Flight date (YYYY-MM-DD) - Required
\n","type":"text/plain"},"key":"date","value":"2025-11-05"},{"description":{"content":"Origin airport code
\n","type":"text/plain"},"key":"origin","value":"KHI"},{"description":{"content":"Destination airport code
\n","type":"text/plain"},"key":"destination","value":"DXB"}],"variable":[]}},"response":[{"id":"a20b5f35-ece4-487d-97eb-6422a3543796","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"d9c5e575-5cb6-4847-8432-1ecc67b595c0"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E3ACA.6
\nUse Case: Coordinates with Airline System for Space Availability: ACA - Initiate Request on behalf of Consignor
\nDescription: ACA will be able to select flights and airline for specific dates or date ranges for quotation by airlines. ACA can insert quote request from a consignor and create an RFQ, or combine quote requests from multiple consignors and create a combined RFQ. ACS will have functionality to connect with ACA systems if the stakeholders want to perform these functions in their software and transmit relevant data to ACS.
\nKey Activities:
\nCreate RFQ from consignor quote request
\nCombine multiple consignor quotes into single RFQ
\nRequest pricing for specific flight or flight range
\nInclude special cargo information
\nSpecify shipment stackability
\nDigital Information:
\nQuote request ID(s)
\nACA name, IATA code, CASS number
\nAirline name, prefix, two-letter code
\nOrigin & destination
\nNumber of pieces
\nWeight (actual & chargeable)
\nDimensions
\nCommodity
\nSpecial cargo information
\nShipment stackable or not
\nDate for delivery to airport
\nRequested flight(s) or date range
\nProcess Flow: E2AL → E3ACA → E3AL
\nActors: ACA, Airline
\nMessage Standard: JSON format or Cargo XML XRAF (use /airline-rfqs/xraf endpoint)
\nAuthentication: Required - OAuth 2.0 Bearer token (ACA role)
\nResponse Codes:
\n201 Created - RFQ created successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - User not authorized as ACA
422 Unprocessable Entity - Validation errors
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E3ACA.6
\nUse Case: Coordinates with Airline System for Space Availability: ACA - Initiate Request on behalf of Consignor
\nDescription: Same as JSON RFQ endpoint, but accepts IATA Cargo XML XRAF message format. This endpoint is for ACAs who want to send RFQ data in the standard Cargo XML format.
\nMessage Standard: IATA Cargo XML - XRAF (Request for Quote)
\nEDI Documentation: Refer to XRAF_v2-10 specification in EDI MCP
\nContent-Type: application/xml
\nProcess Flow: E2AL → E3ACA → E3AL
\nActors: ACA, Airline
\nAuthentication: Required - OAuth 2.0 Bearer token (ACA role)
\nResponse Codes:
\n201 Created - RFQ created successfully
400 Bad Request - Invalid XML structure
401 Unauthorized - Missing or invalid authentication
403 Forbidden - User not authorized as ACA
422 Unprocessable Entity - XML validation errors
500 Internal Server Error - Server-side error
Response Format: JSON (same as JSON RFQ endpoint)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["airline-rfqs","xraf"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"747a73a3-ccc5-4a96-99fa-a608c025c23a","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"960bd688-b353-4d32-adad-4a38c6e538c5"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E3ACA.6
\nUse Case: Coordinates with Airline System for Space Availability
\nDescription: Retrieve a paginated list of RFQs. ACAs can view RFQs they've sent, Airlines can view RFQs sent to them.
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - List retrieved successfully
401 Unauthorized - Missing or invalid authentication
500 Internal Server Error - Server-side error
Filter by status: draft, sent, quoted, cancelled
\n","type":"text/plain"},"key":"status","value":"sent"},{"key":"airlineCode","value":"EK"}],"variable":[]}},"response":[{"id":"38fd61d3-6c99-4f81-b9e1-82ec2a260ad5","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"807e95a2-41be-4c43-a67d-c7cdf8739bcc"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E3ACA.6
\nUse Case: Coordinates with Airline System for Space Availability
\nDescription: Retrieve detailed information about a specific RFQ.
\nPath Parameters:
\nrfqId (required) - Unique identifier of the RFQAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - RFQ details retrieved successfully
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to view this RFQ
404 Not Found - RFQ not found
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E3AL.7
\nUse Case: Airline System Informs Flight & Price Options
\nDescription: Update RFQ if shipment details change. ACS enables ACA to request a new quote if consignment details change. This can also trigger a new quote request to the airline.
\nKey Activities:
\nUpdate RFQ with changed shipment details
\nRequest new quote if conditions change
\nNotify airline of updated requirements
\nPath Parameters:
\nrfqId (required) - Unique identifier of the RFQAuthentication: Required - OAuth 2.0 Bearer token (ACA role)
\nResponse Codes:
\n200 OK - RFQ updated successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to update this RFQ
404 Not Found - RFQ not found
409 Conflict - RFQ cannot be updated in current state
422 Unprocessable Entity - Validation errors
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E3AL.7
\nUse Case: Airline System Informs Flight & Price Options: AL - Process Shipment Quotation Request
\nDescription: Airline will be able to reply ACA for the RFQ in following manner: Pricing for specific flight, Pricing for specific flight range, Pricing for any flight with validity, Request for additional information, Unable to quote message with a reason. ACS enables Airlines to exclude ACA from requesting quotes. ACS enables ACA and Airlines to request a new quote if RFQ conditions change. ACS enables ACA to activate quotes which have an expired validity date.
\nKey Activities:
\nProvide pricing for specific flight
\nProvide pricing for flight range
\nProvide pricing for any flight with validity
\nRequest additional shipment information
\nSend unable-to-quote message with reason
\nManage quote validity and reactivation
\nQuote Types:
\nspecific_flight - Quote for a specific flight number and date
flight_range - Quote valid for flights within a date range
any_flight_with_validity - Quote valid for any flight within validity period
unable_to_quote - Cannot provide quote (include reason)
additional_info_required - Need more information to quote
Digital Information:
\nRFQ ID (reference)
\nQuote ID (auto-generated)
\nACA & Airline details
\nOrigin & destination
\nShipment details (pieces, weight, dimensions, commodity)
\nFlight number or flight range
\nAir freight charge per kg
\nOther charges breakdown
\nTotal amount and currency
\nQuote validity period
\nProcess Flow: E3ACA → E3AL → E4ACA
\nActors: Airline, ACA
\nMessage Standard: JSON format or Cargo XML XRAF (use /airline-quotes/xraf endpoint)
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\nResponse Codes:
\n201 Created - Quote created successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - User not authorized as Airline
404 Not Found - RFQ not found
422 Unprocessable Entity - Validation errors
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E3AL.7
\nUse Case: Airline System Informs Flight & Price Options: AL - Process Shipment Quotation Request
\nDescription: Same as JSON airline quote endpoint, but accepts IATA Cargo XML XRAF response format. This endpoint is for Airlines who want to send quote data in the standard Cargo XML format.
\nMessage Standard: IATA Cargo XML - XRAF (Quote Response)
\nEDI Documentation: Refer to XRAF_v2-10 specification in EDI MCP
\nContent-Type: application/xml
\nProcess Flow: E3ACA → E3AL → E4ACA
\nActors: Airline, ACA
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\nResponse Codes:
\n201 Created - Quote created successfully
400 Bad Request - Invalid XML structure
401 Unauthorized - Missing or invalid authentication
403 Forbidden - User not authorized as Airline
422 Unprocessable Entity - XML validation errors
500 Internal Server Error - Server-side error
Response Format: JSON (same as JSON quote endpoint)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["airline-quotes","xraf"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"7d94f9b7-2ec3-4202-91f4-7da1f670d69c","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"522eaac9-27ab-44ee-bf38-31715e5a9d80"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E3AL.7
\nUse Case: Airline System Informs Flight & Price Options: AL - View Shipment Quotation Request
\nDescription: Retrieve a paginated list of airline quotes. Airlines can view quotes they've provided, ACAs can view quotes they've received.
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - List retrieved successfully
401 Unauthorized - Missing or invalid authentication
500 Internal Server Error - Server-side error
Filter by status: quoted, declined, expired, reactivated
\n","type":"text/plain"},"key":"status","value":"quoted"},{"description":{"content":"Filter by RFQ ID
\n","type":"text/plain"},"key":"rfqId","value":"rfq-xyz123"}],"variable":[]}},"response":[{"id":"a05a4e74-98f8-4942-88f7-3ddc1cb8fc9a","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"f5905e18-cb9e-4c46-a2ef-3bd72e244bf1"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E3AL.7
\nUse Case: Airline System Informs Flight & Price Options: AL - View Shipment Quotation Request
\nDescription: Retrieve detailed information about a specific airline quote.
\nPath Parameters:
\nquoteId (required) - Unique identifier of the quoteAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - Quote details retrieved successfully
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to view this quote
404 Not Found - Quote not found
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E3AL.7
\nUse Case: Airline System Informs Flight & Price Options
\nDescription: ACS enables ACA to activate quotes which have an expired validity date. The airline can choose to reactivate with same pricing or adjust pricing.
\nKey Activities:
\nReactivate expired quote
\nExtend validity period
\nOptional: Adjust pricing
\nNotify ACA of reactivation
\nPath Parameters:
\nquoteId (required) - Unique identifier of the expired quoteRequest Body:
\nnewValidityUntil (required) - New validity end date
reason (optional) - Reason for reactivation
pricingAdjustment (optional) - New pricing if adjusted
Authentication: Required - OAuth 2.0 Bearer token (Can be requested by ACA or approved by Airline)
\nResponse Codes:
\n200 OK - Quote reactivated successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to reactivate this quote
404 Not Found - Quote not found
409 Conflict - Quote is not expired or cannot be reactivated
422 Unprocessable Entity - Validation errors
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E4ACA.8
\nUse Case: ACA Confirms Consignor with Cost Estimate and Flight Details
\nProcess Flow: E3AL → E4ACA → E5CGNR
\nActors: ACA, Consignor
\nAuthentication: Required - OAuth 2.0 Bearer token (ACA role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["price-proposals"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"40c11b28-48e5-4d18-93d0-66cc62a5a0c3","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E4ACA.8
\nUse Case: ACA Confirms Consignor with Cost Estimate and Flight Details: ACA - Finalize Received Quotation
\nDescription: ACA performs final review of compiled quotation (with airline quotes, margins, terms) and finalizes it before submitting to consignor for approval.
\nKey Activities:
\nACA reviews all airline quotes received
\nVerifies pricing calculations and margins
\nConfirms routing and service levels
\nReviews all terms and conditions
\nMarks final review as completed
\nOptionally submits immediately to consignor or saves for later
\nSystem locks proposal from further editing once finalized
\nConsignor is notified if submitToConsignor=true
\nProposal status changes to 'finalized'
\nDigital Information:
\nProposal ID (from path parameter)
\nFinal Review Completed (boolean, required)
\nSubmit to Consignor (boolean):
\ntrue - Immediately submit to consignor after finalization
\nfalse - Finalize but hold for later submission
\nNotes (optional) - Final review notes and comments
\nFinalized by (user ID, captured)
\nFinalized at (timestamp)
\nStatus change (draft → finalized)
\nBusiness Rules:
\nOnly ACA who created the proposal can finalize it
\nProposal must be in 'draft' status
\nMust have at least one airline quote included
\nAll required fields (pricing, routing, terms) must be complete
\nOnce finalized, proposal cannot be edited (new version required)
\nIf submitToConsignor=true, consignor is notified immediately
\nIf submitToConsignor=false, ACA can submit manually later
\nFinalization locks the proposal for audit trail integrity
\nProcess Flow: E4ACA.8 → E5CGNR.9 (if submitted)
\nActors: ACA (initiator), Consignor (recipient if submitted)
\nAuthentication: Required - OAuth 2.0 Bearer token (ACA role)
\nResponse Codes:
\n201 Created - Finalization successful
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not the ACA who created proposal)
404 Not Found - Price proposal not found
409 Conflict - Proposal already finalized or in wrong status
422 Unprocessable Entity - Validation errors (incomplete proposal)
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E4ACA.8
\nUse Case: ACA Confirms Consignor with Cost Estimate and Flight Details: ACA - Finalize Received Quotation
\nDescription: View list of all finalized price proposals with filtering options for tracking and management purposes.
\nQuery Parameters:
\npage - Page number (default: 1)
limit - Items per page (default: 20, max: 100)
fromDate - Filter from date (ISO 8601)
toDate - Filter to date (ISO 8601)
acaId - Filter by ACA
consignorId - Filter by consignor
submitted - Filter by submission status (true/false)
airline - Filter by airline code
origin - Filter by origin city code
destination - Filter by destination city code
sort - Sort field (prefix with - for descending)
Process Flow: E4ACA.8
\nActors: ACA, Consignor (for their proposals), System Administrator
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - Successfully retrieved list
401 Unauthorized - Missing or invalid authentication
500 Internal Server Error - Server-side error
Filter from date (ISO 8601)
\n","type":"text/plain"},"key":"fromDate","value":"2025-11-01"},{"description":{"content":"Filter to date (ISO 8601)
\n","type":"text/plain"},"key":"toDate","value":"2025-11-30"},{"description":{"content":"Filter by ACA
\n","type":"text/plain"},"key":"acaId","value":"aca-12345"},{"description":{"content":"Filter by consignor
\n","type":"text/plain"},"key":"consignorId","value":"user-cgnr-789"},{"description":{"content":"Filter by submission status
\n","type":"text/plain"},"key":"submitted","value":"true"},{"description":{"content":"Filter by airline code
\n","type":"text/plain"},"key":"airline","value":"EK"},{"description":{"content":"Filter by origin
\n","type":"text/plain"},"key":"origin","value":"KHI"},{"description":{"content":"Filter by destination
\n","type":"text/plain"},"key":"destination","value":"DXB"},{"description":{"content":"Sort by field (- for descending)
\n","type":"text/plain"},"key":"sort","value":"-finalizedAt"}],"variable":[]}},"response":[{"id":"27971d05-e63b-454f-9df4-f14e6ba58520","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E5CGNR.9
\nUse Case: Consignor Approves ACA System Quote: CNGR - Accept/Reject Quotation
\nProcess Flow: E4ACA → E5CGNR → E6ACA
\nActors: Consignor, ACA
\nAuthentication: Required - OAuth 2.0 Bearer token (Consignor role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["price-proposals",":proposalId","approve"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"proposalId"}]}},"response":[{"id":"b60107cb-3c07-49d5-a56d-7550f9e97f64","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E5CGNR.9
\nUse Case: Consignor Approves ACA System Quote: CNGR - Accept/Reject Quotation
\nProcess Flow: E4ACA → E5CGNR → E6ACA
\nActors: Consignor, ACA
\nAuthentication: Required - OAuth 2.0 Bearer token (Consignor role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["price-proposals",":proposalId","reject"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"proposalId"}]}},"response":[],"_postman_id":"457ea717-1902-4eb6-b7e4-7afc8e6afcec"}],"id":"e9cf54b6-48d5-4313-83ec-214f1787b8f2","_postman_id":"e9cf54b6-48d5-4313-83ec-214f1787b8f2","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Shipment Bookings (ACA to Airline)","item":[{"name":"Create Shipment Booking (JSON)","id":"1e0c12d5-ca01-414b-9942-09d88fa853e4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/shipment-bookings","description":"Requirement Reference: EQ.E6ACA.10
\nUse Case: Creates Shipment Booking with the Airline System
\nProcess Flow: E5CGNR → E6ACA → E5AL
\nActors: ACA, Airline
\nMessage Standard: JSON, or use /shipment-bookings/xffr (XML) or /shipment-bookings/ffr (IMP)
\nAuthentication: Required - OAuth 2.0 Bearer token (ACA role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["shipment-bookings"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"13480599-0cf8-49c7-9327-ce33a8290912","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E6ACA.10
\nUse Case: Creates Shipment Booking with the Airline System
\nProcess Flow: E5CGNR → E6ACA → E5AL
\nActors: ACA, Airline
\nMessage Standard: IATA Cargo XML - XFFR (Freight Forwarder Request)
\nEDI Documentation: Refer to XFFR_v3-10 specification in EDI MCP
\nContent-Type: application/xml
\nResponse Format: JSON
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["shipment-bookings","xffr"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"bebf8609-f045-4b3a-b8fd-30a36c580dac"},{"name":"Create Shipment Booking (FFR IMP)","id":"df1a6839-7430-450c-be71-ff1045100e32","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/shipment-bookings/ffr","description":"Requirement Reference: EQ.E6ACA.10
\nUse Case: Creates Shipment Booking with the Airline System
\nProcess Flow: E5CGNR → E6ACA → E5AL
\nActors: ACA, Airline
\nMessage Standard: IATA Cargo IMP - FFR (Freight Forwarder Request)
\nContent-Type: text/plain
\nFormat: IATA Cargo IMP message format (string)
\nResponse Format: JSON
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["shipment-bookings","ffr"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"df1a6839-7430-450c-be71-ff1045100e32"}],"id":"95d68c36-7dc6-48b1-b38a-dfd5f9069851","_postman_id":"95d68c36-7dc6-48b1-b38a-dfd5f9069851","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Booking Responses (Airline to ACA)","item":[{"name":"Create Booking Response (JSON)","id":"a15a5557-5996-413b-adbb-bea0ac1ff6b3","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/booking-responses","description":"Requirement Reference: EQ.E6AL.11
\nUse Case: Airline System Accepts Shipment Booking
\nProcess Flow: E6ACA → E6AL → E7AL
\nActors: Airline, ACA
\nMessage Standard: JSON, or use /booking-responses/xffa (XML) or /booking-responses/ffa (IMP)
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["booking-responses"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"d02977f9-5b0e-406d-8fa6-e160be199b90","name":"Success - Accept","originalRequest":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"bookingId\": \"booking-bk1234\",\n \"responseType\": \"accept\",\n \"status\": \"confirmed\",\n \"awb\": \"176-12345678\",\n \"confirmedFlight\": {\n \"flightNumber\": \"EK-602\",\n \"flightDate\": \"2025-11-05\",\n \"departureTime\": \"2025-11-05T03:35:00+05:00\",\n \"arrivalTime\": \"2025-11-05T05:50:00+04:00\"\n },\n \"allocatedSpace\": {\n \"weight\": 500,\n \"volume\": 3.84,\n \"unit\": \"kg/m3\"\n },\n \"notes\": \"Booking confirmed - deliver cargo by 2025-11-04 20:00 UTC\"\n}"},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/booking-responses","description":"**Requirement Reference**: EQ.E6AL.11\n**Use Case**: Airline Accepts Shipment Booking\n**Process Flow**: E6ACA → E6AL → E7AL\n**Actors**: Airline, ACA\n**Message Standard**: JSON, or use /booking-responses/xffa (XML) or /booking-responses/ffa (IMP)\n**Authentication**: Required - OAuth 2.0 Bearer token (Airline role)"},"status":"Created","code":201,"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"response-rsp001\",\n \"bookingId\": \"booking-bk1234\",\n \"responseType\": \"accept\",\n \"status\": \"confirmed\",\n \"confirmedFlight\": {\n \"flightNumber\": \"EK-602\",\n \"flightDate\": \"2025-11-05\"\n },\n \"respondedAt\": \"2025-10-29T10:00:00Z\"\n }\n}"},{"id":"e6453bb3-a937-4805-8ae6-0a1e1e346197","name":"Success - Accept","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E6AL.11
\nUse Case: Airline System Accepts Shipment Booking
\nProcess Flow: E6ACA → E6AL → E7AL
\nActors: Airline, ACA
\nMessage Standard: IATA Cargo XML - XFFA (Freight Forwarder Answer)
\nEDI Documentation: Refer to XFFR_v3-10 specification (includes FFA response)
\nContent-Type: application/xml
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["booking-responses","xffa"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"11f04adb-c80e-4058-a875-2ad46a444411"},{"name":"Create Booking Response (FFA IMP)","id":"b59567a4-01cc-4468-a0e4-77f06ab47c97","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/booking-responses/ffa","description":"Requirement Reference: EQ.E6AL.11
\nUse Case: Airline System Accepts Shipment Booking
\nProcess Flow: E6ACA → E6AL → E7AL
\nActors: Airline, ACA
\nMessage Standard: IATA Cargo IMP - FFA (Freight Forwarder Answer)
\nEDI Documentation: Refer to XFFR_v3-10 specification (includes FFA response)
\nContent-Type: text/plain
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\nFormat: IATA Cargo IMP message format (string)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["booking-responses","ffa"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"b59567a4-01cc-4468-a0e4-77f06ab47c97"}],"id":"63fea324-a9a4-41cf-a744-76c6ea0ebd4e","_postman_id":"63fea324-a9a4-41cf-a744-76c6ea0ebd4e","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"7698ad84-b19e-41fc-b791-4e1d09ae8bee","_postman_id":"7698ad84-b19e-41fc-b791-4e1d09ae8bee","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Flight Schedule Management","item":[{"name":"Create Single Flight Schedule","id":"254b77dc-a973-4798-a01e-892afe3d5f06","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Request-ID","value":"36cb4e45-c2cb-483e-9d72-f68b08a214c7"},{"key":"Accept","value":"application/json"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/flight-schedules","description":"Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Upload Flight Schedule
\nDescription: Airline creates a single flight schedule with detailed routing, timing, capacity, and recurrence information. The schedule is made available to ACAs for booking cargo shipments.
\nKey Activities:
\nAirline specifies flight number, route, and timing
\nDefines aircraft type and available cargo capacity (weight and volume)
\nSets recurrence pattern (one-time, daily, weekly, custom days)
\nSpecifies validity period for recurring flights
\nDefines service type (passenger, cargo, mixed)
\nACAs can view and book against this schedule
\nSystem validates capacity against bookings
\nDigital Information:
\nFlight Number (required, format: XX-NNN, e.g., EK-602, PK-307)
\nOrigin Airport (required, 3-letter IATA code)
\nDestination Airport (required, 3-letter IATA code)
\nDeparture Datetime (required, ISO 8601 with timezone)
\nArrival Datetime (required, ISO 8601 with timezone)
\nAircraft Type (required, IATA aircraft code, e.g., B777-300ER, A350-900)
\nAvailable Capacity (required):
\nWeight (value and unit: kg or lb)
\nVolume (value and unit: m3 or ft3)
\nFrequency (optional: one-time, daily, weekly, monthly)
\nDays of Week (optional array for recurring: Monday-Sunday)
\nValid From (optional, start date for recurring schedules)
\nValid To (optional, end date for recurring schedules)
\nService Type (required: passenger, cargo, mixed)
\nStatus (required: active, cancelled, delayed, completed)
\nNotes (optional)
\nBusiness Rules:
\nFlight number must be unique for the airline per departure datetime
\nDeparture datetime must be in the future (when creating new schedules)
\nArrival datetime must be after departure datetime
\nFor recurring flights, validFrom and validTo are required
\nDays of week required if frequency is 'weekly'
\nAvailable capacity must be positive values
\nOrigin and destination must be different airports
\nAircraft type must be valid IATA code
\nProcess Flow: E1AL.3 → E1ACA.2 (schedule available for booking)
\nActors: Airline (creator), ACA (consumer)
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\nResponse Codes:
\n201 Created - Schedule created successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not airline role)
409 Conflict - Duplicate flight number/datetime combination
422 Unprocessable Entity - Validation errors (past date, invalid airports, etc.)
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Upload Flight Schedule
\nDescription: Airline uploads multiple flight schedules in bulk using standard industry formats (SSIM, CSV, XML). This allows efficient schedule management for airlines with large route networks.
\nKey Activities:
\nAirline prepares schedule file in supported format (SSIM, CSV, XML)
\nUploads file via multipart form data
\nSystem validates all records before processing
\nOption to validate-only without saving (dry run)
\nOption to overwrite existing schedules with same flight/date
\nSystem processes valid records and reports errors
\nReturns summary of success/failure counts
\nFailed records include detailed error messages
\nFile Formats Supported:
\n1. CSV Format:
Headers: FlightNumber,OriginAirport,DestinationAirport,DepartureDatetime,ArrivalDatetime,AircraftType,WeightCapacity,WeightUnit,VolumeCapacity,VolumeUnit,Frequency,DaysOfWeek,ValidFrom,ValidTo,ServiceType,Status,Notes
Example CSV:
\nFlightNumber,OriginAirport,DestinationAirport,DepartureDatetime,ArrivalDatetime,AircraftType,WeightCapacity,WeightUnit,VolumeCapacity,VolumeUnit,Frequency,DaysOfWeek,ValidFrom,ValidTo,ServiceType,Status,Notes\nEK-602,KHI,DXB,2025-11-25T02:15:00+05:00,2025-11-25T05:30:00+04:00,B777-300ER,15000,kg,120,m3,daily,\"Mon,Tue,Wed,Thu,Fri,Sat,Sun\",2025-11-25,2026-03-28,mixed,active,\"Daily service\"\nEK-604,KHI,DXB,2025-11-25T14:30:00+05:00,2025-11-25T17:45:00+04:00,B777-200LR,12000,kg,100,m3,daily,\"Mon,Tue,Wed,Thu,Fri,Sat,Sun\",2025-11-25,2026-03-28,mixed,active,\"Afternoon service\"\nPK-307,KHI,LHR,2025-11-26T03:00:00+05:00,2025-11-26T07:30:00+00:00,B777-300ER,18000,kg,150,m3,weekly,\"Mon,Wed,Fri\",2025-11-26,2026-03-28,mixed,active,\"Three times weekly\"\n\n2. SSIM Format (Standard Schedules Information Manual - IATA standard):
Industry-standard format used by airlines for schedule distribution. The system parses SSIM records and extracts relevant cargo capacity information.
3. XML Format:
Structured XML following airline schedule schema with flight, route, timing, and capacity elements.
Request Parameters:
\nfile (required, multipart file): Schedule file to upload
fileFormat (required, enum: csv, xml, ssim): File format type
validateOnly (optional, boolean, default: false): If true, validates without saving
overwriteExisting (optional, boolean, default: false): If true, overwrites existing schedules
Response Structure:
\nTotal Records: Total number of records in file
\nSuccess Count: Number of successfully processed schedules
\nFailure Count: Number of failed validations
\nErrors: Array of validation errors with line numbers and details
\nCreated Schedules: Array of created schedule IDs (if not validateOnly)
\nBusiness Rules:
\nFile must be valid format (CSV, XML, or SSIM)
\nAll required fields must be present for each record
\nEach record validated independently
\nInvalid records are skipped, valid records are processed
\nIf validateOnly=true, no records are saved to database
\nIf overwriteExisting=true, matching schedules are updated
\nIf overwriteExisting=false, duplicates are reported as errors
\nMaximum file size: 50MB
\nMaximum records per upload: 10,000
\nProcess Flow: E1AL.3 → Batch Processing → E1ACA.2 (schedules available)
\nActors: Airline (uploader), System (processor), ACA (consumer)
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\nResponse Codes:
\n201 Created - Upload processed successfully (full or partial success)
400 Bad Request - Invalid file format or missing required parameters
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not airline role)
413 Payload Too Large - File exceeds maximum size
422 Unprocessable Entity - All records failed validation
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Upload Flight Schedule
\nDescription: Airline updates an existing flight schedule due to operational changes, aircraft swaps, timing adjustments, or cancellations. ACAs with bookings on affected flights are automatically notified of significant changes.
\nKey Activities:
\nAirline selects flight schedule to update
\nModifies timing, aircraft type, capacity, or status
\nProvides mandatory reason for audit trail
\nChooses whether to notify ACAs with existing bookings
\nSystem validates changes (e.g., capacity vs existing bookings)
\nIf capacity reduced, system checks if existing bookings can be accommodated
\nACAs are notified if affectBookings=true and changes are significant
\nUpdate logged in audit trail with reason and timestamp
\nUpdatable Fields:
\nFlight Number
\nOrigin Airport (with validation)
\nDestination Airport (with validation)
\nDeparture Datetime
\nArrival Datetime
\nAircraft Type
\nAvailable Capacity (weight and volume)
\nFrequency
\nDays of Week
\nValid From
\nValid To
\nService Type
\nStatus (active, cancelled, delayed, completed)
\nNotes
\nRequired Additional Fields:
\nUpdate Reason (required, for audit trail)
\nAffect Bookings (required, boolean - whether to notify ACAs)
\nBusiness Rules:
\nCannot update schedules for flights that have already departed (status=completed)
\nUpdate reason must be provided for audit compliance
\nIf capacity is reduced, must not fall below currently booked capacity
\nIf departure time changed by >2 hours, ACAs must be notified
\nIf flight cancelled (status=cancelled), all ACAs with bookings must be notified
\nIf aircraft type changed, capacity must be recalculated
\nArrival datetime must be after departure datetime
\nFor recurring schedules, update applies to future instances only
\nNotification Triggers (when affectBookings=true):
\nDeparture time changed by >2 hours
\nArrival time changed by >2 hours
\nCapacity reduced
\nFlight cancelled
\nRoute changed (origin or destination)
\nAircraft type changed
\nProcess Flow: E1AL.3 → E1ACA.2 (notification if applicable)
\nActors: Airline (updater), ACA (notified party)
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\nResponse Codes:
\n200 OK - Schedule updated successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not airline or wrong airline)
404 Not Found - Schedule not found
409 Conflict - Update conflicts with existing bookings or business rules
422 Unprocessable Entity - Validation errors (past flight, capacity conflict, etc.)
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Process Shipment Booking (Offer Alternate)
\nDescription: When airline cannot fulfill the original booking request (due to capacity, flight cancellation, weight restrictions, or route changes), they can offer one or multiple alternate booking options to the ACA. This allows the ACA to select from available alternatives rather than having the booking simply rejected.
\nKey Activities:
\nAirline rejects original booking with specific reason
\nProvides detailed explanation for rejection
\nOffers one or multiple alternate flight options
\nEach alternate includes flight details, capacity, pricing, and timing
\nSpecifies validity period for alternate offers
\nSets priority level for urgency
\nSystem auto-generates unique IDs for each alternate
\nACA is notified of alternate proposals
\nAll parties can track alternate status
\nDigital Information:
\nResponse ID (from path parameter - references original booking response)
\nOriginal Booking ID (read-only, system populated)
\nRejection Reason (enum):
\ncapacity_full - Flight at full capacity
\nflight_cancelled - Scheduled flight cancelled
\nweight_restriction - Cargo exceeds weight limits
\nroute_unavailable - Route not serviced
\nother - Other reasons (specify in details)
\nReason Details (text explanation)
\nAlternate Options (array, can have multiple):
\nAlternate ID (auto-generated by system)
\nFlight Number
\nDeparture Date (YYYY-MM-DD)
\nDeparture Datetime (ISO 8601 with timezone)
\nArrival Datetime (ISO 8601 with timezone)
\nAircraft Type
\nAvailable Capacity:
\nWeight (value and unit)
\nVolume (value and unit)
\nRoute Details:
\nOrigin (IATA code)
\nOrigin Name
\nDestination (IATA code)
\nDestination Name
\nStops (array of intermediate airports)
\nPricing Difference:
\nAmount (positive for increase, negative for decrease)
\nCurrency (ISO 4217)
\nChange Type (increase, decrease, same)
\nTransit Time (in hours, decimal)
\nNotes (additional information)
\nValid Until (datetime - when these alternates expire)
\nPriority Level (urgent, normal, low)
\nBusiness Rules:
\nCan only offer alternates for pending or rejected booking responses
\nMust provide at least one alternate option
\nCan provide up to 5 alternate options
\nEach alternate must have unique flight/date combination
\nAll alternates automatically expire at validUntil datetime
\nOriginal booking is marked as \"rejected with alternates\"
\nACA must be notified immediately via email and system notification
\nPricing difference must be clearly indicated
\nTransit time must be calculated accurately
\nRoute must match origin and destination of original booking
\nSystem validates flight numbers and aircraft types
\nCannot offer alternates if booking already accepted
\nNotification Logic:
\nACA receives immediate notification with all alternate details
\nNotification includes comparison table of alternates
\nEmail notification includes direct links to accept alternates
\nSystem notification remains visible until alternate accepted/expired
\nConsignor is notified if they initiated the original quote
\nProcess Flow: E1AL.3 → E1ACA (notification) → E1ACA (acceptance)
\nActors: Airline (initiator), ACA (recipient/decision maker)
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\nResponse Codes:
\n201 Created - Alternate proposals created successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not airline or wrong airline)
404 Not Found - Booking response not found
409 Conflict - Booking already accepted or alternates already offered
422 Unprocessable Entity - Validation errors (e.g., invalid flight number, past date)
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Process Shipment Booking (View Alternates)
\nDescription: List all alternate booking options offered for a specific booking response. Shows current status of each alternate, including which (if any) has been accepted. Allows both airline and ACA to view all alternate proposals and their statuses.
\nKey Activities:
\nRetrieve all alternate options for a booking response
\nFilter by status (pending, accepted, rejected, expired)
\nView which alternate was accepted (if any)
\nCheck expiry status of pending alternates
\nCompare alternate options side-by-side
\nTrack acceptance/rejection timestamps
\nDigital Information:
\nAlternate Group ID
\nBooking Response ID
\nOriginal Booking Details (flight, date, route)
\nRejection Reason and Details
\nList of Alternates:
\nAlternate ID
\nFlight Number
\nDeparture/Arrival Datetimes
\nAircraft Type
\nAvailable Capacity
\nRoute Details
\nPricing Difference
\nTransit Time
\nStatus (pending, accepted, rejected, expired)
\nAccepted By (if accepted)
\nAccepted At (if accepted)
\nValid Until
\nPriority Level
\nOverall Status
\nCreation/Update Timestamps
\nQuery Parameters:
\nstatus - Filter by alternate status (pending, accepted, rejected, expired)
sort - Sort field (createdAt, departureDate, pricingDifference.amount)
Business Rules:
\nReturns all alternates for the specified booking response
\nAutomatically marks alternates as expired if past validUntil
\nShows which alternate was accepted (only one can be accepted)
\nAll other alternates auto-rejected when one is accepted
\nACA can only see alternates for their own bookings
\nAirline can see all alternates for their flights
\nProcess Flow: E1AL.3, E1ACA.2
\nActors: Airline, ACA
\nAuthentication: Required - OAuth 2.0 Bearer token
\nResponse Codes:
\n200 OK - Successfully retrieved alternates
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized to view this booking response
404 Not Found - Booking response not found
500 Internal Server Error - Server-side error
Filter by status (pending, accepted, rejected, expired)
\n","type":"text/plain"},"key":"status","value":"pending"},{"description":{"content":"Sort by field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-createdAt"}],"variable":[{"type":"any","value":"resp-abc123","key":"responseId"}]}},"response":[{"id":"a7213eb5-78e8-4e4f-8196-9c4aee8f9eed","name":"Success Response - With Accepted Alternate","originalRequest":{"method":"GET","header":[],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/booking-responses/resp-abc123/alternates"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json"}],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"alt-group-xyz789\",\n \"bookingResponseId\": \"resp-abc123\",\n \"originalBooking\": {\n \"bookingId\": \"booking-abc123\",\n \"flightNumber\": \"EK-602\",\n \"departureDate\": \"2025-11-20\",\n \"departureDatetime\": \"2025-11-20T02:15:00+05:00\",\n \"route\": \"KHI-DXB\",\n \"status\": \"alternate_accepted\"\n },\n \"rejectionReason\": \"capacity_full\",\n \"rejectionReasonDisplay\": \"Flight at Full Capacity\",\n \"reasonDetails\": \"EK-602 flight on 2025-11-20 is at full capacity for the requested cargo dimensions. Offering alternate flights with available capacity.\",\n \"alternateOptions\": [\n {\n \"alternateId\": \"alt-xyz789-01\",\n \"flightNumber\": \"EK-604\",\n \"departureDate\": \"2025-11-20\",\n \"departureDatetime\": \"2025-11-20T06:15:00+05:00\",\n \"arrivalDatetime\": \"2025-11-20T09:30:00+04:00\",\n \"aircraftType\": \"B777-300ER\",\n \"availableCapacity\": {\n \"weight\": {\n \"value\": 2500,\n \"unit\": \"kg\"\n },\n \"volume\": {\n \"value\": 15,\n \"unit\": \"m3\"\n }\n },\n \"routeDetails\": {\n \"origin\": \"KHI\",\n \"originName\": \"Jinnah International Airport\",\n \"destination\": \"DXB\",\n \"destinationName\": \"Dubai International Airport\",\n \"stops\": []\n },\n \"pricingDifference\": {\n \"amount\": 0,\n \"currency\": \"USD\",\n \"changeType\": \"same\"\n },\n \"transitTime\": 3.25,\n \"notes\": \"Next available flight same day, 4 hours later than originally requested. Direct flight with ample capacity.\",\n \"status\": \"accepted\",\n \"acceptedBy\": \"user-aca-123\",\n \"acceptedByName\": \"Mike Johnson\",\n \"acceptedAt\": \"2025-11-19T12:15:00Z\",\n \"timeDifferenceFromOriginal\": {\n \"hours\": 4,\n \"direction\": \"later\"\n }\n },\n {\n \"alternateId\": \"alt-xyz789-02\",\n \"flightNumber\": \"EK-606\",\n \"departureDate\": \"2025-11-21\",\n \"departureDatetime\": \"2025-11-21T02:15:00+05:00\",\n \"arrivalDatetime\": \"2025-11-21T05:30:00+04:00\",\n \"aircraftType\": \"A380-800\",\n \"availableCapacity\": {\n \"weight\": {\n \"value\": 5000,\n \"unit\": \"kg\"\n },\n \"volume\": {\n \"value\": 30,\n \"unit\": \"m3\"\n }\n },\n \"routeDetails\": {\n \"origin\": \"KHI\",\n \"originName\": \"Jinnah International Airport\",\n \"destination\": \"DXB\",\n \"destinationName\": \"Dubai International Airport\",\n \"stops\": []\n },\n \"pricingDifference\": {\n \"amount\": -50,\n \"currency\": \"USD\",\n \"changeType\": \"decrease\"\n },\n \"transitTime\": 3.25,\n \"notes\": \"Next day morning flight with reduced rate due to delay. A380 aircraft with significant available capacity.\",\n \"status\": \"auto_rejected\",\n \"autoRejectedAt\": \"2025-11-19T12:15:00Z\",\n \"autoRejectedReason\": \"Another alternate was accepted\",\n \"timeDifferenceFromOriginal\": {\n \"hours\": 24,\n \"direction\": \"later\"\n }\n }\n ],\n \"validUntil\": \"2025-11-20T18:00:00+05:00\",\n \"priorityLevel\": \"urgent\",\n \"status\": \"accepted\",\n \"totalAlternates\": 2,\n \"acceptedAlternate\": \"alt-xyz789-01\",\n \"acceptedAt\": \"2025-11-19T12:15:00Z\",\n \"createdBy\": \"user-airline-123\",\n \"createdByName\": \"John Smith\",\n \"createdAt\": \"2025-11-19T10:30:00Z\",\n \"updatedAt\": \"2025-11-19T12:15:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-19T14:00:00Z\",\n \"requestId\": \"req-123474\"\n }\n}"},{"id":"352af3a7-871e-45a2-80c5-26fb8ee6917f","name":"Success Response - Pending Alternates","originalRequest":{"method":"GET","header":[],"url":{"raw":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/booking-responses/resp-def456/alternates?status=pending","host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"path":["booking-responses","resp-def456","alternates"],"query":[{"key":"status","value":"pending"}]}},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json"}],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"alt-group-def456\",\n \"bookingResponseId\": \"resp-def456\",\n \"originalBooking\": {\n \"bookingId\": \"booking-def456\",\n \"flightNumber\": \"EK-602\",\n \"departureDate\": \"2025-11-21\",\n \"route\": \"KHI-LHR\",\n \"status\": \"rejected_with_alternates\"\n },\n \"rejectionReason\": \"route_unavailable\",\n \"rejectionReasonDisplay\": \"Route Not Available\",\n \"reasonDetails\": \"Direct KHI-LHR route temporarily unavailable. Offering one-stop alternatives.\",\n \"alternateOptions\": [\n {\n \"alternateId\": \"alt-def456-01\",\n \"flightNumber\": \"EK-604/EK-008\",\n \"departureDate\": \"2025-11-21\",\n \"departureDatetime\": \"2025-11-21T06:15:00+05:00\",\n \"arrivalDatetime\": \"2025-11-21T15:45:00+00:00\",\n \"aircraftType\": \"B777-300ER/A380-800\",\n \"availableCapacity\": {\n \"weight\": {\n \"value\": 1500,\n \"unit\": \"kg\"\n },\n \"volume\": {\n \"value\": 10,\n \"unit\": \"m3\"\n }\n },\n \"routeDetails\": {\n \"origin\": \"KHI\",\n \"originName\": \"Jinnah International Airport\",\n \"destination\": \"LHR\",\n \"destinationName\": \"London Heathrow\",\n \"stops\": [\n {\n \"airport\": \"DXB\",\n \"airportName\": \"Dubai International Airport\",\n \"layoverDuration\": 2.5\n }\n ]\n },\n \"pricingDifference\": {\n \"amount\": 75,\n \"currency\": \"USD\",\n \"changeType\": \"increase\"\n },\n \"transitTime\": 9.5,\n \"notes\": \"One-stop via Dubai with 2.5 hour layover. Additional charge for connection.\",\n \"status\": \"pending\",\n \"isExpiringSoon\": true,\n \"hoursUntilExpiry\": 4\n }\n ],\n \"validUntil\": \"2025-11-19T18:00:00+05:00\",\n \"priorityLevel\": \"normal\",\n \"status\": \"pending\",\n \"totalAlternates\": 1,\n \"createdBy\": \"user-airline-456\",\n \"createdByName\": \"Sarah Williams\",\n \"createdAt\": \"2025-11-19T11:00:00Z\",\n \"updatedAt\": \"2025-11-19T11:00:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-19T14:00:00Z\",\n \"requestId\": \"req-123475\"\n }\n}"},{"id":"325920bf-4573-4177-9590-535980896cb4","name":"Success Response - With Accepted Alternate","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E1AL.3
\nUse Case: AL - Process Shipment Booking (Accept Alternate)
\nDescription: ACA accepts one of the alternate booking options offered by the airline. Upon acceptance, the original booking is updated with the new flight details, all other alternates are automatically rejected, and all relevant parties are notified.
\nKey Activities:
\nACA selects and accepts one alternate from available options
\nProvides acceptance notes (optional but recommended)
\nIndicates if shipment details need updating
\nSystem validates alternate is still valid (not expired)
\nSystem validates alternate is still available (status = pending)
\nSystem updates original booking with new flight details
\nSystem auto-rejects all other alternates
\nSystem sends notifications to:
\nAirline (alternate accepted)
\nConsignor (booking confirmed with new flight)
\nGround handling (if applicable)
\nSystem updates booking status to 'confirmed'
\nIf updateShipmentDetails=true, allows subsequent updates to shipment
\nDigital Information:
\nResponse ID (from path parameter)
\nAlternate ID (from path parameter)
\nAcceptance Notes (optional text)
\nUpdate Shipment Details (boolean):
\ntrue - Allows updating shipment details to match new flight
\nfalse - Keeps original shipment details as-is
\nBusiness Rules:
\nCan only accept pending alternates
\nCannot accept if alternate has expired
\nCannot accept if already expired (past validUntil)
\nOnly one alternate can be accepted per booking
\nAccepting one alternate auto-rejects all others
\nOriginal booking is updated with new flight information
\nAll parties must be notified immediately
\nACA must have authorization for this booking
\nFlight capacity is reserved upon acceptance
\nPricing from the alternate is applied to the booking
\nIf pricing difference exists, invoice is updated
\nAcceptance cannot be undone (final action)
\nNotification Logic:
\nAirline: Notified that alternate was accepted, which alternate, by whom, when
\nConsignor: Notified booking confirmed with new flight details, any pricing changes
\nACA Team: Internal notification of acceptance
\nGround Handling: Notified of new flight details (if booking includes GHA)
\nSystem: Updates all related records (quote, shipment, AWB if issued)
\nCascading Updates:
When alternate is accepted:
Original booking updated with new flight number, dates, aircraft type
\nQuote updated with pricing difference (if any)
\nShipment details updated (if updateShipmentDetails=true)
\nAll other alternates marked as 'auto_rejected'
\nAlternate group status changed to 'accepted'
\nBooking status changed to 'confirmed'
\nFlight capacity decremented
\nTimeline/audit trail updated
\nProcess Flow: E1ACA (acceptance) → E1AL (notification) → E1CGNR (notification)
\nActors: ACA (initiator), Airline (notified), Consignor (notified)
\nAuthentication: Required - OAuth 2.0 Bearer token (ACA role)
\nResponse Codes:
\n200 OK - Alternate accepted successfully
400 Bad Request - Invalid request data
401 Unauthorized - Missing or invalid authentication
403 Forbidden - Not authorized (not ACA or wrong ACA)
404 Not Found - Booking response or alternate not found
409 Conflict - Alternate expired or already accepted
422 Unprocessable Entity - Validation errors
500 Internal Server Error - Server-side error
Requirement Reference: EQ.E2CGNR.12
\nUse Case: Consignor sends request item to EPO
\nProcess Flow: E2CGNR → E2EPO
\nActors: Consignor, EPO
\nAuthentication: Required - OAuth 2.0 Bearer token (Consignor role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["epo-quote-requests"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"970e05f1-d054-4f0d-b8fc-fefcd63f2872","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E2EPO.13
\nUse Case: Item Request Received
\nKey Features: Different service levels, pricing for each item, different pricing for each consignor
\nProcess Flow: E2CGNR → E2EPO → E2CGNR
\nActors: EPO, Consignor
\nAuthentication: Required - OAuth 2.0 Bearer token (EPO role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["epo-quotes"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"323cb970-e38b-4546-a1cc-3f6c3ac5a1b9","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E1EPO.14
\nUse Case: When preassigned AWB stock is depleted or for first-time use, the EPO requests new stock.
\nProcess Flow: E1EPO → E1AL
\nActors: EPO, Airline
\nAuthentication: Required - OAuth 2.0 Bearer token (EPO role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["epo-awb-requests"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"45dccff0-75e2-4bc6-9561-b6c648d1de70","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E1AL.15
\nUse Case: AWB Stock Allocation
\nProcess Flow: E1EPO → E1AL → E1EPO
\nActors: Airline, EPO
\nAuthentication: Required - OAuth 2.0 Bearer token (Airline role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["epo-awb-allocations"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"081fd74b-10a7-4c08-ac97-c5c73b83788f"}],"id":"b4ef7c7b-9b21-47a6-896b-d44742eeb702","_postman_id":"b4ef7c7b-9b21-47a6-896b-d44742eeb702","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"HAWB Management","item":[{"name":"Create HAWB","id":"dba17a6b-db75-481d-8527-dabbfba1459e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/hawbs","description":"Requirement Reference: EQ.E2EPO.17
\nUse Case: Consignor Receives HAWB from EPO (HAWB Creation)
\nProcess Flow: E2CGNR → E2EPO → E3CGNR
\nActors: EPO, Consignor
\nAuthentication: Required - OAuth 2.0 Bearer token (EPO role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawbs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"e06974dd-b753-46b8-8587-8c32b2229aab","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E3CGNR.17
\nUse Case: Consignor Receives HAWB from EPO
\nProcess Flow: E2EPO → E3CGNR → E4EPO
\nActors: Consignor, EPO
\nAuthentication: Required - OAuth 2.0 Bearer token (Consignor role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawbs",":hawbId","confirm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"hawbId"}]}},"response":[{"id":"cff07c76-f534-4abf-98a8-7937b433ddfb","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EQ.E3CGNR.17
\nUse Case: Consignor Receives HAWB from EPO
\nActors: Consignor, EPO
\nAuthentication: Required - OAuth 2.0 Bearer token (Consignor role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawbs",":hawbId","request-correction"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"hawbId"}]}},"response":[{"id":"651582b4-47e0-4f2e-bbec-54450bc4dd26","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerUnique identifier for request tracing
\n","key":"X-Request-ID","value":"99b69c30-783f-438a-8032-c97e6f1da5a4"},{"description":"Identifier of the system making the request (POST, ANF, CUSTOMS, GHA)
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.798Z"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"airlinePrefix\": \"176\",\n \"startingAWBNumber\": \"176-12345678\",\n \"endingAWBNumber\": \"176-12346767\",\n \"additionalNotes\": \"Test AWB Range\",\n \"range\": \"176-12345678-176-12346767\",\n \"totalAWB\": \"90\"\n}","options":{"raw":{"headerFamily":"json","language":"json"}}},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/awb","description":"Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Create AWB Stock
\nIntegration Point: Airline pushes pre-defined AWB stocks
\nProcess Flow: Airline System → Airport Community System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["awb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"b6326ae1-464e-4ee0-b0af-3ce5ebb043ce"},{"name":"Allocate AWB Stock","id":"58a67553-0638-4b69-b238-f59b0ac5d547","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/","description":"Requirement Reference: EQ.E1AL.3
\nUse Case: AL - Process AWB Stock Acquisition Request / Allocate AWB Stock
\nIntegration Point: Stock allocation processing
\nProcess Flow: Airline System → Airport Community System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":[""],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"58a67553-0638-4b69-b238-f59b0ac5d547"},{"name":"Delete Unallocated AWB Stocks","id":"e25ff1b4-9259-4ac8-991d-fe41c450a34c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"DELETE","header":[],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":[""],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"e25ff1b4-9259-4ac8-991d-fe41c450a34c"}],"id":"507b908a-d44c-473e-98f4-6b14a03ef812","_postman_id":"507b908a-d44c-473e-98f4-6b14a03ef812","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"a5645916-c1ec-4a8c-9784-04ba14d64214","_postman_id":"a5645916-c1ec-4a8c-9784-04ba14d64214","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"e-Ops module","item":[{"name":"Import & GHA Operations","item":[{"name":"Flight Data & Documents","item":[{"name":"ACI","item":[{"name":"Receive ACI (Advance Cargo Information)","id":"2c33c908-5a84-44c7-9a33-b7f5d1c09966","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"7cb919c7-c640-4254-85d2-ad162927e202"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests","description":"Global API References:
\n\nRequirement References:
\nEO.I4AL.1
\nG.I4AL.1
\nEO.I4GHA.2
\nEO.I4CUS.3
\nG.I4GHA.2
\nG.I4CUS.4
\nEO.I5PSW.5
\nUse Cases:
\nSend Advance Cargo Information (ACI) to ACS
\nReceive Advance Cargo Information from ACS
\nDescription: Airline system sends Flight Manifest (FFM), Master Air Waybills (FWB), and House Air Waybills (FHL) to ACS via API.
\nProcess Flow: Airline System→ Airport Community System → GHA System
\nPriority: P1
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"2c33c908-5a84-44c7-9a33-b7f5d1c09966"}],"id":"0d1e5a9b-abf5-4e0e-b3b8-bb57e0e6a58a","_postman_id":"0d1e5a9b-abf5-4e0e-b3b8-bb57e0e6a58a","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Mail Manifest","item":[{"name":"Receive Mail Manifest","id":"630a300b-41a9-431d-8fcf-e4567065a9c1","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"e5ceceae-43ee-4e8a-aa24-d00efe84e044"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.799Z"}],"url":"","description":"Global API References:
\nRequirement References:
\nEO.I4GHA.2
\nEO.I4P.4
\nEO.I5PAA.6
\nG.I4P.3
\nUse Case: View Mail Manifest in ACS
\nDescription: ACS displays Mail Manifest received from Airlines to authorized entities.
\nProcess Flows:
\nAirport Community System → Airline System
\nAirport Community System → GHA System
\nAirport Community System → Postal Aviation Authority
\nAirport Community System → Pakistan Post
\nPriority: P2
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"query":[],"variable":[]}},"response":[],"_postman_id":"630a300b-41a9-431d-8fcf-e4567065a9c1"}],"id":"28fcb42d-dfa7-4158-87b3-f6394f3c5b28","_postman_id":"28fcb42d-dfa7-4158-87b3-f6394f3c5b28","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"754e1d7f-eed4-4c10-a2d8-59e81c310610","_postman_id":"754e1d7f-eed4-4c10-a2d8-59e81c310610","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Arrival & Customs","item":[{"name":"Cargo Arrival & Documents","item":[{"name":"Submit Cargo Arrival Information","id":"e5b41d96-1678-451d-b741-3cb67cde5edf","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{access_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/cargo-arrivals","description":"Global API Reference:
\n\nRequirement References:
\nEO.I10CUS.15
\nEO.I10CNE.16
\nEO.I10AL.17
\nEO.I10ACA.18
\nEO.I10CB.19
\nEO.I10CGNR.20
\nG.I10CNE.11
\nG.I10ACA.12
\nG.I10AL.13
\nG.I10CB.14
\nG.I10CUS.15
\nUse Cases:
\nReceive Cargo Arrival Information from ACS
\nView Cargo Arrival Information in ACS
\nView Cargo Arrival Information in PSW
\nDescription: ACS pushes Cargo Arrival Information to GHA and Customs after receiving from Airlines.
\nProcess Flows:
\nAirport Community System → GHA System
\nAirport Community System → Airline System
\nAirport Community System → Postal Aviation Authority
\nPriority: P1
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","cargo-arrivals"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"e5b41d96-1678-451d-b741-3cb67cde5edf"},{"name":"Upload X-ray Images","id":"8a1b631b-24bd-45af-88ee-02e0d0759e08","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"54d2ce1b-83a1-444b-94f2-c2d405726adb"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.799Z"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"images\": [\n {\n \"scannedAt\": \"2025-11-24T10:30:00Z\",\n \"scanResult\": \"cleared\",\n \"id\": \"7ced6c4f-872d-43c4-9203-1423e2949c00\",\n \"name\": \"1.png\",\n \"contentType\": \"image/png\",\n \"scannedBy\": \"Operator-001\",\n \"machineId\": \"XRAY-KHI-03\",\n \"angle\": \"front\"\n },\n {\n \"scannedAt\": \"2025-11-24T10:32:00Z\",\n \"scanResult\": \"flagged\",\n \"id\": \"cd25c14e-aa7e-4440-aa02-25407936557e\",\n \"name\": \"2.png\",\n \"contentType\": \"image/png\",\n \"scannedBy\": \"Operator-001\",\n \"machineId\": \"XRAY-KHI-03\",\n \"angle\": \"top\"\n }\n ]\n}","options":{"raw":{"headerFamily":"json","language":"json"}}},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/security-scans/:id/images","description":"Requirement Reference: G.I13GHA.19
\nUse Case: Upload x-ray scan images
\nImage Angles:
\nFRONT: Front view
\nSIDE: Side view
\nTOP: Top view
\nDETAIL: Detail/close-up view
\nMULTI_ANGLE: Multiple angles in single image
\nProcess Flow: GHA System → Airport Community System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","security-scans",":id","images"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"scan-12345","key":"id"}]}},"response":[],"_postman_id":"8a1b631b-24bd-45af-88ee-02e0d0759e08"}],"id":"6b10b81d-d3e5-485f-ba2c-73e980d9e899","_postman_id":"6b10b81d-d3e5-485f-ba2c-73e980d9e899","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Trucking Operations","item":[{"name":"Create Trucking Request","id":"adcde992-ba51-4a46-ae9a-e02fcfc3106e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"2b0f9a0f-a075-47f4-b7f8-f27ef12d43c5"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.799Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/trucking-requests","description":"Requirement References:
\nEO.I24TRK.24
\nG.I24CNE.38
\nG.I24ACA.39
\nG.I25GHA.40
\nUse Case: Create Trucking Request
\nDescription: ACA/Trader creates a Trucking Request for pick-up via ACS.
\nProcess Flow: Air Cargo Agent/Trader → Airport Community System → Trucking Company
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","trucking-requests"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"adcde992-ba51-4a46-ae9a-e02fcfc3106e"},{"name":"Submit Trucking Quote","id":"cdc672e4-dab0-48ea-80eb-610982dbdffc","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"e72bec53-433a-4e88-b449-fdb393f72a5e"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.799Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/trucking-requests/:requestId/quotes","description":"Requirement Reference: EO.I24TRK.24
\nUse Case: Submit Quote for Trucking Requests in ACS
\nDescription: Trucking Company submits quote response to ACA via ACS.
\nProcess Flow: Trucking Company → Airport Community System
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","trucking-requests",":requestId","quotes"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"trk-req-001","key":"requestId"}]}},"response":[],"_postman_id":"cdc672e4-dab0-48ea-80eb-610982dbdffc"},{"name":"Accept Trucking Quote","id":"910234e1-f7af-4d74-91e2-d277702e73a7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"994f62d8-66b8-4e3a-ac82-27a2338be184"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.799Z"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"ghaCode\": \"GHA001\",\n \"confirmedAmount\": 15000,\n \"confirmedCurrency\": \"PKR\"\n}","options":{"raw":{"headerFamily":"json","language":"json"}}},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/trucking-requests/:requestId/quotes/:quoteId/accept","description":"Requirement References:
\nEO.I24TRK.24
\nG.I24CNE.38
\nG.I24ACA.39
\nUse Cases:
\nDescription: ACA/Trader user reviews and accepts trucking quote.
\nProcess Flow: Air Cargo Agent/Trader → Airport Community System
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","trucking-requests",":requestId","quotes",":quoteId","accept"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"trk-req-001","key":"requestId"},{"type":"any","value":"quote-001","key":"quoteId"}]}},"response":[],"_postman_id":"910234e1-f7af-4d74-91e2-d277702e73a7"},{"name":"Reject Trucking Quote","id":"7e81779e-9668-4896-91e6-e85f42ee2e3f","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"b30b572b-c778-444c-911c-37986cdbfeea"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.800Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/trucking-requests/:requestId/quotes/:quoteId/reject","description":"Requirement References:
\nEO.I24TRK.24
\nG.I24CNE.38
\nG.I24ACA.39
\nUse Case: Accept/Reject Trucking Quotes in ACS
\nDescription: ACA/Trader user reviews and rejects trucking quote.
\nProcess Flow: Air Cargo Agent/Trader → Airport Community System
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","trucking-requests",":requestId","quotes",":quoteId","reject"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"trk-req-001","key":"requestId"},{"type":"any","value":"quote-001","key":"quoteId"}]}},"response":[],"_postman_id":"7e81779e-9668-4896-91e6-e85f42ee2e3f"},{"name":"Accept Trucking Job","id":"a7e40d67-4be8-4c8f-80fa-b2ff94466a5c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"7621187a-5f74-412a-94c1-6bef0d08f382"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.800Z"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"ghaCode\": \"GHA001\",\n \"pickup\": {\n \"confirmedTime\": \"2025-11-24T09:00:00+05:00\"\n },\n \"delivery\": {\n \"confirmedTime\": \"2025-11-24T14:00:00+05:00\"\n },\n \"vehicleInfo\": {\n \"vehicleRegistration\": \"KHI-ABC-1234\",\n \"vehicleType\": \"TRUCK\",\n \"driverName\": \"Muhammad Aslam\",\n \"driverCNIC\": \"42101-1234567-1\",\n \"driverPhone\": \"+92-21-12345678\",\n \"dockNumber\": \"LG\",\n \"qrToken\": \"base64:....\"\n }\n}","options":{"raw":{"headerFamily":"json","language":"json"}}},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/trucking-requests/:requestId/job/:jobId/accept","description":"Requirement References:
\nEO.I24TRK.24
\nG.I25GHA.40
\nUse Cases:
\nDescription: ACA/Trader user reviews and accepts trucking job. ACS updates trucking job status (Accepted) and optionally sends Driver & Vehicle Details to authorized GHAs via API if enabled for EDI.
\nProcess Flow: Transporter / Truck Operator → Airport Community System → GHA System
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","trucking-requests",":requestId","job",":jobId","accept"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"trk-req-001","key":"requestId"},{"type":"any","value":"job-001","key":"jobId"}]}},"response":[],"_postman_id":"a7e40d67-4be8-4c8f-80fa-b2ff94466a5c"},{"name":"Reject Trucking Job","id":"f4f47ed0-f936-4cf4-b512-e149b5088c5d","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"c5d5b188-9e0f-4f2b-966e-b9fd605c9d2e"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.800Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/trucking-requests/:requestId/jobs/:jobId/reject","description":"Requirement References:
\nEO.I24TRK.24
\nG.I25GHA.40
\nUse Case: Accept/Reject Trucking Jobs in ACS
\nDescription: ACA/Trader user reviews and rejects trucking job. ACS updates trucking job status (Rejected) and optionally sends Driver & Vehicle Details to authorized GHAs via API if enabled for EDI.
\nProcess Flow: Transporter / Truck Operator → Airport Community System → GHA System
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","trucking-requests",":requestId","jobs",":jobId","reject"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"trk-req-001","key":"requestId"},{"type":"any","value":"job-001","key":"jobId"}]}},"response":[],"_postman_id":"f4f47ed0-f936-4cf4-b512-e149b5088c5d"},{"name":"Submit GHA Slot Assignment","id":"6ff62020-c0ac-4ea8-870a-9a9913616b3d","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"78557224-5692-4e6d-b318-6e36d6c848c4"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.800Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/trucking-jobs/:jobId/slot","description":"Requirement Reference:
\nEO.I26TRK.25
\nG.I25GHA.40
\nG.I27GHA.46
\nUse Case: Send GHA Truck Slot Number to ACS
\nDescription: GHA sends assigned slot number and time for truck arrival.
\nProcess Flow: GHA System → Airport Community System
\nPriority: P1
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","trucking-jobs",":jobId","slot"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"trk-job-001","key":"jobId"}]}},"response":[],"_postman_id":"6ff62020-c0ac-4ea8-870a-9a9913616b3d"}],"id":"ad0642df-3b68-4b75-9905-1811f871b4ab","_postman_id":"ad0642df-3b68-4b75-9905-1811f871b4ab","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"9059e7b4-92ac-4941-95ef-9ec8ae5510f6","_postman_id":"9059e7b4-92ac-4941-95ef-9ec8ae5510f6","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Delivery Orders (e-DO)","item":[{"name":"Create e-DO","id":"d433a3ba-fec0-40df-ac54-e2d6d8dba705","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"105b6c11-ed20-4ba2-a6b1-943deb646e7b"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.800Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/delivery-orders","description":"Requirement Reference: G.I15GHA.22
\nUse Case: Send e-DO to ACS
\nDescription: GHA creates electronic Delivery Order (e-DO) for import shipments after customs clearance.
\nShipment Types:
\nDIRECT: Direct shipment (MAWB only) - GHA issues directly to Consignee
\nCONSOLIDATED: Consolidated shipment (HAWB under MAWB) - GHA issues to ACA who then issues to Consignee
\nProcess Flow: GHA System → Airport Community System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","delivery-orders"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"d433a3ba-fec0-40df-ac54-e2d6d8dba705"},{"name":"Create e-DO Payment","id":"172c9fa0-e5e9-42d8-8d6b-5c354a5e18e5","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for request tracing
\n","key":"X-Request-ID","value":"78631dde-1283-455d-80c9-70cbfbdbcc66"},{"description":"Identifier of the system making the request
\n","key":"X-Request-System","value":"{{request_system}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.800Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/delivery-order-payments","description":"Requirement References:
\nG.I16CNE.24
\nG.I17CNE.25
\nG.I17ACA.26
\nG.I18CNE.27
\nG.I17GHA.29
\nUse Case: Generate Invoice for e-DO fees
\nDescription: ACS sends API request to PSW's UPS to generate PSID for e-DO fee and receives PSID and payment details; ACS notifies ACA, GHA, Consignee, or Customs Broker of payment due.
\nPayment Workflows:
\nConsolidated Shipments (Two-step):
\nConsignee pays e-DO fee to ACA via PSW UPS
\nACA receives payment confirmation
\nACA pays GHA e-DO fee via PSW UPS
\nGHA receives payment and authorizes cargo release
\nDirect Shipments (Direct):
\nConsignee pays e-DO fee to GHA via PSW UPS
\nGHA receives payment and authorizes cargo release
\nPSW UPS Integration:
\nGenerates PSID (Payment System ID) for tracking
\nProvides payment link for online/bank payment
\nSends payment confirmation to all parties
\nReal-time status updates
\nProcess Flows:
\nCONSOLIDATED: Consignee System → Airport Community System → Pakistan Single Window UPS → Air Cargo Agent → GHA System
\nDIRECT: Consignee System → Airport Community System → Pakistan Single Window UPS → GHA System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","delivery-order-payments"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"172c9fa0-e5e9-42d8-8d6b-5c354a5e18e5"},{"name":"[deprecated] Push e-DO to ACA","id":"2b0e6e8a-3556-4654-a8dc-f8d498558f0a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/delivery-orders/:id/push/aca","description":"ACS pushes e-DO to ACA system for consolidated shipments. ACA will verify and forward to Consignee.
\nRequirement Reference: G.I16ACA.23
\nUse Case: Receive e-DO from ACS
\nDescription: ACS pushes e-DO to ACA for verification and release.
\nProcess Flow: ACS → ACA System (external API)
\nPriority: P1 (Critical Integration)
\nActors: ACS → ACA System
\nBusiness Rules:
\nOnly for CONSOLIDATED shipments
\nACA verifies e-DO details match their HAWB records
\nACA then issues e-DO to Consignee with their invoice
\nPush is asynchronous with retry mechanism
\nNotification sent to ACA users upon successful push
\nIntegration Pattern: Two-hop middleware pattern (GHA → ACS → ACA)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","delivery-orders",":id","push","aca"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"edo-12345","key":"id"}]}},"response":[{"id":"bdf44dc6-9120-4079-a6dc-e64471ab5567","name":"Success - Pushed to ACA","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerACS pushes e-DO notification to Consignee for direct shipments or after ACA verification for consolidated shipments.
\nRequirement Reference: G.I16CNE.24
\nUse Case: Update on e-DO (Consol)/e-DO invoice received (Direct)
\nDescription: ACS will enable Consignee to digitally receive status updates on delivery order process of its shipment, when it is ready to processing from GHA and ACA. ACS will enable Consignee to digitally receive e-DO invoice from GHA or ACA.
\nProcess Flow: ACS → Consignee (Email/SMS/Portal)
\nPriority: P1 (Critical Integration)
\nActors: ACS → Consignee
\nBusiness Rules:
\nConsignee notified via email, SMS, and portal notification
\nIncludes e-DO details and payment invoice link
\nFor DIRECT shipments: Invoice from GHA
\nFor CONSOLIDATED shipments: Invoice from ACA
\nConsignee can view and download e-DO from PSW Portal
\nView list of electronic Delivery Orders (e-DO).
\nRequirement Reference: G.I15GHA.22, G.I16ACA.23
\nPriority: P2
\nActors: GHA, ACA, Consignee, Customs Broker
\nQuery Parameters:
\nFilter by AWB number
\n","type":"text/plain"},"key":"awbNumber","value":"176-12345678"},{"description":{"content":"Filter by HAWB number
\n","type":"text/plain"},"key":"hawbNumber","value":"SKL-00012345"},{"description":{"content":"Filter by status: ISSUED, PAID, EXPIRED
\n","type":"text/plain"},"key":"status","value":"ISSUED"},{"description":{"content":"Filter by type: DIRECT, CONSOLIDATED
\n","type":"text/plain"},"key":"shipmentType","value":"CONSOLIDATED"},{"description":{"content":"Filter by issued date from
\n","type":"text/plain"},"key":"issuedDateFrom","value":"2025-11-01"},{"description":{"content":"Filter by issued date to
\n","type":"text/plain"},"key":"issuedDateTo","value":"2025-11-30"},{"key":"page","value":"1"},{"key":"limit","value":"20"}],"variable":[]}},"response":[{"id":"3a2b9f09-2db7-4fd9-8dde-aecd9d765d80","name":"Success - e-DO List","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerView specific e-DO details including full cargo information, payment status, and pickup details.
\nRequirement Reference: G.I15GHA.22, G.I16ACA.23
\nPriority: P2
\nActors: GHA, ACA, Consignee, Customs Broker
\nReturns: Complete e-DO details including cargo, customs clearance, payment status, and pickup information.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","delivery-orders",":id"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"edo-12345","key":"id"}]}},"response":[{"id":"8112b21f-077f-4fb7-b397-3f072623a841","name":"Success - e-DO Details","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: G.I20GHA.31
\nUse Case: Create GHA Handling & Storage Charges Invoice in ACS
\nDescription: GHA creates handling & storage charge invoices through ACS.
\nProcess Flow: GHA System → Airport Community System
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","gha-handling-invoices"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"611f7237-0750-489e-abd2-4e6ad214aede"},{"name":"[deprecated] Push Invoice to ACA","id":"c9b4b108-c386-422d-b6ad-aba9c83b9ff8","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/gha-handling-invoices/:id/push/aca","description":"ACS pushes GHA handling & storage invoice to ACA system.
\nRequirement Reference: G.I20GHA.31
\nProcess Flow: ACS → ACA System
\nPriority: P2
\nActors: ACS → ACA
\nBusiness Rules:
\nACS pushes GHA handling & storage invoice to Consignee.
\nRequirement Reference: G.I20GHA.31, G.I21CNE.32
\nProcess Flow: ACS → Consignee
\nPriority: P2
\nActors: ACS → Consignee
\nBusiness Rules:
\nACS pushes GHA handling & storage invoice to Customs Broker.
\nRequirement Reference: G.I21CB.35
\nUse Case: Update received
\nDescription: ACS will enable CB to receive consignment cleared message in digital format. ACS will enable CB to e-invoice for handling & storage from GHA on behalf of consignee in digital format.
\nProcess Flow: ACS → Customs Broker System
\nPriority: P2
\nActors: ACS → Customs Broker
\nBusiness Rules:
\nCB may pay on behalf of Consignee
\nCB coordinates pickup after payment
\nInvoice integrated with CB's billing system
\nCustoms Broker or ACA initiates payment for GHA handling & storage fees via PSW UPS.
\nRequirement Reference: G.I22CB.36
\nUse Case: Payment of Ground handling fees
\nDescription: ACS will enable CB to payment of handling & storage fees via payment gateway to GHA.
\nProcess Flow: CB/ACA → ACS → PSW UPS → GHA
\nPriority: P2
\nActors: Customs Broker, ACA, PSW UPS, GHA
\nBusiness Rules:
\nPayment required before cargo pickup
\nCB or ACA may pay on behalf of Consignee
\nPayment via PSW UPS with PSID tracking
\nReceipt auto-generated for payer and beneficiary
\nPayment confirmation triggers cargo release
\nPayment Flow:
\nCB/ACA initiates payment
\nPSW UPS generates PSID and payment link
\nPayment processed through bank/online
\nConfirmation sent to GHA
\nGHA authorizes cargo release
\nReceipt issued to payer
\nGHA receives handling & storage fee payment confirmation from PSW UPS.
\nRequirement Reference: G.I22GHA.37
\nUse Case: Payment received for handling & storage fees
\nDescription: ACS will enable GHA to receive payment via payment gateway for handling & storage fees from CB on behalf of CNE digitally.
\nProcess Flow: PSW UPS → ACS → GHA
\nPriority: P2
\nActors: PSW UPS → ACS → GHA
\nBusiness Rules:
\nPayment confirmation triggers cargo release authorization
\nUpdates invoice status to PAID
\nReceipt auto-generated and distributed
\nNotifies warehouse to prepare cargo
\nEnables TSM pickup slot assignment
\nNotifies CB/ACA/Consignee of payment completion
\nValidation:
\nPSID must match invoice payment
\nAmount must match invoice total
\nPayment within validity period
\nGlobal API References:
\n\nRequirement Reference: G.I4AL.1
\nUse Case: Send Advance Cargo Information (ACI) to ACS
\nDescription: Airline system sends Advance Cargo Information (ACI) including Flight Manifest, Master and House Air Waybills, and Mail Manifest to ACS via API (IATA EDI-compliant) or through UI upload.
\nProcess Flow: I4AL → I4ACS
\nPriority: P1 (Critical Integration)
\nActors: Airline → ACS
\nMessage Format: IATA Cargo-XML (XFWB)
\nContent-Type: application/xml
Business Context: MAWB data provides detailed shipment information including shipper, consignee, cargo details, and handling instructions. This is required for customs clearance and cargo handling.
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"mawbId\": \"mawb-12345\",\n \"awbNumber\": \"176-12345678\",\n \"format\": \"XFWB\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:40:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:40:00Z\",\n \"requestId\": \"req-123462\"\n }\n}\n\nRequirement Reference: G.I4AL.1
\nUse Case: Send Advance Cargo Information (ACI) to ACS
\nDescription: Airline system sends Advance Cargo Information (ACI) including Flight Manifest, Master and House Air Waybills, and Mail Manifest to ACS via API (IATA EDI-compliant) or through UI upload.
\nProcess Flow: I4AL → I4ACS
\nPriority: P1 (Critical Integration)
\nActors: Airline → ACS
\nMessage Format: IATA Cargo-IMP (FWB)
\nContent-Type: text/plain
Business Context: FWB is the legacy IATA Cargo-IMP format for Master Air Waybill data. Many airlines still use this format.
\nFWB Format Structure:
\nLine 1: Message type (FWB)
\nLine 2: AWB number
\nLine 3: Recipient address
\nLine 4: Date/time
\nLine 5: Origin/Destination
\nLine 6: Pieces/Weight
\nLine 7: Shipper details
\nLine 8: Consignee details
\nLine 9: Commodity description
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"mawbId\": \"mawb-12345\",\n \"awbNumber\": \"176-12345678\",\n \"format\": \"FWB\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:41:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:41:00Z\",\n \"requestId\": \"req-123463\"\n }\n}\n\nRequirement Reference: G.I4AL.1
\nUse Case : Send Advance Cargo Information (ACI) to ACS
\nDescription: Airline system sends Advance Cargo Information (ACI) including Flight Manifest, Master and House Air Waybills, and Mail Manifest to ACS via API (IATA EDI-compliant) or through UI upload.
\nProcess Flow: I4AL → I4ACS
\nPriority: P1 (Critical Integration)
\nActors: Airline → ACS
\nMessage Format: IATA Cargo-XML (XFZB)
\nContent-Type: application/xml
Business Context: HAWB data is required for consolidated shipments where multiple consignments are grouped under a single MAWB. Each HAWB represents an individual shipment within the consolidation.
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"hawbId\": \"hawb-12345\",\n \"hawbNumber\": \"SKL-00012345\",\n \"mawbNumber\": \"176-12345678\",\n \"format\": \"XFZB\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:45:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:45:00Z\",\n \"requestId\": \"req-123464\"\n }\n}\n\nRequirement Reference: G.I4AL.1, G.I4P.3
\nUse Case: Send Advance Cargo Information (ACI) to ACS\" and \"View Mail Manifest in ACS
\nDescription: Airline system sends Advance Cargo Information (ACI) including Flight Manifest, Master and House Air Waybills, and Mail Manifest to ACS via API (IATA EDI-compliant) or through UI upload.
\nProcess Flow: I4AL → I4ACS
\nPriority: P1 (Critical Integration)
\nActors: Airline → ACS
\nMessage Format: IATA Cargo-IMP (FHL)
\nContent-Type: text/plain
Business Context: FHL is the legacy IATA Cargo-IMP format for House Air Waybill and Mail data. This format covers both consolidated cargo (HAWBs) and mail bags.
\nFHL Format Structure:
\nLine 1: Message type (FHL)
\nLine 2: MAWB number
\nLine 3: HAWB number/Pieces/Weight
\nLine 4: Shipper
\nLine 5: Consignee
\nLine 6: Commodity
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"hawbId\": \"hawb-12345\",\n \"hawbNumber\": \"SKL-00012345\",\n \"mawbNumber\": \"176-12345678\",\n \"format\": \"FHL\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:46:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:46:00Z\",\n \"requestId\": \"req-123465\"\n }\n}\n\nRequirement Reference: G.I4GHA.2, G.I25GHA.40, G.I20GHA.31, G.I27ACA.47, G.I27AL.48
\nUse Case: View Air Waybills in ACS
\nDescription: ACS provides access to Master Air Waybill data for Airlines, GHAs, PAA.
\nPriority: P2
\nActors: Airline, GHA, PAA, ACA
\nQuery Parameters:
\nflightNumber: Filter by flight number
awbNumber: Filter by AWB number
origin: Filter by origin airport
destination: Filter by destination airport
arrivalDate: Filter by arrival date
page: Page number
limit: Items per page
Success Response (200 OK):
\n{\n \"success\": true,\n \"data\": [\n {\n \"mawbId\": \"mawb-12345\",\n \"awbNumber\": \"176-12345678\",\n \"flightNumber\": \"EK-606\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 10,\n \"weight\": 500,\n \"weightUnit\": \"kg\",\n \"commodityDescription\": \"Electronics\",\n \"shipper\": {\n \"name\": \"ABC Electronics LLC\"\n },\n \"consignee\": {\n \"name\": \"XYZ Trading\"\n },\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:40:00Z\"\n }\n ],\n \"meta\": {\n \"pagination\": {\n \"currentPage\": 1,\n \"totalPages\": 1,\n \"pageSize\": 20,\n \"totalCount\": 1\n },\n \"timestamp\": \"2025-11-28T15:05:00Z\",\n \"requestId\": \"req-123468\"\n }\n}\n\nRequirement Reference: G.I4GHA.2, G.I25GHA.40, G.I20GHA.31, G.I27ACA.47, G.I27AL.48
\nUse Case: View House Air Waybills in ACS
\nDescription: ACS provides view access to House Air Waybill data for Airlines, GHAs, PAA.
\nPriority: P2
\nActors: Airline, GHA, PAA, ACA
\nQuery Parameters:
\nmawbNumber: Filter by MAWB number (consolidation)
hawbNumber: Filter by HAWB number
flightNumber: Filter by flight number
page: Page number
limit: Items per page
Success Response (200 OK):
\n{\n \"success\": true,\n \"data\": [\n {\n \"hawbId\": \"hawb-12345\",\n \"hawbNumber\": \"SKL-00012345\",\n \"mawbNumber\": \"176-12345678\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 5,\n \"weight\": 250,\n \"weightUnit\": \"kg\",\n \"commodityDescription\": \"Electronics - Laptop Computers\",\n \"shipper\": {\n \"name\": \"Tech Supplier LLC\"\n },\n \"consignee\": {\n \"name\": \"Electronics Retailer Pvt Ltd\"\n },\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:45:00Z\"\n }\n ],\n \"meta\": {\n \"pagination\": {\n \"currentPage\": 1,\n \"totalPages\": 1,\n \"pageSize\": 20,\n \"totalCount\": 1\n },\n \"timestamp\": \"2025-11-28T15:10:00Z\",\n \"requestId\": \"req-123469\"\n }\n}\n\nRequirement Reference: G.I4P.3
\nUse Case: View Mail Manifest in ACS
\nDescription: ACS displays Mail Manifest received from Airlines to authorized entities.
\nPriority: P2
\nActors: Airline, GHA, PAA, Pakistan Post
\nBusiness Context: Mail manifests contain postal items (mail bags) transported on commercial flights. Pakistan Post uses this data for mail processing and delivery.
\nSuccess Response (200 OK):
\n{\n \"success\": true,\n \"data\": [\n {\n \"mailManifestId\": \"mail-12345\",\n \"flightNumber\": \"EK-606\",\n \"arrivalDate\": \"2025-11-28\",\n \"arrivalTime\": \"20:00:00Z\",\n \"mailBags\": [\n {\n \"mailBagNumber\": \"MAIL-DXB-KHI-001\",\n \"weight\": 100,\n \"weightUnit\": \"kg\",\n \"numberOfBags\": 3,\n \"origin\": \"DXB\",\n \"destination\": \"KHI\"\n }\n ],\n \"totalBags\": 3,\n \"totalWeight\": 100,\n \"weightUnit\": \"kg\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:30:00Z\"\n }\n ],\n \"meta\": {\n \"pagination\": {\n \"currentPage\": 1,\n \"totalPages\": 1,\n \"pageSize\": 20,\n \"totalCount\": 1\n },\n \"timestamp\": \"2025-11-28T15:15:00Z\",\n \"requestId\": \"req-123470\"\n }\n}\n\nRequirement Reference: EO.I5PAA.6 (from e-Ops module)
\nUse Case: View Flight Manifest in ACS
\nPriority: P2
\nActors: PAA (Pakistan Airport Authority)
\nBusiness Context: PAA requires flight and cargo statistics for airport planning, capacity management, infrastructure development, and regulatory reporting.
\nQuery Parameters:
\ndateFrom: Start date for statistics (YYYY-MM-DD)
dateTo: End date for statistics (YYYY-MM-DD)
airport: Airport code (KHI, LHE, ISB, etc.)
reportType: Type of report (summary, detailed, by-airline, by-origin)
Success Response (200 OK):
\n{\n \"success\": true,\n \"data\": {\n \"reportType\": \"summary\",\n \"airport\": \"KHI\",\n \"period\": {\n \"from\": \"2025-11-01\",\n \"to\": \"2025-11-30\"\n },\n \"summary\": {\n \"totalFlights\": 450,\n \"totalPieces\": 67500,\n \"totalWeight\": 3375000,\n \"weightUnit\": \"kg\",\n \"totalMailBags\": 450,\n \"averageFlightLoad\": 7500,\n \"topOrigins\": [\n {\"airport\": \"DXB\", \"flights\": 120},\n {\"airport\": \"DOH\", \"flights\": 80},\n {\"airport\": \"RUH\", \"flights\": 60}\n ],\n \"topAirlines\": [\n {\"airline\": \"Emirates\", \"flights\": 120},\n {\"airline\": \"Qatar Airways\", \"flights\": 80}\n ]\n }\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T15:20:00Z\",\n \"requestId\": \"req-123471\"\n }\n}\n\nRequirement Reference: EO.I5PSW.5 (from e-Ops module)
\nUse Case: View Cargo Arrival Information in PSW
\nDescription: PSW retrieves Cargo Arrival Information from ACS through API.
\nPriority: P2
\nActors: PSW Portal
\nBusiness Context: PSW Portal provides public visibility of trade statistics, cargo volumes, and arrival information for government reporting and business intelligence.
\nQuery Parameters:
\ndateFrom: Start date for statistics (YYYY-MM-DD)
dateTo: End date for statistics (YYYY-MM-DD)
reportType: Type of report (trade-volume, by-commodity, by-country)
Success Response (200 OK):
\n{\n \"success\": true,\n \"data\": {\n \"reportType\": \"trade-volume\",\n \"period\": {\n \"from\": \"2025-11-01\",\n \"to\": \"2025-11-30\"\n },\n \"summary\": {\n \"totalImportVolume\": 3375000,\n \"volumeUnit\": \"kg\",\n \"totalShipments\": 4500,\n \"averageShipmentWeight\": 750,\n \"topCommodities\": [\n {\"commodity\": \"Electronics\", \"weight\": 1012500},\n {\"commodity\": \"Garments\", \"weight\": 675000},\n {\"commodity\": \"Machinery\", \"weight\": 506250}\n ],\n \"topOrigins\": [\n {\"country\": \"UAE\", \"weight\": 1350000},\n {\"country\": \"Qatar\", \"weight\": 675000},\n {\"country\": \"Saudi Arabia\", \"weight\": 506250}\n ]\n }\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T15:25:00Z\",\n \"requestId\": \"req-123472\"\n }\n}\n\nRequirement Reference: G.I8GHA.9
\nUse Case : Performs on spot check of ULD intactness
\nDescription: ACS will enable GHA to record ULD check of unloaded consignment digitally. In case of ULD damage, ACS will enable GHA to transmit damage record to airlines digitally.
\nProcess Flow: I7GHA → I8GHA → I9GHA → I10AL (if damaged)
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Airline (if damage reported)
\nAuthentication: JWT Bearer token required
\nBusiness Rules:
\nULD check must be performed within 2 hours of flight arrival
\nIf integrity status is DAMAGED, damage details are mandatory
\nImage uploads recommended for damage claims
\nAirline automatically notified if ULD damaged
\nCargo condition tracked separately from ULD condition
\nIntegrity Status Values:
\nINTACT: ULD in good condition, no damage
\nDAMAGED: ULD has visible damage (requires damage details)
\nSEAL_BROKEN: Security seal broken (security investigation required)
\nMISSING: ULD not found in cargo hold
\nDamage Types:
\nDENT: Impact damage causing dents
\nTEAR: Fabric or panel tears
\nBROKEN_LATCH: Latch mechanism broken
\nSTRUCTURAL: Structural frame damage
\nCONTAMINATION: Contamination from spills/leaks
\nOTHER: Other types of damage
\nDamage Severity:
\nMINOR: Cosmetic damage, no repair needed
\nMODERATE: Requires repair, ULD still usable
\nMAJOR: Extensive damage, ULD unusable
\nTOTAL_LOSS: ULD beyond repair
\nResponse Codes:
\n201: ULD integrity check recorded successfully
\n400: Invalid check data or missing damage details
\n401: Unauthorized
\n404: Flight or ULD not found
\n409: ULD check already submitted
\nRequirement Reference: G.I9GHA.10
\nUse Case: Confirms arrival of shipments against FFM
\nDescription: ACS will enable GHA to transmit consignment cargo received information (ARR/RCF) to ACA, Consignee, Airline, CB, Customs, Consignor and Express Parcel Operator unloading digitally.
\nProcess Flow: I8GHA → I9GHA → I10CNE, I10ACA, I10AL, I10CB, I10CUS, I10CGNR, I10EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → 7 stakeholders (ACA, Consignee, Airline, Customs Broker, Customs, Consignor, EPO)
\nAuthentication: JWT Bearer token required
\nBusiness Rules:
\nMust match against FFM (Flight Manifest) data
\nDiscrepancies (missing/damaged pieces) must be documented
\nAll stakeholders notified automatically
\nWarehouse location must be valid GHA storage location
\nTemperature-controlled cargo tracked separately
\nCondition Values:
\nGOOD: Cargo in good condition
\nDAMAGED: Cargo shows damage
\nWET: Water damage detected
\nSHORTAGE: Pieces missing (discrepancy)
\nOVERAGE: Extra pieces found (discrepancy)
\nDiscrepancy Types:
\nMISSING_PIECES: Expected pieces not received
\nDAMAGED_PIECES: Pieces damaged in transit
\nWEIGHT_DISCREPANCY: Weight mismatch
\nPACKAGE_DAMAGED: Outer packaging damaged
\nSEAL_BROKEN: Security seal broken
\nMessage Type: IATA FSU RCF (Received from Flight)
\nMulti-Stakeholder Distribution:
\nACA (Air Cargo Agent) - for consolidated shipments
\nConsignee - arrival notification
\nAirline - delivery confirmation
\nCustoms Broker - for customs clearance
\nCustoms (WeBOC) - regulatory notification
\nConsignor - proof of delivery to destination
\nEPO (Express Post Office) - for express items
\nResponse Codes:
\n201: Cargo received confirmation recorded successfully
\n400: Invalid cargo data or discrepancies
\n401: Unauthorized
\n404: AWB/HAWB not found in FFM
\n409: Cargo already marked as received
\nRequirement Reference: G.I9GHA.10
\nUse Case: Confirms arrival of shipments against FFM
\nDescription: IATA Cargo-XML (XFSU) with RCF status code
\nContent-Type: application/xml
\nStandards: IATA Cargo-XML, FSU RCF message type
\nResponse: Same JSON structure as standard endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","cargo-received-confirmations","xfsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"c885e490-b265-46da-95bc-97fad1152e6f"},{"name":"Submit Cargo Received Confirmation (RCF) - IATA IMP","id":"78c7ec19-944b-4183-8316-13bda640fd2f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Request-ID","value":"87cfd27c-c840-475a-83b1-c2665d4ac4bc"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/cargo-received-confirmations/fsu","description":"Requirement Reference: G.I9GHA.10
\nUse Case: Confirms arrival of shipments against FFM
\nDescription: IATA Cargo-IMP (FSU) with RCF status code
\nContent-Type: text/plain
\nStandards: IATA Cargo-IMP, FSU RCF message type
\nFSU Status Code: RCF = Received from Flight
\nResponse: Same JSON structure as standard endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","cargo-received-confirmations","fsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"78c7ec19-944b-4183-8316-13bda640fd2f"}],"id":"ceb12d75-1cdc-4da6-97b2-c99c7ff1bc03","_postman_id":"ceb12d75-1cdc-4da6-97b2-c99c7ff1bc03","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Document Management","item":[{"name":"Upload Import Documents (ACA/Consignee)","id":"83124930-a6dc-4e7f-b737-7f79f2447000","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"multipart/form-data"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/documents/receipts","description":"Requirement Reference: G.I5ACA.5, G.I5CNE.6, G.I6GHA.7
\nUse Case (ACA): Consolidation, ACA uploads imports documents (ACI Process)
\nDescription (ACA): ACS will enable ACA to send the document of import shipment in digital format to Customs, its customs broker or Consignee before flight departure.
\nUse Case (Consignee): Direct shipment, Consignee uploads imports documents (ACI process)
\nIntegration Point (Consignee): ACS will enable Consignee to send the documents of import shipment in digital format to Customs, its customs broker or Air Cargo Agent.
\nProcess Flow:
\nACA: I5ACA → I6CNE, I6CB, I6CUS, I6GHA
\nConsignee: I5CNE → I6CB, I6CUS, I6GHA
\nPriority: P1 (Critical Integration)
\nActors: ACA, Consignee (senders) → ACS → GHA, Customs, Customs Broker
\nAuthentication: JWT Bearer token required
\nBusiness Rules:
\nDocuments must be uploaded before or within 24 hours of flight arrival
\nSupported file types: PDF, JPG, PNG
\nMaximum file size: 10MB per document
\nMultiple documents can be uploaded per shipment
\nDocuments automatically distributed to stakeholders
\nDocument Types:
\nCOMMERCIAL_INVOICE: Commercial invoice for customs valuation
\nPACKING_LIST: Detailed packing list
\nCERTIFICATE_OF_ORIGIN: Certificate showing origin country
\nIMPORT_PERMIT: Special import permits for restricted goods
\nPHYTOSANITARY_CERTIFICATE: Plant health certificate
\nVETERINARY_CERTIFICATE: Animal health certificate
\nHALAL_CERTIFICATE: Halal certification
\nTEST_REPORT: Product test/quality reports
\nOTHER: Other supporting documents
\nResponse Codes:
\n201: Document uploaded successfully
\n400: Invalid file type or size
\n401: Unauthorized
\n404: AWB/HAWB not found
\n413: File too large (max 10MB)
\nRequirement Reference: G.I6GHA.7, EO.I8CUS.14, G.I15CUS.21
\nUse Case: View uploaded import documents
\nPriority: P2
\nActors: GHA, Customs, Customs Broker, ACA, Consignee
\nQuery Parameters:
\nRequirement Reference: G.I13GHA.19, G.I13PSW.20, G.I15CUS.21
\nUse Case: Shipments are x-rayed
\nDescription: ACS will enable GHA to transmit consignment x-ray image to customs and PSW digitally.
\nProcess Flow: I9GHA → I13GHA → I13PSW, I15CUS, I15GHA
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Customs, PSW Portal
\nAuthentication: JWT Bearer token required
\nBusiness Rules:
\nAll import cargo must be x-rayed before customs clearance
\nScan images required for suspicious items
\nCertified operators only
\nMachine calibration must be current (within 90 days)
\nUp to 20 images per scan (max 10MB each)
\nAnomalies trigger automatic customs notification
\nScan Types:
\nX_RAY: Standard X-ray screening
\nCT_SCAN: Computed Tomography scan (high-risk items)
\nHAND_SEARCH: Manual physical inspection
\nETD: Explosive Trace Detection
\nEDD: Explosive Detection Dog
\nScan Results:
\nCLEAR: No issues detected, cleared for release
\nSUSPICIOUS: Anomaly detected, requires investigation
\nPROHIBITED: Prohibited items detected, do not release
\nREFER_TO_CUSTOMS: Refer to customs for manual inspection
\nAnomaly Types:
\nORGANIC_MATTER: Unexpected organic materials
\nDENSE_OBJECT: Unusually dense objects
\nSHIELDED_AREA: Areas shielded from X-ray
\nLIQUID_CONTAINER: Undeclared liquids
\nPROHIBITED_ITEM: Known prohibited items
\nOTHER: Other anomalies
\nResponse Codes:
\n201: Security scan recorded successfully
\n400: Invalid scan data or expired certification
\n401: Unauthorized
\n403: Operator not certified
\n404: AWB/HAWB not found
\nRequirement Reference: G.I13GHA.19, G.I15CUS.21
\nUse Case: Review of shipment x-ray
\nDescription: ACS will enable Customs to digitally receive and review x-ray scan of import consignment in digital format.
\nProcess Flow: I13GHA → I15CUS
\nPriority: P1 (Critical Integration)
\nActors: ACS → WeBOC (Customs) System
\nBusiness Rules:
\nAutomatic push for suspicious scans
\nIncludes all scan images
\nReal-time notification to customs officers
\nRetry mechanism for failed pushes
\nRequirement Reference: G.I13GHA.19, G.I13PSW.20
\nUse Case: PSW receives data for analysis
\nDescription: ACS will enable PSW to digitally receive X-ray data from GHA for analysis.
\nProcess Flow: I13GHA → I13PSW
\nPriority: P1 (Critical Integration)
\nActors: ACS → PSW Portal
\nBusiness Rules:
\nAll scans pushed to PSW for analytics
\nAggregate data for risk pattern analysis
\nNo personal data included in PSW push
\nStatistical reporting only
\nRequirement Reference: G.I13GHA.19, G.I15CUS.21
\nUse Case: View security scan list
\nPriority: P2
\nActors: GHA, Customs, PSW
\nQuery Parameters:
\nACS receives customs clearance status from WeBOC for import shipments.
\nRequirement Reference: G.I20CUS.30, G.I20GHA.31
\nUse Case: Consignment Item cleared
\nDescription: ACS will enable Customs to digitally communicate release or confiscation of consignment and item in digital format.
\nProcess Flow: WeBOC → ACS → GHA, ACA, Airline, Consignee, CB
\nPriority: P1 (Critical Integration)
\nActors: WeBOC → ACS
\nClearance Statuses:
\nCLEARED: Cargo cleared for release - can issue e-DO
\nCONFISCATED: Cargo confiscated - cannot release
\nEXAMINATION_REQUIRED: Physical examination required
\nHELD: Temporarily held for additional review
\nPENDING_PAYMENT: Awaiting duty/tax payment
\nBusiness Rules:
\nOnly CLEARED status allows e-DO issuance
\nCONFISCATED triggers notification to all stakeholders
\nStatus updates trigger workflow actions:
\nCLEARED → GHA issues e-DO
\nCONFISCATED → Cargo moved to customs warehouse
\nEXAMINATION_REQUIRED → GHA prepares cargo for inspection
\nWCO Immediate Release Guidelines:
\nLow-value shipments may get immediate clearance
\nExpress shipments processed faster
\nRisk-based clearance reduces delays
\nValidation:
\nGD number must exist in system
\nAWB/HAWB must match GD records
\nCustoms officer credentials verified
\nACS pushes customs clearance status to GHA system. Triggers e-DO issuance workflow if CLEARED.
\nRequirement Reference: G.I20GHA.31
\nUse Case: Status updated/ issues invoice for handling & storage fees
\nDescription: ACS will enable GHA to update the customs status of consignment to cleared to CB, ACA, Airlines, and Consignee digitally. ACS will enable GHA to issue invoice for handling & storage digitally to Express Parcel Operator, ACA or CB.
\nProcess Flow: ACS → GHA System
\nPriority: P1 (Critical Integration)
\nActors: ACS → GHA System
\nWorkflow Triggers:
\nCLEARED: GHA issues e-DO and handling/storage invoice
\nCONFISCATED: GHA moves cargo to customs warehouse
\nEXAMINATION_REQUIRED: GHA prepares cargo for inspection
\nBusiness Rules:
\nReal-time push to GHA system
\nAuto-triggers e-DO creation for CLEARED status
\nAuto-generates handling & storage invoice
\nUpdates warehouse management system
\nNotifies GHA operators via dashboard
\nRequirement Reference: G.I26TRK.44
\nUse Case: Receives truck slot - Trucker receives truck slot and information from GHA in digital format.
\nDescription: ACS pushes truck slot and vehicle token to Trucker via API, SMS, and Email.
\nProcess Flow: ACS → Trucker
\nPriority: P1 (Critical Integration)
\nActors: ACS → Trucker System
\nNotification Channels:
\nAPI Push: Full slot details pushed to trucker's webhook endpoint
\nSMS: Vehicle token (6-digit code) + gate number + time sent to driver mobile
\nEmail: Complete slot details with QR code image attached
\nSMS Format Example:
\nPSW ACS: Pickup slot assigned\nGate: GATE-1, Dock: DOCK-B3\nTime: 2025-11-29 10:30-12:00\nToken: 735291\nAWB: 176-12345678\n\nResponse Codes:
\n200 OK: Push successful (all channels)
\n207 Multi-Status: Partial success (some channels failed)
\n404 Not Found: Slot not found
\n500 Internal Server Error: All channels failed
\nRequirement Reference: G.I25GHA.40, G.I27GHA.46
\nPriority: P2
\nActors: GHA, Trucker, ACA, Consignee
\nQuery Parameters:
\ndate: Filter by assigned date
\nstatus: ASSIGNED, CHECKED_IN, COMPLETED, EXPIRED, CANCELLED
\nloadingDock: Filter by dock number
\ngateNumber: Filter by gate number
\nawbNumber: Filter by AWB
\ntruckingCompany: Filter by trucker
\npage: Page number
\nlimit: Results per page
\nResponse Codes:
\n200 OK: List retrieved
\n401 Unauthorized: Authentication required
\nRequirement Reference: G.I27TRK.45
\nUse Case: Truck arrives at GHA facility/loads consignment - Trucker sends arrival at airport information in digital format.
\nDescription: ACS enables Trucker to send arrival at airport information in digital format.
\nProcess Flow: I27TRK → ACS → GHA
\nPriority: P1 (Critical Integration)
\nActors: Trucker
\nAuthentication: OAuth 2.0 JWT Bearer token OR vehicle token validation
\nBusiness Rules:
\nArrival must reference valid TSM slot in ASSIGNED status
\nArrival time must be within slot time window (or within 30 min grace period)
\nVehicle token must be valid and not expired
\nSMS code validation (if provided) must match assigned code
\nDriver CNIC must match job confirmation details
\nVehicle registration must match job confirmation
\nGPS location optional but recommended for audit trail
\nArrival Sources:
\nMOBILE_APP: Driver uses PSW ACS mobile app
\nWEB_PORTAL: Driver/dispatcher uses web portal
\nSMS: Driver sends SMS with token code to shortcode
\nGATE_SCAN: Gate security scans QR code
\nMANUAL: GHA staff manually records arrival
\nToken Validation Process:
\nSystem validates vehicle token format and expiry
\nSystem validates SMS code (if provided)
\nSystem validates driver CNIC against job details
\nSystem validates vehicle registration against job details
\nSystem validates arrival time against slot window
\nIf all validations pass, arrival recorded and GHA notified
\nGrace Period Rules:
\nEarly arrival (>30 min before slot): Held at gate until slot window
\nOn-time arrival (within slot window): Immediate processing
\nLate arrival (<30 min after slot end): Accepted with warning
\nVery late arrival (>30 min after slot end): Rejected, must request new slot
\nResponse Codes:
\n201 Created: Arrival recorded successfully
\n400 Bad Request: Invalid arrival data
\n401 Unauthorized: Invalid vehicle token
\n403 Forbidden: Token expired or slot window passed
\n404 Not Found: TSM slot not found
\n422 Unprocessable Entity: Validation failed (CNIC/vehicle mismatch)
\nRequirement Reference: G.I27GHA.46
\nUse Case : Truck token confirmed/shipment released/vehicle loading - GHA confirms truck slot via QR Token and informs stakeholders on shipment release and loading digitally.
\nDescription: ACS enables GHA to confirm truck slot for pick-up via QR Token and inform Consignee, ACA, CB and Consignor on shipment release and loading digitally.
\nProcess Flow: I27GHA → ACS → Multiple Stakeholders
\nPriority: P1 (Critical Integration)
\nActors: GHA
\nAuthentication: OAuth 2.0 JWT Bearer token
\nBusiness Rules:
\nShipment release must reference valid truck arrival in CHECKED_IN status
\ne-DO must be valid, paid, and customs cleared
\nDriver ID verification mandatory (CNIC check)
\nReleased pieces must match expected pieces (or justify discrepancy)
\nCargo condition assessment mandatory
\nGHA supervisor signature/approval required
\nTemperature check required for refrigerated cargo
\nLoading photos optional but recommended for audit trail
\nRelease automatically updates shipment status to PICKED_UP
\nCargo Condition Values:
\nINTACT: All packages in good condition
\nMINOR_DAMAGE: Minor packaging damage, contents safe
\nMAJOR_DAMAGE: Significant damage observed
\nPARTIAL: Some pieces missing or damaged
\nPackaging Integrity Values:
\nGOOD: Packaging intact and secure
\nFAIR: Minor wear but acceptable
\nPOOR: Significant damage or compromise
\ne-DO Verification:
System validates:
e-DO exists and belongs to this shipment
\nPayment status is PAID
\nCustoms status is CLEARED
\ne-DO not expired
\ne-DO not already used for another release
\nMulti-Stakeholder Notification:
After shipment release, ACS automatically pushes release notification to:
ACA (G.I27ACA.47) - Delivery status update
\nAirline (G.I27AL.48) - Delivery completion
\nCustoms Broker (G.I27CB.49) - Release confirmation
\nConsignor (G.I27CGNR.50) - Cargo picked up at destination
\nConsignee (G.I27CNE.51) - Shipment released to trucker
\nResponse Codes:
\n201 Created: Shipment released successfully
\n400 Bad Request: Invalid release data
\n403 Forbidden: e-DO not valid or customs not cleared
\n404 Not Found: Truck arrival not found
\n422 Unprocessable Entity: Validation failed (pieces mismatch, temperature out of range)
\nRequirement Reference: G.I27ACA.47
\nUse Case : Update received - ACA receives delivery status of the shipment in digital format.
\nDescription: ACS pushes delivery status update to ACA system.
\nProcess Flow: ACS → ACA
\nPriority: P1
\nActors: ACS → ACA System
\nResponse Codes:
\n200 OK: Push successful
\n404 Not Found: Release not found
\n500 Internal Server Error: Push failed
\nRequirement Reference: G.I27CNE.51
\nUse Case: Update received - Consignee digitally receives delivery of the shipment from GHA to trucker information.
\nDescription: ACS pushes shipment release notification to Consignee.
\nProcess Flow: ACS → Consignee
\nPriority: P1
\nActors: ACS → Consignee System
\nResponse Codes:
\n200 OK: Push successful
\n404 Not Found: Release not found
\n500 Internal Server Error: Push failed
\nRequirement Reference: G.I27CB.49
\nUse Case : Update received - CB receives delivery status of the shipment in digital format.
\nDescription: ACS pushes shipment release status to Customs Broker.
\nProcess Flow: ACS → Customs Broker
\nPriority: P1
\nActors: ACS → CB System
\nResponse Codes:
\n200 OK: Push successful
\n404 Not Found: Release not found
\n500 Internal Server Error: Push failed
\nRequirement Reference: G.I27AL.48
\nUse Case: Update delivery - Airline receives delivery to consignee information digitally.
\nDescription: ACS pushes delivery completion status to Airline system.
\nProcess Flow: ACS → Airline
\nPriority: P1
\nActors: ACS → Airline System
\nResponse Codes:
\n200 OK: Push successful
\n404 Not Found: Release not found
\n500 Internal Server Error: Push failed
\nRequirement Reference: G.I27CGNR.50
\nUse Case: Update Received - Consignor digitally receives truck loading information at GHA facility at destination.
\nDescription: ACS pushes truck loading and departure status to Consignor.
\nProcess Flow: ACS → Consignor
\nPriority: P1
\nActors: ACS → Consignor System
\nResponse Codes:
\n200 OK: Push successful
\n404 Not Found: Release not found
\n500 Internal Server Error: Push failed
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"be3c281a-e259-42dc-b157-1da0227b1561"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/hawbs/draft","description":"Global API Reference:
\nRequirement Reference: EO.E7ACA.1
\nUse Case: Transmit and Exchange Draft HAWB with Consignor
\nDescription: The ACS(ACA) shall share the draft HAWB with the Consignor for providing missing information or correction.
\nProcess Flow: Air Cargo Agent System → Airport Community System → Consignor System
\nPriority:
\nP1
\nP2
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"c1a77772-6bc7-48dc-8c6d-995fbda23fd1"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/hawbs/:hawbId/complete","description":"Global API Reference:
\nRequirement Reference: EO.E7CGNR.2
\nUse Case: HAWB draft received to consignor
\nDescription: The ACS system shall allow the Consignor to complete and confirm the HAWB and allow the Consignor to amend specific details.
\nAmendable Fields:
\nConsignee address
\nCommodity description (excluding special cargo)
\nHTS code
\nProcess Flow: Consignor System → Airport Community System → Air Cargo Agent System
\nPriority:
\nP1
\nP2
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"8ad89064-68bb-4c26-ac60-3263daeea7fa"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/hawbs/:hawbId/amendment-request","description":"Requirement Reference: EO.E7CGNR.2
\nUse Case: HAWB draft received to consignor
\nIntegration Point: The ACS(ACA) shall accept, reject, or restart the quotation upon a Consignor's request for HAWB changes; if the Consignor declines to restart, the process shall terminate.
\nProcess Flow: Airline System → Airport Community System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawbs",":hawbId","amendment-request"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"hawb-KHI12345678","key":"hawbId"}]}},"response":[],"_postman_id":"309adeb6-50bf-44d0-a8ec-995cb337ffa3"},{"name":"Respond to Amendment Request","id":"7ae306ff-c46d-49ff-8be3-8412051cb82a","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"accept":true,"content-type":true}},"request":{"method":"PATCH","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"3b0e42a0-f939-446d-b538-2458bb52ca4e"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/hawbs/:hawbId/amendment-request/response","description":"Global API Reference:
\nRequirement Reference: EO.E7CGNR.2
\nUse Case: HAWB draft received to consignor
\nACA Response Options:
\naccepted - Accept the amendment
rejected - Reject with reason
Process Flow: Air Cargo Agent System → Airport Community System → Consignor System
\nPriority:
\nP1
\nP2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawbs",":hawbId","amendment-request","response"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"hawb-KHI12345678","key":"hawbId"}]}},"response":[],"_postman_id":"7ae306ff-c46d-49ff-8be3-8412051cb82a"}],"id":"84e909c4-45af-4849-ac85-0e7fb179c3b4","_postman_id":"84e909c4-45af-4849-ac85-0e7fb179c3b4","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Flight Booking List","item":[{"name":"Create Flight Booking List","id":"441f3462-a624-43a6-b925-cb8458440b85","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true,"accept":true}},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"7579c5f4-6c7e-44e4-9460-3cb20e60df4a"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/flight-booking-lists","description":"Global API Reference:
\nRequirement Reference: EO.E7AL.3
\nUse Case: Airline sends flight booking list to GHA
\nDescription: The ACS system will transmit flight booking details received from the Airline system to the GHA system in digital format.
\nProcess Flow: Airline system → Airport Community System → GHA System
\nPriority:
\nP1
\nP2
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"4f7468b9-98b1-48a7-b0c6-b8b1353dbfd7"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/mawb/consolidate-hawbs","description":"Global API References:
\n\nRequirement Reference: EO.E8ACA.6
\nUse Case: Confirmed HAWB Ready/ Multiple HAWB for same Destination
\nDescription:
\nThe ACS(ACA) consolidate multiple HAWBs for the same destination into a single MAWB
\nShare MAWB details digitally with WeBOC (Customs Broker)
\nCreate and transmit MAWB and assigned HAWB information digitally to Airline system
\nKey Activities:
\nACA consolidates multiple confirmed HAWBs for same destination under one MAWB
\nACA sends MAWB information from ERP or creates in ACS using FFA data
\nMAWB and HAWB information transmitted to Airlines (E23ACA)
\nNotifications sent to Customs Broker and Customs
\nProcess Flows:
\nConsignor System→ Air Cargo Agent System
\nConsignor System→ Air Cargo Agent System
\nPriority:
\nP1 (Integration)
\nP2 (External Systems)
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"138bbb00-28c5-48e0-bdbe-96d5d4473cb9"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/mawb/{{{{awbId}}}}/status","description":"Global API References:
\nRequirement Reference: EO.E8ACA.6
\nUse Case: Confirmed HAWB Ready/ Multiple HAWB for same Destination
\nDescription: Add additional confirmed HAWBs to existing MAWB consolidation.
\nProcess Flows:
\nConsignor System→ Air Cargo Agent System
\nConsignor System→ Air Cargo Agent System
\nPriority:
\nP1 (Integration)
\nP2 (External Systems)
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"f6db5427-d54b-491d-a604-0337403e9619"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"body":{"mode":"raw","raw":"{\n \"MessageHeaderDocument\": {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"020-92560996\"\n },\n \"Name\": {\n \"languageID\": null,\n \"Value\": \"Air Waybill\"\n },\n \"TypeCode\": {\n \"listID\": \"1001\",\n \"listAgencyID\": \"6\",\n \"listAgencyIDSpecified\": true,\n \"listVersionID\": \"D09A\",\n \"name\": null,\n \"listURI\": null,\n \"Value\": \"740\"\n },\n \"IssueDateTime\": \"2016-06-15T11:55:06\",\n \"PurposeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"Creation\"\n },\n \"VersionID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"3.00\"\n },\n \"ConversationID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"725ba4be-9002-53e4-6782-133a2318cc34\"\n },\n \"SenderParty\": [\n {\n \"PrimaryID\": {\n \"schemeID\": \"C\",\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"TDVAGT03TEST/AMS1\"\n }\n }\n ],\n \"RecipientParty\": [\n {\n \"PrimaryID\": {\n \"schemeID\": \"C\",\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"FRAFMLH\"\n }\n }\n ]\n },\n \"BusinessHeaderDocument\": {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"020-92560996\"\n },\n \"SenderAssignedID\": null,\n \"IncludedHeaderNote\": null,\n \"SignatoryConsignorAuthentication\": null,\n \"SignatoryCarrierAuthentication\": {\n \"ActualDateTime\": \"2016-05-16T00:00:00\",\n \"Signatory\": {\n \"languageID\": null,\n \"Value\": \"U168411\"\n },\n \"IssueAuthenticationLocation\": {\n \"Name\": {\n \"languageID\": null,\n \"Value\": \"NYC\"\n }\n }\n }\n },\n \"MasterConsignment\": {\n \"ID\": null,\n \"AdditionalID\": null,\n \"FreightForwarderAssignedID\": null,\n \"AssociatedReferenceID\": null,\n \"NilCarriageValueIndicator\": true,\n \"NilCarriageValueIndicatorSpecified\": true,\n \"DeclaredValueForCarriageAmount\": null,\n \"NilCustomsValueIndicator\": true,\n \"NilCustomsValueIndicatorSpecified\": true,\n \"DeclaredValueForCustomsAmount\": null,\n \"NilInsuranceValueIndicator\": true,\n \"NilInsuranceValueIndicatorSpecified\": true,\n \"InsuranceValueAmount\": null,\n \"TotalChargePrepaidIndicator\": true,\n \"TotalDisbursementPrepaidIndicator\": true,\n \"IncludedTareGrossWeightMeasure\": {\n \"unitCode\": \"KGM\",\n \"unitCodeSpecified\": true,\n \"Value\": 2.0\n },\n \"GrossVolumeMeasure\": {\n \"unitCode\": \"MTQ\",\n \"unitCodeSpecified\": true,\n \"Value\": 0.02\n },\n \"DensityGroupCode\": null,\n \"PackageQuantity\": null,\n \"TotalPieceQuantity\": {\n \"unitCodeSpecified\": false,\n \"Value\": 1.0\n },\n \"ProductID\": null,\n \"ConsignorParty\": {\n \"PrimaryID\": null,\n \"AdditionalID\": null,\n \"Name\": {\n \"languageID\": null,\n \"Value\": \"COLT MANUFACTURING ACER EXHIBTIS\"\n },\n \"AccountID\": null,\n \"PostalStructuredAddress\": {\n \"PostcodeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"21078\"\n },\n \"StreetName\": {\n \"languageID\": null,\n \"Value\": \"1601 CLEARK RD\"\n },\n \"CityName\": {\n \"languageID\": null,\n \"Value\": \"HAVRE DE GRACE\"\n },\n \"CountryID\": {\n \"schemeID\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeVersionID\": \"second edition 2006\",\n \"Value\": \"US\"\n },\n \"CountryName\": null,\n \"CountrySubDivisionName\": {\n \"languageID\": null,\n \"Value\": \"MD\"\n },\n \"PostOfficeBox\": null,\n \"CityID\": null,\n \"CountrySubDivisionID\": null,\n \"SpecifiedAddressLocation\": null\n },\n \"DefinedTradeContact\": null\n },\n \"ConsigneeParty\": {\n \"PrimaryID\": null,\n \"AdditionalID\": null,\n \"Name\": {\n \"languageID\": null,\n \"Value\": \"BLACK SEA DEFENSE AND AEROSAPCE\"\n },\n \"AccountID\": null,\n \"PostalStructuredAddress\": {\n \"PostcodeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"85214\"\n },\n \"StreetName\": {\n \"languageID\": null,\n \"Value\": \"CARE OF SCHENKER 65 67 MARASTI AVE\"\n },\n \"CityName\": {\n \"languageID\": null,\n \"Value\": \"BUCHAREST\"\n },\n \"CountryID\": {\n \"schemeID\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeVersionID\": \"second edition 2006\",\n \"Value\": \"RO\"\n },\n \"CountryName\": null,\n \"CountrySubDivisionName\": null,\n \"PostOfficeBox\": null,\n \"CityID\": null,\n \"CountrySubDivisionID\": null,\n \"SpecifiedAddressLocation\": null\n },\n \"DefinedTradeContact\": null\n },\n \"FreightForwarderParty\": {\n \"PrimaryID\": null,\n \"AdditionalID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"CAG\"\n },\n \"Name\": {\n \"languageID\": null,\n \"Value\": \"COSMIC LOGISTICS INC.\"\n },\n \"AccountID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"1696NYC\"\n },\n \"CargoAgentID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"0112294\"\n },\n \"FreightForwarderAddress\": {\n \"PostcodeCode\": null,\n \"StreetName\": null,\n \"CityName\": {\n \"languageID\": null,\n \"Value\": \"VALHALLA\"\n },\n \"CountryID\": null,\n \"CountryName\": null,\n \"CountrySubDivisionName\": null,\n \"PostOfficeBox\": null,\n \"CityID\": null,\n \"CountrySubDivisionID\": null\n },\n \"SpecifiedCargoAgentLocation\": {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"0011\"\n }\n },\n \"DefinedTradeContact\": null\n },\n \"AssociatedParty\": [\n {\n \"PrimaryID\": null,\n \"AdditionalID\": null,\n \"Name\": {\n \"languageID\": null,\n \"Value\": \"BLACK SEA DEFENSE AND AEROSAPCE\"\n },\n \"RoleCode\": {\n \"listID\": \"3035\",\n \"listAgencyID\": \"6\",\n \"listAgencyIDSpecified\": true,\n \"listVersionID\": \"D09A\",\n \"name\": null,\n \"Value\": \"NI\"\n },\n \"Role\": null,\n \"PostalStructuredAddress\": {\n \"PostcodeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"85214\"\n },\n \"StreetName\": {\n \"languageID\": null,\n \"Value\": \"CARE OF SCHENKER 65 67 MARASTI AVE\"\n },\n \"CityName\": {\n \"languageID\": null,\n \"Value\": \"BUCHAREST\"\n },\n \"CountryID\": {\n \"schemeID\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeVersionID\": \"second edition 2006\",\n \"Value\": \"RO\"\n },\n \"CountryName\": null,\n \"CountrySubDivisionName\": null,\n \"PostOfficeBox\": null,\n \"CityID\": null,\n \"CountrySubDivisionID\": null,\n \"SpecifiedAddressLocation\": null\n },\n \"DefinedTradeContact\": null\n }\n ],\n \"OriginLocation\": {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"JFK\"\n },\n \"Name\": null\n },\n \"FinalDestinationLocation\": {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"OTP\"\n },\n \"Name\": null\n },\n \"SpecifiedLogisticsTransportMovement\": [\n {\n \"StageCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"Main-Carriage\"\n },\n \"ModeCode\": {\n \"listID\": \"Recommendation 19\",\n \"listAgencyID\": \"6\",\n \"listAgencyIDSpecified\": true,\n \"listVersionID\": \"2\",\n \"name\": null,\n \"Value\": \"4\"\n },\n \"Mode\": {\n \"languageID\": null,\n \"Value\": \"AIR TRANSPORT\"\n },\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"LH0401\"\n },\n \"SequenceNumericSpecified\": false,\n \"UsedLogisticsTransportMeans\": {\n \"Name\": {\n \"languageID\": null,\n \"Value\": \"LH\"\n }\n },\n \"ArrivalEvent\": {\n \"ScheduledOccurrenceDateTime\": \"2016-05-16T00:00:00\",\n \"ScheduledOccurrenceDateTimeSpecified\": true,\n \"OccurrenceArrivalLocation\": {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"FRA\"\n },\n \"Name\": null,\n \"TypeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"Airport\"\n }\n }\n },\n \"DepartureEvent\": null\n },\n {\n \"StageCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"Main-Carriage\"\n },\n \"ModeCode\": {\n \"listID\": \"Recommendation 19\",\n \"listAgencyID\": \"6\",\n \"listAgencyIDSpecified\": true,\n \"listVersionID\": \"2\",\n \"name\": null,\n \"Value\": \"4\"\n },\n \"Mode\": {\n \"languageID\": null,\n \"Value\": \"AIR TRANSPORT\"\n },\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"LH1418\"\n },\n \"SequenceNumericSpecified\": false,\n \"UsedLogisticsTransportMeans\": {\n \"Name\": {\n \"languageID\": null,\n \"Value\": \"LH\"\n }\n },\n \"ArrivalEvent\": {\n \"ScheduledOccurrenceDateTime\": \"2016-05-17T00:00:00\",\n \"ScheduledOccurrenceDateTimeSpecified\": true,\n \"OccurrenceArrivalLocation\": {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"OTP\"\n },\n \"Name\": null,\n \"TypeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"Airport\"\n }\n }\n },\n \"DepartureEvent\": {\n \"ScheduledOccurrenceDateTimeSpecified\": false,\n \"OccurrenceDepartureLocation\": {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"FRA\"\n },\n \"Name\": null,\n \"TypeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"Airport\"\n }\n }\n }\n }\n ],\n \"UtilizedLogisticsTransportEquipment\": null,\n \"HandlingSPHInstructions\": [\n {\n \"Description\": null,\n \"DescriptionCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"ZXF\"\n }\n },\n {\n \"Description\": null,\n \"DescriptionCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"GEN\"\n }\n },\n {\n \"Description\": null,\n \"DescriptionCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"SPX\"\n }\n }\n ],\n \"HandlingSSRInstructions\": null,\n \"HandlingOSIInstructions\": null,\n \"IncludedAccountingNote\": null,\n \"IncludedCustomsNote\": [\n {\n \"ContentCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"M\"\n },\n \"Content\": {\n \"languageID\": null,\n \"Value\": \"NOEEI 30.37A\"\n },\n \"SubjectCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"EXP\"\n },\n \"CountryID\": {\n \"schemeID\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeVersionID\": \"second edition 2006\",\n \"Value\": \"US\"\n }\n },\n {\n \"ContentCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"M\"\n },\n \"Content\": {\n \"languageID\": null,\n \"Value\": \"16DE330262293676I8\"\n },\n \"SubjectCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"OCI\"\n },\n \"CountryID\": {\n \"schemeID\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeVersionID\": \"second edition 2006\",\n \"Value\": \"DE\"\n }\n }\n ],\n \"AssociatedReferenceDocument\": null,\n \"AssociatedConsignmentCustomsProcedure\": {\n \"GoodsStatusCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"T1\"\n }\n },\n \"ApplicableOriginCurrencyExchange\": {\n \"SourceCurrencyCode\": {\n \"listID\": \"ISO 4217 3A\",\n \"listAgencyID\": \"5\",\n \"listAgencyIDSpecified\": true,\n \"listVersionID\": \"2007-06-18\",\n \"listURI\": null,\n \"Value\": \"USD\"\n }\n },\n \"ApplicableDestinationCurrencyExchange\": null,\n \"ApplicableLogisticsServiceCharge\": {\n \"TransportPaymentMethodCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"PP\"\n },\n \"ServiceTypeCode\": null\n },\n \"ApplicableLogisticsAllowanceCharge\": [\n {\n \"ID\": {\n \"schemeID\": null,\n \"schemeName\": null,\n \"schemeAgencyIDSpecified\": false,\n \"schemeAgencyName\": null,\n \"schemeVersionID\": null,\n \"schemeDataURI\": null,\n \"schemeURI\": null,\n \"Value\": \"MR\"\n },\n \"AdditionalID\": null,\n \"PrepaidIndicator\": true,\n \"LocationTypeCode\": null,\n \"Reason\": null,\n \"PartyTypeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"C\"\n },\n \"ActualAmount\": {\n \"currencyIDSpecified\": false,\n \"Value\": 1.93\n },\n \"TimeBasisQuantity\": null,\n \"ItemBasisQuantity\": null,\n \"ServiceDateSpecified\": false,\n \"SpecialServiceDescription\": null,\n \"SpecialServiceTimeSpecified\": false\n }\n ],\n \"ApplicableRating\": [\n {\n \"TypeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"F\"\n },\n \"TotalChargeAmount\": {\n \"currencyIDSpecified\": false,\n \"Value\": 140.0\n },\n \"ConsignmentItemQuantity\": null,\n \"IncludedMasterConsignmentItem\": [\n {\n \"SequenceNumeric\": 1.0,\n \"TypeCode\": null,\n \"GrossWeightMeasure\": {\n \"unitCode\": \"KGM\",\n \"unitCodeSpecified\": true,\n \"Value\": 2.0\n },\n \"GrossVolumeMeasure\": {\n \"unitCode\": \"MTQ\",\n \"unitCodeSpecified\": true,\n \"Value\": 0.02\n },\n \"PackageQuantity\": null,\n \"PieceQuantity\": {\n \"unitCodeSpecified\": false,\n \"Value\": 1.0\n },\n \"VolumetricFactor\": null,\n \"Information\": null,\n \"NatureIdentificationTransportCargo\": {\n \"Identification\": {\n \"languageID\": null,\n \"Value\": \"EXHIBITION GOODS NOT RESTRICTED\"\n }\n },\n \"OriginCountry\": null,\n \"AssociatedUnitLoadTransportEquipment\": null,\n \"TransportLogisticsPackage\": [\n {\n \"ItemQuantity\": {\n \"unitCodeSpecified\": false,\n \"Value\": 1.0\n },\n \"GrossWeightMeasure\": {\n \"unitCode\": \"KGM\",\n \"unitCodeSpecified\": true,\n \"Value\": 2.0\n },\n \"LinearSpatialDimension\": {\n \"WidthMeasure\": {\n \"unitCode\": \"CMT\",\n \"unitCodeSpecified\": true,\n \"Value\": 30.0\n },\n \"LengthMeasure\": {\n \"unitCode\": \"CMT\",\n \"unitCodeSpecified\": true,\n \"Value\": 33.0\n },\n \"HeightMeasure\": {\n \"unitCode\": \"CMT\",\n \"unitCodeSpecified\": true,\n \"Value\": 18.0\n }\n }\n }\n ],\n \"ApplicableFreightRateServiceCharge\": {\n \"CategoryCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"M\"\n },\n \"CommodityItemID\": null,\n \"ChargeableWeightMeasure\": {\n \"unitCode\": \"KGM\",\n \"unitCodeSpecified\": true,\n \"Value\": 3.5\n },\n \"AppliedRate\": 140.0,\n \"AppliedAmount\": {\n \"currencyIDSpecified\": false,\n \"Value\": 140.0\n }\n },\n \"SpecifiedRateCombinationPointLocation\": null,\n \"ApplicableUnitLoadDeviceRateClass\": null\n }\n ]\n }\n ],\n \"ApplicableTotalRating\": [\n {\n \"TypeCode\": {\n \"listID\": null,\n \"listAgencyIDSpecified\": false,\n \"listAgencyName\": null,\n \"listName\": null,\n \"listVersionID\": null,\n \"name\": null,\n \"languageID\": null,\n \"listURI\": null,\n \"listSchemeURI\": null,\n \"Value\": \"F\"\n },\n \"ApplicableDestinationCurrencyServiceCharge\": null,\n \"ApplicablePrepaidCollectMonetarySummation\": [\n {\n \"PrepaidIndicator\": true,\n \"WeightChargeTotalAmount\": {\n \"currencyIDSpecified\": false,\n \"Value\": 140.0\n },\n \"ValuationChargeTotalAmount\": null,\n \"TaxTotalAmount\": null,\n \"AgentTotalDuePayableAmount\": null,\n \"CarrierTotalDuePayableAmount\": {\n \"currencyIDSpecified\": false,\n \"Value\": 1.93\n },\n \"GrandTotalAmount\": {\n \"currencyIDSpecified\": false,\n \"Value\": 141.93\n }\n }\n ]\n }\n ]\n }\n}"},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/mawb/{{:awbId}}/status","description":"Global API References:
\nRequirement Reference: EO.E8ACA.6
\nUse Case: Confirmed HAWB Ready/ Multiple HAWB for same Destination
\nDescription: Add additional confirmed HAWBs to existing MAWB consolidation.
\nProcess Flows:
\nConsignor System→ Air Cargo Agent System
\nConsignor System→ Air Cargo Agent System
\nPriority:
\nP1 (Integration)
\nP2 (External Systems)
\nRequirement References:
\nEO.E9ACA.10
\nEO.E10CGNR.11
\nG.E9ACA.3
\nUse Case: Send ASI (Advance Shipment Information) to Stakeholder
\nDescription: ACS will enable ACA to send ASI (advance shipment information) to GHA, Consignor, Airlines, Customs and Customs broker.
\nProcess Flows:
\nAirline system → Air Cargo Agent → Consignor System
\nAirline system → Air Cargo Agent → GHA System
\nPriority:
\nP1
\nP2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["advance-shipment-info"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"a51b38c5-2cd9-4140-8843-f9867025a53c"}],"id":"32156931-5fcb-4e04-ad53-4a460ded7ebe","_postman_id":"32156931-5fcb-4e04-ad53-4a460ded7ebe","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Transport Arrangement","item":[{"name":"Set Transport Arrangement","id":"65d51509-1656-4260-8429-0a018cf022fb","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/transport-arrangements","description":"Requirement Reference: EO.E11ACA.16
\nUse Case: ACS(ACA) is arranging transport to Airport
\nDescription: ACS (ACA) to inform GHA, that they will be arranging transport for the consignment.
\nTransport Options:
\naca - ACA will arrange trucking (Yes) → E11ACA → E12ACA
consignor - Consignor will arrange trucking (No) → E11ACA → E12CGNR
Process Flow: Air Cargo Agent System → Airport Community System → GHA System
\nPriority: P3
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["transport-arrangements"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"65d51509-1656-4260-8429-0a018cf022fb"}],"id":"834e4868-564a-4c14-a83a-3e3dbaefdbc2","_postman_id":"834e4868-564a-4c14-a83a-3e3dbaefdbc2","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Risk Assessment","item":[{"name":"Submit Risk Assessment (Customs)","id":"c655f94e-cd6a-4d44-a68f-636bb3f53b11","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/risk-assessments","description":"Requirement References:
\nEO.E11CUS.17
\nEO.E11GHA.18
\nG.E11GHA.6
\nUse Case: Risk Assessment Shared by Customs
\nRisk Classifications:
\ngreen - No inspection required
yellow - Document check required
red - Document + physical check of goods required
Process Flow: Web Based One Customs → Airport Community System → GHA System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["risk-assessments"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"c655f94e-cd6a-4d44-a68f-636bb3f53b11"},{"name":"Update Inspection Result","id":"2120c701-73a4-4046-ad41-d2fd1b2c0cd9","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"PATCH","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/risk-assessments/:assessmentId/inspection","description":"Requirement Reference: EO.E11CUS.17
\nUse Case: Risk Assessment Shared by Customs
\nDescription: Update risk assessment after inspection.
\nRisk Classifications:
\ngreen - No inspection required
yellow - Document check required
red - Document + physical check of goods required
Process Flow: Web Based One Customs → Airport Community System → GHA System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["risk-assessments",":assessmentId","inspection"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ra-2025-001234","key":"assessmentId"}]}},"response":[],"_postman_id":"2120c701-73a4-4046-ad41-d2fd1b2c0cd9"}],"id":"3069d189-cdba-4ba1-a68b-83ef5db28e27","_postman_id":"3069d189-cdba-4ba1-a68b-83ef5db28e27","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"37ba3df2-1c41-4c37-a60f-ca516312991d","_postman_id":"37ba3df2-1c41-4c37-a60f-ca516312991d","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Transport & TSM","item":[{"name":"Trucking Requests","item":[{"name":"Create Trucking Request","id":"8d2a78a1-1f04-4702-b2e6-9c1a091b5826","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/trucking-requests","description":"Requirement References:
\nEO.E12ACA.19
\nEO.E12CGNR.20
\nUse Case: Transport arranged by ACA/Consignor
\nDescription:
\nPickup Request: ACS enables ACA to contact and request a pickup quota from the Trucker
\nACS will enable the Consignor to communicate shipment details digitally to the Trucker.
\nProcess Flows:
\nAir Cargo Agent System → Airport Community System → Transporter / Truck Operator
\nConsignor System → Airport Community System → Transporter / Truck Operator
\nPriority: P3
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["trucking-requests"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"592eb4ca-ed3f-4863-bf6e-c8d1fb1278da","name":"Create Trucking Request (ACA)","originalRequest":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"body":{"mode":"raw","raw":"{\n \"requestedBy\": \"aca\",\n \"mawbNumber\": \"176-12345678\",\n \"hawbDetails\": [\n {\n \"hawbNumber\": \"176-12345689\",\n \"pieces\": 10,\n \"weight\": {\n \"value\": 500,\n \"unit\": \"KGM\"\n },\n \"commodity\": \"Electronics - Mobile Phones\",\n \"dimensions\": {\n \"volume\": 5,\n \"unit\": \"MTQ\"\n },\n \"shipper\": \"ABC Electronics Ltd\",\n \"consignee\": \"XYZ Trading LLC\"\n },\n {\n \"hawbNumber\": \"176-12345700\",\n \"pieces\": 20,\n \"weight\": {\n \"value\": 1000,\n \"unit\": \"KGM\"\n },\n \"commodity\": \"Textiles\",\n \"dimensions\": {\n \"volume\": 7.5,\n \"unit\": \"MTQ\"\n },\n \"shipper\": \"ABC Electronics Ltd\",\n \"consignee\": \"XYZ Trading LLC\"\n }\n ],\n \"pickup\": {\n \"address\": \"123 Industrial Area, Site, Karachi\",\n \"city\": \"Karachi\",\n \"postalCode\": \"74000\",\n \"contactPerson\": \"Ahmed Khan\",\n \"contactPhone\": \"+92-21-12345678\",\n \"requestedTime\": \"2025-11-24T09:00:00+05:00\"\n },\n \"delivery\": {\n \"airport\": \"KHI\",\n \"ghaName\": \"Pakistan Airport Services\",\n \"requestedTime\": \"2025-11-24T14:00:00+05:00\"\n },\n \"shipmentDetails\": {\n \"numberOfPieces\": 10,\n \"weight\": {\n \"value\": 500,\n \"unit\": \"KGM\"\n },\n \"dimensions\": {\n \"length\": 120,\n \"width\": 80,\n \"height\": 100,\n \"unit\": \"CMT\"\n },\n \"commodity\": \"Electronics\",\n \"specialRequirements\": \"Handle with care - Fragile\"\n },\n \"acaContact\": {\n \"name\": \"Freight Manager\",\n \"phone\": \"+92-21-9876543\"\n },\n \"targetTruckers\": [\n \"trucker-001\",\n \"trucker-002\"\n ],\n \"quoteRequired\": true,\n \"quoteExpiredAt\": \"2025-11-23T18:00:00Z\"\n}"},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/trucking-requests"},"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":null},{"id":"307377d1-4110-4fd3-b0d9-8ed75b904f99","name":"Create Trucking Request (ACA)","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: EO.E12TRK.21
\nUse Case: Shipment and delivery details received, vehicle information sent.
\nDescription: ACS will enable the Trucker to prepare and send a price proposal digitally to ACA or Consignor.
\nProcess Flows:
\nAir Cargo Agent System → Airport Community System → Transporter / Truck Operator
\nConsignor System → Airport Community System → Transporter / Truck Operator
\nPriority: P3
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["trucking-requests",":requestId","quote"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"tr-req-001","key":"requestId"}]}},"response":[],"_postman_id":"8cf2c181-ed83-461b-87f0-6651fdc02883"},{"name":"Accept/Reject Quote (ACA/Consignor)","id":"0c0b872e-0751-4fc7-be7b-012789c6ee27","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/trucking-requests/:requestId/quote-response","description":"Requirement Reference: EO.E12TRK.21
\nUse Case: Shipment and delivery details received, vehicle information sent.
\nDescription: ACS will enable the Consignor or ACA to receive the price proposal, review it, and send confirmation digitally.
\nProcess Flows:
\nAir Cargo Agent System → Airport Community System → Transporter / Truck Operator
\nConsignor System → Airport Community System → Transporter / Truck Operator
\nPriority: P3
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["trucking-requests",":requestId","quote-response"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"tr-req-001","key":"requestId"}]}},"response":[],"_postman_id":"0c0b872e-0751-4fc7-be7b-012789c6ee27"},{"name":"Confirm Vehicle Details (Trucker)","id":"895b8162-2ab8-4b63-8d9d-686910cf8bb2","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/trucking-requests/:requestId/vehicle-confirmation","description":"Requirement Reference: EO.E12TRK.21
\nUse Case: Shipment and delivery details received, vehicle information sent.
\nDescription: ACS will enable the Trucker to reply with confirmation, including price, date, vehicle, and driver details, in digital format.
\nProcess Flows:
\nTransporter / Truck Operator → Airport Community System → Air Cargo Agent System
\nTransporter / Truck Operator→ Airport Community System → Consignor System
\nPriority: P3
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["trucking-requests",":requestId","vehicle-confirmation"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"tr-req-001","key":"requestId"}]}},"response":[],"_postman_id":"895b8162-2ab8-4b63-8d9d-686910cf8bb2"}],"id":"1c49de73-e657-4bd9-9760-e170931313ff","_postman_id":"1c49de73-e657-4bd9-9760-e170931313ff","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"TSM Slot Request","item":[{"name":"Request TSM Slot","id":"467de1e7-59bf-4342-9685-d607e1166754","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/tsm/slot-requests","description":"Requirement References:
\nEO.E13ACA.22
\nEO.E13CGNR.23
\nG.E13ACA.8
\nUse Case:
\nObtain TSM delivery slot (time & dock number) and receive vehicle token.
\nTransmission of vehicle & delivery day for Truck Slot Management (TSM) booking
\nDescription:
\nACS will enable ACA to digitally transmit vehicle details to GHA and request an unloading slot.
\nACS will enable ACA to transmit to GHA vehicle details and request unloading slot in digital format.
\nProcess Flows:
\nAir Cargo Agent System → Airport Community System → GHA System
\nConsignor System → Airport Community System → GHA System
\nPriority:
\nP1 (Integration)
\nP2 (External Systems)
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["tsm","slot-requests"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"467de1e7-59bf-4342-9685-d607e1166754"}],"id":"34c586ad-c057-471f-b6fe-d445ef3ffde4","_postman_id":"34c586ad-c057-471f-b6fe-d445ef3ffde4","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"GHA Slot Assignment","item":[{"name":"Assign TSM Slot (GHA)","id":"1261942b-31c8-433f-ac9d-4ba00fb97459","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/tsm/slot-assignments","description":"Requirement Reference:
\nEO.E13GHA.24
\nG.E13GHA.10
\nUse Case: Receive vehicle details, assign time & dock via TSM, and create vehicle token
\nDescription:
\nACS will enable GHA to receive vehicle information digitally from ACA or Consignor
\nACS will enable GHA to assign time and dock through TSM in ACS and share it with ACA
\nACS will enable GHA to create a vehicle token in ACS and transmit it digitally to ACA or Consignor
\nIf GHA lacks infrastructure or IT capacity to run TSM, ACS will enable GHA to operate TSM via ACS
\nProcess Flows:
\nGHA System → Airport Community System → Air Cargo Agent System
\nGHA System → Airport Community System → Consignor System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["tsm","slot-assignments"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"1261942b-31c8-433f-ac9d-4ba00fb97459"},{"name":"Update Slot Assignment","id":"dcc2376c-be58-4380-9307-7be4cc721554","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"PATCH","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/tsm/slot-assignments/:assignmentId","description":"Requirement Reference: EO.E13GHA.24
\nUse Case: Receive vehicle details, assign time & dock via TSM, and create vehicle token.
\nDescription: Update slot assignment.
\nProcess Flows:
\nGHA System → Airport Community System → Air Cargo Agent System
\nGHA System → Airport Community System → Consignor System
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["tsm","slot-assignments",":assignmentId"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"slot-assign-001","key":"assignmentId"}]}},"response":[],"_postman_id":"dcc2376c-be58-4380-9307-7be4cc721554"}],"id":"a413b205-c3be-4d1b-a313-4ecf7a9aa739","_postman_id":"a413b205-c3be-4d1b-a313-4ecf7a9aa739","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Trucker Slot Receipt","item":[{"name":"Acknowledge Slot Receipt","id":"25d07670-afba-423b-8004-342a3ae38402","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/tsm/slot-assignments/:assignmentId/acknowledge","description":"Requirement Reference: EO.E14TRK.25
\nUse Case: Delivery Slot information received
\nDescription: Trucker acknowledges slot receipt and provides ETA.
\nProcess Flow: GHA System → Airport Community System → Transporter / Truck Operator
\nPriority:
\nP1
\nP2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["tsm","slot-assignments",":assignmentId","acknowledge"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"slot-assign-001","key":"assignmentId"}]}},"response":[],"_postman_id":"25d07670-afba-423b-8004-342a3ae38402"}],"id":"5d93cf0d-b78d-480b-8066-6a97254eb20a","_postman_id":"5d93cf0d-b78d-480b-8066-6a97254eb20a","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"38dae52b-406e-4f58-99af-1bb78f976573","_postman_id":"38dae52b-406e-4f58-99af-1bb78f976573","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Airport Operations","item":[{"name":"Vehicle Arrival","item":[{"name":"Report Vehicle Arrival","id":"5b582a7a-382a-468f-a7b8-e392184e2c40","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/vehicle-arrivals","description":"Requirement References:
\nEO.E15TRK.26
\nG.E15GHA.11
\nG.E15TRK.12
\nUse Case: Vehicle arrives at the Airport
\nDescription: ACS will enable Trucker to send this arrival at the airport information in digital format.
\nArrival Methods:
\nQR token scan at gate
\nACS portal check-in
\nMobile application (Geofencing)
\nProcess Flows:
\nTransporter / Truck Operator → Airport Community System→ GHA System
\nTransporter / Truck Operator → Airport Community System→ Air Cargo Agent System
\nTransporter / Truck Operator → Airport Community System→ Consignor System
\nPriority:
\nP1 (Broadcast)
\nP2 (External Systems)
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["vehicle-arrivals"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"5b582a7a-382a-468f-a7b8-e392184e2c40"},{"name":"Confirm Cargo Unloading (GHA)","id":"f5714a26-6e32-4c5e-b611-27eae66565a0","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/vehicle-arrivals/:arrivalId/unloading-confirmation","description":"Requirement Reference: EO.E15TRK.26
\nUse Case: Vehicle arrives at the Airport
\nDescription: GHA confirms cargo unloading completion.
\nProcess Flows:
\nTransporter / Truck Operator → Airport Community System→ GHA System
\nTransporter / Truck Operator → Airport Community System→ Air Cargo Agent System
\nTransporter / Truck Operator → Airport Community System→ Consignor System
\nPriority:
\nP1 (Broadcast)
\nP2 (External Systems)
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["vehicle-arrivals",":arrivalId","unloading-confirmation"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"arr-20251124-001","key":"arrivalId"}]}},"response":[],"_postman_id":"f5714a26-6e32-4c5e-b611-27eae66565a0"}],"id":"1161c298-2e32-4aaa-b4f6-6f959ed0bbb2","_postman_id":"1161c298-2e32-4aaa-b4f6-6f959ed0bbb2","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Mail Operations","item":[{"name":"Report Mail Arrival","id":"c5233695-97e7-41a5-a3e3-64670e86358f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/mail/arrivals","description":"Requirement Reference: EO.E17P.30
\nUse Case: Mail arrives at airport post facilities
\nDescription: ACS will enable Pakistan Post to share mail arrival at airport information with relevant stakeholders.
\nProcess Flows:
\nPakistan Post → Airport Community System → GHA System
\nPakistan Post → Airport Community System → Airline System
\nPriority:
\nP1 (Push)
\nP2 (External Systems)
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["mail","arrivals"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"c5233695-97e7-41a5-a3e3-64670e86358f"},{"name":"Submit X-ray Scan Results","id":"d71d85a5-5963-4b93-946f-625b0d8b5cc7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/mail/xray-scans","description":"Requirement Reference: EO.E18P.31
\nUse Case: Mail scanned by X-ray and accepted
\nDescription: ACS to enable Pakistan Post to digitally transmit X-ray scans of mail bags to PSW and ANF.
\nProcess Flows:
\nPakistan Post → Airport Community System → Anti-Narcotics Force System
\nPakistan Post → Airport Community System → Pakistan Single Window
\nPriority:
\nP1 (Push)
\nP2 (External Systems)
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["mail","xray-scans"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"d71d85a5-5963-4b93-946f-625b0d8b5cc7"},{"name":"Update Mail Bag Status","id":"792f1e20-2dd2-4ca4-aba8-a7fcc3086bc6","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"PATCH","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/mail/bags/:bagNumber/status","description":"Requirement Reference: EO.E18P.31
\nUse Case: Update mail bag status after inspection.
\nActors: Customs, ANF
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["mail","bags",":bagNumber","status"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"PKKHI20251124002","key":"bagNumber"}]}},"response":[],"_postman_id":"792f1e20-2dd2-4ca4-aba8-a7fcc3086bc6"}],"id":"27d5a186-36c1-4a6c-ad1b-eb4a958f6b8c","_postman_id":"27d5a186-36c1-4a6c-ad1b-eb4a958f6b8c","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Flight Manifest (PAA)","item":[{"name":"Submit Flight Manifest and Departure Message","id":"c12aade9-01b8-4c1c-8685-c168361af926","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/flight-manifests","description":"Global API References:
\n\nRequirement References:
\nEO.E36PAA.32
\nEO.E37PAA.33
\nEO.E38PAA.34
\nUse Case: Flight Manifest and Departure Messages Received (Statistical Purposes)
\nDescription: ACS will enable PAA to receive Flight manifest data including departure message in digital format for statistical purpose.
\nDigital Information:
\nFlight Manifest information (FFM data set)
\nDEP message (FSU data set)
\nProcess Flow: Postal Aviation Authority System → Airport Community System → GHA System
\nPriority:
\nP1
\nP2
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"e963062a-057a-416c-bab3-9f95508256b4"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/flight-bookings/receipts","description":"Global API Reference:
\nRequirement Reference: G.E7AL.1, G.E7GHA.2
\nUse Case: Send and Receive Flight Booking List
\nDescription: Airline sends & GHA receives Flight Booking List
\nProcess Flow: Airline → ACS → GHA
\nPriority: P1 (Critical Integration)
\nActors: Airline, ACS, GHA
\nAction:
\nPUSH
\nPOST
\nMessage Formats: JSON (this endpoint), IATA Cargo-XML (XFBL), IATA Cargo-IMP (FBL)
\nBusiness Context:
The Flight Booking List (FBL) is sent by airlines to GHA to inform them of all confirmed cargo bookings on a specific flight. This allows GHA to:
Pre-plan warehouse space and handling resources
\nPrepare ULDs (Unit Load Devices) for cargo loading
\nSchedule manpower for cargo acceptance
\nCoordinate with ACAs for delivery time slots
\nIdentify special handling requirements (dangerous goods, perishables, valuables)
\nThe FBL is typically sent 24-48 hours before flight departure and may be updated if bookings change.
\nValidation Rules:
\nFlight date must be in the future
\nOrigin and destination must be valid IATA airport codes
\nMAWB numbers must follow format: 3-digit prefix + hyphen + 8-digit serial
\nTotal pieces/weight/volume must match sum of individual bookings
\nSpecial handling codes must be valid IATA codes
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","flight-bookings","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"28c3655a-9a5e-484a-a6a9-a7cd04b57fee"},{"name":"Flight Booking List (IATA XML XFBL)","id":"b8e8b2ee-93db-4f37-be2d-e8dff03c32d4","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"6e52f2c9-18a5-4ce5-be3a-368fa30c5e8e"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/flight-bookings/receipts/xfbl","description":"Global API Reference:
\nRequirement Reference: G.E7AL.1, G.E7GHA.2
\nUse Case : Send and Receive Flight Booking List
\nDescription: Airline sends & GHA receives Flight Booking List
\nProcess Flow: Airline system→ ACS → GHA
\nPriority: P1 (Critical Integration)
\nActors: Airline, ACS, GHA
\nMessage Formats: IATA Cargo-XML (XFBL)
\nBusiness Context:
XFBL (Flight Booking List) is the IATA Cargo-XML standard format for transmitting flight booking information. This format is widely used by:
Modern airline cargo systems
\nGround handling systems
\nCargo community systems worldwide
\nThe XML format provides structured data with schema validation, ensuring data integrity and interoperability between different airline and GHA systems.
\nXML Schema: IATA Cargo-XML 3.00 XFBL message
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","flight-bookings","receipts","xfbl"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"b8e8b2ee-93db-4f37-be2d-e8dff03c32d4"},{"name":"Flight Booking List (IATA IMP FBL)","id":"17d30b8a-4922-46c1-afa7-df874e4094eb","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"16d38495-a05e-4d54-8745-175d8354e166"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/flight-bookings/receipts/fbl","description":"Global API Reference:
\nRequirement Reference: G.E7AL.1, G.E7GHA.2
\nUse Case: Send and Receive Flight Booking List
\nDescription: Airline sends & GHA receives Flight Booking List
\nProcess Flow: Airline system → ACS → GHA
\nPriority: P1 (Critical Integration)
\nActors: Airline, ACS, GHA
\nMessage Formats: IATA Cargo-IMP (FBL)
\nBusiness Context:
FBL (Flight Booking List) in IATA Cargo-IMP format is the legacy but widely-used format for flight booking information. Many airlines and GHA systems still use this format due to:
Backward compatibility with older systems
\nCompact message size for bandwidth efficiency
\nWidespread adoption across the industry
\nThe format is cryptic but follows strict IATA standards defined in the Cargo-IMP manual.
\nAPI Example Parameters:
\nFBL Format Structure:
\nFBL\n<Flight>/<Date>.<Origin><Destination>\n<AWB>/<Pieces><Weight><Volume>/<Commodity>/<SpecialHandling>\n\nIATA Cargo-IMP Codes:
\nWeight units: K=kg, L=lb
\nVolume units: MC=cubic meters, CF=cubic feet
\nCommodity prefixes: N=Nature of goods
\nSpecial handling prefixes: S=Special handling code
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"fbl-imp-001\",\n \"format\": \"IATA_CARGO_IMP\",\n \"messageType\": \"FBL\",\n \"flightNumber\": \"EK-606\",\n \"flightDate\": \"2025-11-28\",\n \"totalBookings\": 1,\n \"status\": \"RECEIVED\",\n \"parsedSuccessfully\": true,\n \"receivedAt\": \"2025-11-27T10:15:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T10:15:00Z\",\n \"requestId\": \"req-fbl-imp-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"INVALID_FBL_FORMAT\",\n \"message\": \"FBL message format is invalid - does not conform to IATA Cargo-IMP standards\",\n \"details\": [\n {\n \"field\": \"line2\",\n \"issue\": \"Invalid AWB number format - expected prefix-serial (e.g., 176-12345678)\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T10:15:00Z\",\n \"requestId\": \"req-fbl-imp-001\"\n }\n}\n\nStatus Codes:
\n201: FBL message received and parsed
\n400: Invalid IMP format
\n401: Unauthorized
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"0fec38d3-27b8-42c5-bceb-d53cd4e24eb1"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/asi-submissions/receipts","description":"**to merge with [**link] POST Send ASI toStakeholders
---
Requirement Reference:
G.E9ACA.3, G.E10GHA.4, G.E11CUS.5
\nEO.E9ACA.10, EO.E10GHA.13
\nUse Case: Distribute Advanced Shipment Information
\nDescription: ACS will enable ACA to send ASI (advanced shipment information) to GHA, Consignor, Airlines, Customs and Customs broker.
\nProcess Flow:
\nACA → Consignor
\nAirline system → ACA → Consignor
\nAirline system → ACA → Customs broker
\nAirline system → ACA → GHA
\nAirline system → ACA → Customs
\nPriority: P1 (Critical Integration)
\nActors: ACA (via ACS) → GHA, Consignor, Airlines, Customs, Customs Broker
\nAuthentication: OAuth 2.0 JWT Bearer token (ACA role required)
\nBusiness Rules:
\nASI must be submitted before cargo arrives at GHA facility
\nHAWB and MAWB numbers must be valid and match flight booking
\nShipper and consignee details must be complete
\nCommodity description required for customs clearance
\nHS code required for international shipments
\nWeight and dimensions must match booking information
\nACS validates ASI data before acceptance
\nMessage Formats: JSON (primary)
\nValidation Rules:
\nRequired fields: hawbNumber, mawbNumber, flightNumber, shipper, consignee, cargo
\nAWB format: {prefix}-{8-digit-serial}
\nHAWB format: {aca-code}-{serial}
\nPhone numbers: International format with country code
\nEmail: Valid email format
\nWeight: Positive number
\nHS Code: Valid 4-10 digit code
\nACS Processing:
\nValidates ASI data completeness
\nStores ASI in ACS database
\nGenerates unique ASI reference ID
\nTriggers broadcast push to all stakeholders (IP #34)
\nReturns confirmation with ASI ID
\nBroadcast Distribution (Automatic):
\nPush to GHA: POST /asi-submissions/:id/push/gha
\nPush to Consignor: POST /asi-submissions/:id/push/consignor
\nPush to Airline: POST /asi-submissions/:id/push/airline
\nPush to Customs: POST /asi-submissions/:id/push/customs
\nPush to Customs Broker: POST /asi-submissions/:id/push/customs-broker
\nUse Cases:
\nACA submits advance shipment information before cargo delivery
\nEnables all stakeholders to prepare for cargo arrival
\nFacilitates customs pre-clearance
\nSupports GHA resource planning
\n*API Parameters:__*
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","asi-submissions","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"b239d1e2-3dc7-45d3-a84f-8446fd8bd458","name":"Success - ASI Received","originalRequest":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"ad999c8a-70e4-4f7a-a221-b017e7729a73"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"8ac9d229-752a-404d-ba0b-9a143d3f8d83"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/risk-assessments/receipts","description":"**to merge with [**link**] POST Submit Risk Assesment (Customs)
--
Requirement Reference**: EO.E11CUS.17, EO.E11GHA.18, G.E11GHA.6
\nUse Case: Receive Risk Assessment
\nDescription: ACS (Customs) to share risk assessment classification assignment for each consignment and item with EPO and GHA digitally.
\nProcess Flow:
\nPriority: P1 (Critical Integration)
\nActors: Customs (WeBOC) → ACS → GHA
\nAuthentication: OAuth 2.0 JWT Bearer token (Customs role required)
\nBusiness Rules:
\nRisk assessment performed by WeBOC based on ASI data
\nThree risk classifications: GREEN (low), YELLOW (medium), RED (high)
\nDecision types: LOAD, DOCUMENT_CHECK, PHYSICAL_INSPECTION, DO_NOT_LOAD
\nAssessment must reference valid ASI submission
\nGHA uses classification to determine cargo handling procedures
\nRED classification requires physical inspection before loading
\nYELLOW classification requires document verification
\nGREEN classification allows immediate loading
\nRisk Classifications:
\nGREEN (Low Risk):
\nDecision: LOAD (proceed with loading)
\nNo additional checks required
\nStandard handling procedures
\nFast-track clearance
\nYELLOW (Medium Risk):
\nDecision: DOCUMENT_CHECK (document verification required)
\nAdditional documentation may be requested
\nReview by customs officer
\nMay require clarifications from shipper
\nRED (High Risk):
\nDecision: PHYSICAL_INSPECTION or DO_NOT_LOAD
\nPhysical examination required
\nX-ray scanning mandatory
\nPossible EDD (Explosive Detection Dog) or ETD (Explosive Trace Detection)
\nCannot load without customs clearance
\nAssessment Criteria:
\nCommodity risk (based on HS code and description)
\nShipper history and compliance record
\nConsignee verification status
\nDestination country risk level
\nDeclared value vs typical value
\nSpecial handling requirements
\nHistorical anomalies
\nACS Processing:
\nValidates risk assessment data from WeBOC
\nStores assessment in ACS database
\nLinks to corresponding ASI submission
\nTriggers push to GHA system (IP #43)
\nNotifies relevant stakeholders
\nReturns confirmation
\nSubsequent Actions:
\nACS automatically pushes to GHA via POST /risk-assessments/:id/push/gha
\nGHA adjusts cargo handling based on classification
\nRED/YELLOW: GHA coordinates with customs for inspection
\nGREEN: GHA proceeds with standard loading procedures
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","risk-assessments","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"00d3618a-7bfc-460e-be50-786c1707816e","name":"Success - Risk Assessment Received","originalRequest":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"Content-Type","value":"application/json"},{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"X-Request-ID","value":"777fa11b-f85d-465d-bf23-c4e280688da7"}],"body":{"mode":"raw","raw":"{\n \"gdNumber\": \"GD-EXP-2025-001234\",\n \"mawbNumber\": \"176-12345678\",\n \"hawbAssessments\": [\n {\n \"hawbNumber\": \"KHI12345678\",\n \"riskClassification\": \"green\",\n \"remarks\": \"No inspection required\"\n },\n {\n \"hawbNumber\": \"KHI12345679\",\n \"riskClassification\": \"yellow\",\n \"remarks\": \"Document check required\",\n \"requiredDocuments\": [\"Commercial Invoice\", \"Packing List\"]\n }\n ],\n \"overallClassification\": \"yellow\",\n \"assessedBy\": \"customs-officer-001\",\n \"assessedAt\": \"2025-11-21T14:00:00Z\",\n \"validUntil\": \"2025-11-25T23:59:59Z\"\n}"},"url":"https://api.psw.gov.pk/api/v1/export/risk-assessments/receipts","description":"**to merge with \\[**[link](https://postman.belli.app/#4b36df3d-2a91-4320-809a-3af7249b350f)**\\] POST Submit Risk Assesment (Customs) \n\\--\n\nRequirement Reference**: EO.E11CUS.17, EO.E11GHA.18, G.E11GHA.6\n\n**Use Case**: Receive Risk Assessment\n\n**Description:** ACS (Customs) to share risk assessment classification assignment for each consignment and item with EPO and GHA digitally.\n\n**Process Flow**:\n\n- Customs → ACA → GHA\n \n\n**Priority**: P1 (Critical Integration)\n\n**Actors**: Customs (WeBOC) → ACS → GHA\n\n**Authentication**: OAuth 2.0 JWT Bearer token (Customs role required)\n\n**Business Rules**:\n\n- Risk assessment performed by WeBOC based on ASI data\n \n- Three risk classifications: GREEN (low), YELLOW (medium), RED (high)\n \n- Decision types: LOAD, DOCUMENT_CHECK, PHYSICAL_INSPECTION, DO_NOT_LOAD\n \n- Assessment must reference valid ASI submission\n \n- GHA uses classification to determine cargo handling procedures\n \n- RED classification requires physical inspection before loading\n \n- YELLOW classification requires document verification\n \n- GREEN classification allows immediate loading\n \n\n**Risk Classifications**:\n\n1. **GREEN** (Low Risk):\n \n - Decision: LOAD (proceed with loading)\n \n - No additional checks required\n \n - Standard handling procedures\n \n - Fast-track clearance\n \n2. **YELLOW** (Medium Risk):\n \n - Decision: DOCUMENT_CHECK (document verification required)\n \n - Additional documentation may be requested\n \n - Review by customs officer\n \n - May require clarifications from shipper\n \n3. **RED** (High Risk):\n \n - Decision: PHYSICAL_INSPECTION or DO_NOT_LOAD\n \n - Physical examination required\n \n - X-ray scanning mandatory\n \n - Possible EDD (Explosive Detection Dog) or ETD (Explosive Trace Detection)\n \n - Cannot load without customs clearance\n \n\n**Assessment Criteria**:\n\n- Commodity risk (based on HS code and description)\n \n- Shipper history and compliance record\n \n- Consignee verification status\n \n- Destination country risk level\n \n- Declared value vs typical value\n \n- Special handling requirements\n \n- Historical anomalies\n \n\n**ACS Processing**:\n\n1. Validates risk assessment data from WeBOC\n \n2. Stores assessment in ACS database\n \n3. Links to corresponding ASI submission\n \n4. Triggers push to GHA system (IP #43)\n \n5. Notifies relevant stakeholders\n \n6. Returns confirmation\n \n\n**Subsequent Actions**:\n\n- ACS automatically pushes to GHA via POST /risk-assessments/:id/push/gha\n \n- GHA adjusts cargo handling based on classification\n \n- RED/YELLOW: GHA coordinates with customs for inspection\n \n- GREEN: GHA proceeds with standard loading procedures\n \n\nAPI Parameters:\n\n| Field Name | Field Type | Field Length | Condition | Field Validation Rule |\n| --- | --- | --- | --- | --- |\n| gdNumber | String | Variable | M | Format: GD-EXP--, e.g., GD-EXP-2025-001234 |\n| mawbNumber | String | Variable | M | Format: nnn-nnnnnnnn, e.g., \"176-12345678\" |\n| hawbAssessments | Array | Variable | M | Array of objects, each containing hawbNumber, riskClassification, remarks |\n| hawbAssessments.hawbNumber | String | 35 | M | Format: nnn-nnnnnnnn, e.g., \"KHI12345678\" |\n| hawbAssessments.riskClassification | String | 10 | M | Possible values: \"green\", \"yellow\", \"red\" |\n| hawbAssessments.remarks | String | Variable | M | Remarks about the assessment |\n| hawbAssessments.requiredDocuments | Array | Variable | O | Array of documents required for inspection, e.g., \\[\"Commercial Invoice\", \"Packing List\"\\] |\n| overallClassification | String | 10 | M | Possible values: \"green\", \"yellow\", \"red\" |\n| assessedBy | String | 50 | M | Identifier of the person who made the assessment |\n| assessedAt | String | ISO 8601 DateTime | M | Date and time of the assessment (e.g., \"2025-11-21T14:00:00Z\") |\n| validUntil | String | ISO 8601 DateTime | M | Date and time the assessment is valid until (e.g., \"2025-11-25T23:59:59Z\") |"},"status":"Created","code":201,"_postman_previewlanguage":"Text","header":[{"key":"Content-Type","value":"application/json"},{"key":"Location","value":"/api/v1/export/risk-assessments/risk-khi-2025-11-26-001"}],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"risk-khi-2025-11-26-001\",\n \"assessmentReference\": \"RISK-KHI-2025-11-26-001\",\n \"asiReference\": \"ASI-KHI-2025-11-26-001\",\n \"hawbNumber\": \"SKL-00012345\",\n \"mawbNumber\": \"214-98765432\",\n \"riskClassification\": \"GREEN\",\n \"decision\": \"LOAD\",\n \"totalRiskScore\": 23,\n \"status\": \"RECEIVED\",\n \"receivedDateTime\": \"2025-11-26T11:00:05+05:00\",\n \"pushedToGHA\": true,\n \"ghaPushDateTime\": \"2025-11-26T11:00:08+05:00\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-26T11:00:05+05:00\",\n \"requestId\": \"req-risk-123456\"\n }\n}"},{"id":"dcdfe67b-5e6b-4a8f-a31b-177daa2f34f0","name":"Error - ASI Not Found","originalRequest":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"3a7fe690-a58e-438a-80a7-4a759c3957a1"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"512d7314-ae96-45f0-8233-0f2f7f867cee"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/tsm-requests/receipts","description":"Requirement Reference: G.E13ACA.8, G.E13CGNR.9
\nUse Case: Request Truck Delivery Slot
\nDescription: ACS will enable ACA to digitally transmit vehicle details to GHA and request an unloading slot.
\nProcess Flows:
\nACA → GHA
\nACA → GHA
\nPriority: P1 (Critical Integration)
\nActors: ACA → ACS → GHA
\nMessage Formats: JSON
\nBusiness Rules:
\nVehicle registration must be valid Pakistan format (CITY-NNNN)
\nDriver CNIC must be valid 13-digit Pakistan CNIC (NNNNN-NNNNNNN-N)
\nRequested time window must be during GHA operating hours (typically 06:00-22:00)
\nTSM request must be submitted at least 2 hours before requested time
\nACA must have active flight booking for the specified MAWB/HAWB
\nResponse Codes:
\n201 Created: TSM request received and forwarded to GHA
\n400 Bad Request: Invalid vehicle details or time window
\n401 Unauthorized: Invalid or missing authentication
\n409 Conflict: Duplicate TSM request reference
\n422 Unprocessable Entity: Validation errors (invalid CNIC, registration, etc.)
\nBusiness Rules:
\nConsignor must have registered shipment in ACS
\nDirect delivery by consignor (not via ACA)
\nVehicle and driver details mandatory for security clearance
\nConsignor can request specific time window based on production schedule
\nGHA will validate consignor authorization before slot assignment
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","tsm-requests","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"1fa37447-3328-4075-93d7-d2cc1eb1a52a","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"ca165785-e64a-482c-bc0f-b3e2c26c33f8"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"492667c7-2223-4eb2-a40c-49517b69a442"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/tsm-slots","description":"to merge with [**link] POST Assign TSM Slot (GHA)
--
Requirement Reference: EO.E13GHA.24, G.E13GHA.10
Use Case: Process Truck Slot
\nDescription: ACS will enable the Consignor to request unloading slot allocation from GHA in digital format.
\nProcess Flow: E13GHA
\nPriority: P1 (Critical)
\nActors: GHA
\nMessage Formats: JSON
\nVehicle Token Types:
\nQR_CODE: Scannable QR code for automated gate entry (primary method)
\nSMS: 6-digit code sent to driver's mobile (backup method)
\nAPP: JWT token for mobile app-based check-in (future enhancement)
\nBusiness Rules:
\nGHA assigns slot based on availability and cargo type
\nVehicle token is unique and single-use
\nToken validity typically 2 hours (to allow some flexibility)
\nToken includes embedded data: Date, Dock, AWB, Vehicle Registration
\nQR code is primary method, SMS is backup if scanner unavailable
\nToken expires if vehicle doesn't arrive within validity period
\nGHA can extend token validity if truck delayed due to traffic
\nTSM Slot Assignment Logic:
\nSlots allocated in 30-60 minute windows based on cargo volume
\nDangerous goods assigned to dedicated docks with safety equipment
\nHeavy cargo (>1000kg) assigned to docks with forklifts/cranes
\nTemperature-controlled cargo assigned to climate-controlled docks
\nPeak hours (09:00-12:00, 14:00-17:00) may have longer wait times
\nResponse Codes:
\n201 Created: Slot assigned and token generated
\n400 Bad Request: Invalid TSM request ID
\n409 Conflict: Requested slot unavailable, suggest alternatives
\n422 Unprocessable Entity: Cannot assign slot (e.g., no suitable dock)
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","tsm-slots"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"804d1c1f-ae97-4dc7-ad7f-09f74e20cb36","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)","key":"X-Request-ID","value":"91612244-f26b-4bec-b6a2-1136845e20d1"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"a75cb50d-28d1-4cb8-b792-f8bd3a8d7240"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/vehicle-arrivals/validations","description":"Requirement Reference: G.E15GHA.11
\nUse Case: Validate Vehicle Arrival
\nDescription: GHA validates vehicle token at arrival
\nProcess Flow:
\nGHA → ACA → Customs Broker
\nGHA → ACA → Consignor system
\nGHA → ACA → Customs Broker
\nPriority: P1 (Critical Integration)
\nActors: GHA (gate staff)
\nBusiness Rules:
\nVehicle token must be valid and not previously used
\nToken expiry = assigned slot time + 2 hours + 30 min grace period
\nDriver CNIC must match CNIC in token data
\nVehicle registration must match registration in token data
\nArrival time must be within valid token window
\nGate number must match assigned gate
\nDock number must match assigned dock
\nToken is marked as USED after successful validation
\nCannot revalidate used token (prevents duplicate entries)
\nGrace period allows for traffic delays
\nToken Types:
\nQR_CODE (Primary):
\nScanned at gate using QR scanner
\nContains: date, dock, AWB, vehicle reg, driver CNIC
\nFormat: Base64-encoded PNG image
\nSingle scan operation
\nSMS (Backup):
\n6-digit numeric code sent via SMS
\nManual entry by gate staff
\nUsed when QR scanner unavailable
\nFormat: \"485729\"
\nAPP_JWT (Mobile App):
\nJWT token from mobile app
\nContains embedded arrival data
\nVerified using ACS public key
\nSupports offline validation
\nValidation Steps:
\nDecode vehicle token to extract embedded data
\nVerify token signature and expiry
\nCheck token not already used (query database)
\nVerify driver CNIC matches token data
\nVerify vehicle registration matches token data
\nVerify gate and dock numbers match assignment
\nCheck arrival time within valid window
\nMark token as USED in database
\nRecord actual arrival time
\nTrigger broadcast notifications (IP #20)
\nError Cases:
\nToken expired (beyond grace period)
\nToken already used (duplicate entry attempt)
\nCNIC mismatch (wrong driver)
\nVehicle registration mismatch (wrong vehicle)
\nGate/dock mismatch (arrived at wrong location)
\nToken invalid or corrupted
\nSubsequent Actions:
\nACS broadcasts arrival info to CB, ACA, CGNR (IP #20)
\nGHA gate staff directs vehicle to assigned dock
\nUnloading can begin after successful validation
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","vehicle-arrivals","validations"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"08dd4358-073a-4f4b-9325-ce8e127e242e","name":"Success - Token Validated","originalRequest":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"aaaef316-3d9f-4596-8126-90bd3090df67"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"9d3bdb4f-0278-4682-bd56-3c3b6f655492"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/vehicle-arrivals/receipts","description":"Requirement Reference: G.E15TRK.12, G.E15CB.13
\nUse Case: Send/Receive Vehicle Arrival
\nDescription: Trucker sends arrival info to GHA and CB receives the notification.
\nProcess Flow: Trucker → ACS → Customs Broker
\nPriority: P1 (Critical Integration)
\nActors: Trucker , ACS, Customs Broker
\nMessage Formats: JSON
\nArrival Methods:
\nQR_CODE_SCAN: Security scans QR code at gate (automated, preferred)
\nSMS_CODE: Security validates 6-digit SMS code manually
\nAPP_BASED: Driver checks in via mobile app with geofencing
\nMANUAL: Security manually enters token number (fallback)
\nBusiness Rules:
\nVehicle token must be valid and not expired
\nDriver CNIC must match TSM request
\nVehicle registration must match TSM request
\nArrival within ±30 minutes of assigned time is considered on-time
\nLate arrivals (>30 min) may require slot reassignment
\nVery early arrivals (>60 min early) may be asked to wait
\nSystem validates token authenticity before accepting arrival
\nGeolocation validates vehicle is actually at GHA facility
\nSecurity Validation:
\nToken authenticity check (signature verification)
\nDriver identity verification (CNIC vs request)
\nVehicle match verification (registration vs request)
\nTime window validation (not expired, not too early)
\nBlacklist check (driver/vehicle not banned)
\nResponse Codes:
\n201 Created: Arrival recorded, proceed to assigned dock
\n400 Bad Request: Invalid token format
\n401 Unauthorized: Token expired or invalid
\n403 Forbidden: Driver/vehicle mismatch with request
\n409 Conflict: Vehicle already checked in
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","vehicle-arrivals","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"e8bbcf32-7dcf-463e-85a9-14df05de82cb","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)","key":"X-Request-ID","value":"9d989557-72c2-4791-abae-9e2d25355dae"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: G.E17GHA.16, G.E17CB.17, G.E17ACA.18, G.E17CGNR.19
\nUse Case: Transmit & Receive Unloading Info
\nProcess Flows:
\nGHA → ACS system → Customs Broker system
\nGHA → ACS system → ACA
\nGHA → ACS system → Consignor system
\nPriority: P1
\nActors: GHA
\nMessage Formats: JSON
\nUnloading Status Values:
\nSTARTED: Unloading started
\nIN_PROGRESS: Unloading in progress
\nCOMPLETED: Unloading completed successfully
\nCOMPLETED_WITH_DISCREPANCY: Completed but with issues (damage, missing pieces)
\nSUSPENDED: Unloading suspended (customs hold, safety issue)
\nBusiness Rules:
\nUnloading start time recorded when first piece removed from truck
\nCompletion time recorded when last piece stored in warehouse
\nDock-out time is when vehicle exits the dock area
\nWarehouse location assigned during unloading for future retrieval
\nAny discrepancies (damage, shortage, excess) must be documented
\nGHA staff member responsible for unloading is recorded
\nUnloading duration tracked for operational efficiency metrics
\nDiscrepancy Types:
\nSHORTAGE: Fewer pieces than declared
\nEXCESS: More pieces than declared
\nDAMAGE: Physical damage to cargo
\nWEIGHT_MISMATCH: Actual weight differs from declared
\nPACKAGING_ISSUE: Improper or damaged packaging
\nAutomatic Notifications:
\nACA: Unloading completion notification
\nConsignor: Cargo received at GHA warehouse
\nCustoms Broker: Cargo ready for customs inspection
\nAirline: Cargo ready for flight preparation
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","vehicle-unloading-records"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"f9cfb54e-d449-4a1d-8ece-426b89639602","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"4ea7a4ec-9e1a-4a59-a1f4-df989a88ade9"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/dangerous-goods-declarations/receipts","description":"Requirement Reference: G.E19CGNR.20
\nUse Case: Send e-DGD
\nProcess Flow: E19CGNR → E19ACA
\nPriority: P1 (Critical Integration)
\nActors: Consignor → ACS → ACA
\nMessage Formats: JSON
\nIATA e-DGD Standards: Based on IATA Dangerous Goods Regulations (DGR)
\nUN Hazard Classes:
\nClass 1: Explosives
\nClass 2: Gases (2.1 Flammable, 2.2 Non-flammable, 2.3 Toxic)
\nClass 3: Flammable liquids
\nClass 4: Flammable solids (4.1, 4.2, 4.3)
\nClass 5: Oxidizing substances (5.1, 5.2)
\nClass 6: Toxic substances (6.1, 6.2)
\nClass 7: Radioactive material
\nClass 8: Corrosive substances
\nClass 9: Miscellaneous dangerous goods
\nPacking Groups:
\nI: High danger
\nII: Medium danger
\nIII: Low danger
\nBusiness Rules:
\nUN number must be valid (4-digit format: UNNNNN)
\nProper shipping name must match UN number
\nClass and packing group mandatory for most DG
\nPacking instruction must be IATA-compliant
\nEmergency contact phone mandatory
\nDigital signature required for declaration authenticity
\nMultiple dangerous goods items can be declared per shipment
\nSome DG require special authorization from CAA
\nValidation Rules:
\nCross-check UN number with shipping name
\nVerify packing group allowed for the class
\nCheck packaging type compatible with DG class
\nValidate quantity limits for air transport
\nEnsure proper labeling and marking requirements met
\nRestricted/Prohibited DG:
\nCertain explosives (Class 1 div 1.4S, 1.5, 1.6)
\nHighly toxic gases (Class 2.3)
\nOrganic peroxides Type A (Class 5.2)
\nSome radioactive materials (Class 7)
\nSystem validates against CAA prohibited list
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","dangerous-goods-declarations","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"3c579cf7-3be0-4b5f-851a-aff8b5e12918","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)","key":"X-Request-ID","value":"dbf00b2e-5b9d-417a-b708-5afedc28810a"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"acb8b750-d06f-48d1-8fc7-471eaeb6cc90"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/dangerous-goods-declarations/xsdg","description":"Requirement Reference: G.E19CGNR.20
\nUse Case: Send e-DGD in IATA E-DGD XML format (XSDG)
\nProcess Flow: E19CGNR → E19ACA → E20AL
\nPriority: P1
\nActors: Consignor → ACS → ACA → Airline
\nMessage Formats: IATA E-DGD XML (XSDG)
\nContent-Type: application/xml
\nIATA Standard: XSDG (XML Shipper's Declaration for Dangerous Goods) based on IATA Cargo-XML standards
\nPurpose: Airlines and some large shippers prefer IATA E-DGD XML format for system-to-system integration and regulatory compliance
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","dangerous-goods-declarations","xsdg"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"c29fcd3b-e639-4d32-8851-a90ec26f3557"},{"name":"Send MAWB/HAWB with DG","id":"d33d8b69-6442-4914-9e3d-c5a5951efa2c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"description":"Unique identifier for the request (UUID format)
\n","key":"X-Request-ID","value":"bb551de4-a307-44ef-a9ba-a33c24cdfc3d"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/mawb-hawb-receipts/xfwb","description":"Requirement Reference: G.E19ACA.21, G.E19GHA.22
\nUse Case: Send e-DGD
\nProcess Flow: E19ACA → E19GHA
\nPriority: P1
\nActors: ACA → ACS → GHA
\nSend e-DGD API:
Transmits the Dangerous Goods Declaration (DGD) electronically, ensuring compliance with safety regulations for dangerous goods.
Send House Air Waybill (HAWB) API:
Handles the House Air Waybill details, including shipper, consignee, flight, weight, and special handling instructions.
Send Master Air Waybill (HAWB) API:
Handles the Master Air Waybill details, including shipper, consignee, flight, weight, and special handling instructions.
Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"4ced6595-b804-4041-a1e0-91f5475ec30a"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/cargo-acceptances","description":"Requirement Reference: G.E21GHA.28, G.E21ACA.29, G.E21CUS.30, G.E21AL.31, G.E21CGNR.32
\nUse Case: Finalize Physical Cargo Acceptance
\nDescription: GHA records actual weight/dimensions, transmit Cargo acceptance information and reports any damage
\nProcess Flows:
\nGHA → ACS System → ACA
\nGHA → ACS System → Customs
\nGHA → ACS System → Airline system
\nGHA → ACS System → Consignor system
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → ACA, Customs, Airline, Consignor (receivers)
\nMessage Formats: JSON (this endpoint), IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nFSU Status: FOH (Freight On Hand)
\nBusiness Context:
Cargo Acceptance is the final physical verification step before cargo is ready for loading. GHA performs:
Physical Verification:
\nCount pieces and verify against AWB
\nWeigh cargo on calibrated scales
\nMeasure dimensions (Length x Width x Height)
\nCalculate dimensional weight (L x W x H / 6000 for air cargo)
\nDetermine chargeable weight (greater of actual or dimensional)
\nInspect for damage or tampering
\nVerify labels and markings
\nWeight Discrepancies:
Common reasons for weight differences:
Additional protective packaging
\nPalletization or unitization
\nMoisture absorption
\nMeasurement errors
\nIncorrect shipper declaration
\nSignificant discrepancies (>5% or >10kg) trigger:
\nRe-weighing with witness
\nInvestigation
\nPotential re-rating of freight charges
\nAmendment of AWB
\nDamage Reporting:
If damage detected:
Photograph damage
\nDocument extent and nature
\nNotify ACA and consignor immediately
\nShipper may withdraw cargo or accept \"as-is\"
\nInsurance claim process initiated
\nFSU FOH (Freight On Hand):
IATA standard status indicating:
Cargo physically received by GHA
\nAll checks completed
\nStored in warehouse
\nReady for buildup and loading
\nCustody transferred from ACA to GHA
\nRequest Body Fields:
\nacceptanceReference: Unique acceptance ID
mawbNumber: Master AWB
hawbNumbers: Array of House AWBs
flightNumber: Booked flight
flightDate: Departure date
acceptanceDateTime: When cargo accepted
actualCargoDetails: Verified measurements
pieces: Actual piece count
weight: Actual gross weight
volume: Actual volume
dimensionalWeight: Calculated from dimensions
chargeableWeight: Greater of actual or dimensional
discrepancies: Differences from AWB
weightDifference: kg difference (positive = heavier)
volumeDifference: Volume difference
reason: Explanation for discrepancy
damageReport: Condition assessment
damageDetected: Boolean
If true: Include photos, description, severity
\nremarks: Condition notes
warehouseAllocation: Storage location
warehouseZone: Physical zone (DG zone for dangerous goods)
storageLocation: Specific bay/row
storageDateTime: When stored
acceptedBy: Personnel details
fsuStatus: IATA status code (FOH)
remarks: Additional notes
Validation Rules:
\nActual weight must be positive
\nChargeable weight must be >= actual weight
\nIf damage detected, photos and description mandatory
\nWarehouse zone must exist in GHA system
\nAcceptance date/time must be after cargo delivery
\nFSU status must be \"FOH\" for this endpoint
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"acc-001\",\n \"acceptanceReference\": \"ACC-GHA-20251128-001\",\n \"mawbNumber\": \"176-12345678\",\n \"actualPieces\": 50,\n \"actualWeight\": 252.3,\n \"chargeableWeight\": 270.0,\n \"damageDetected\": false,\n \"fsuStatus\": \"FOH\",\n \"warehouseLocation\": \"ZONE-DG-A / ROW-12-BAY-5\",\n \"acceptedAt\": \"2025-11-27T14:00:00Z\",\n \"broadcastPending\": true,\n \"broadcastTargets\": [\"ACA\", \"Customs\", \"Airline\", \"Consignor\"],\n \"nextStep\": \"Cargo ready for buildup and loading\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:25:00Z\",\n \"requestId\": \"req-acc-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"INVALID_CHARGEABLE_WEIGHT\",\n \"message\": \"Chargeable weight must be greater than or equal to actual weight\",\n \"details\": [\n {\n \"field\": \"actualCargoDetails.chargeableWeight\",\n \"issue\": \"Chargeable weight (240.0) is less than actual weight (252.3). Chargeable weight must be the greater of actual or dimensional weight.\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:25:00Z\",\n \"requestId\": \"req-acc-001\"\n }\n}\n\nStatus Codes:
\n201: Cargo acceptance finalized successfully
\n400: Invalid data (weight logic error, missing damage details)
\n401: Unauthorized
\n403: Personnel not authorized for cargo acceptance
\n404: AWB not found
\n409: Cargo already accepted
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"0e9c8b5e-120f-47b1-9e98-284ac85d9d15"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/cargo-acceptances/xfsu","description":"Requirement Reference: G.E21GHA.28, G.E21ACA.29, G.E21CUS.30, G.E21AL.31, G.E21CGNR.32
\nUse Case: Finalize Physical Cargo Acceptance
\nDescription: GHA records actual weight/dimensions, transmit Cargo acceptance information and reports any damage
\nProcess Flows:
\nGHA → ACS System → ACA
\nGHA → ACS System → Customs
\nGHA → ACS System → Airline system
\nGHA → ACS System → Consignor system
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-XML (XFSU - Freight Status Update)
\nFSU Status: FOH (Freight On Hand)
\nBusiness Context: XFSU FOH is the IATA Cargo-XML standard for cargo acceptance status. Widely used by airlines and GHA systems for interoperability.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","cargo-acceptances","xfsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"dc37c7e3-fa10-43a5-b342-dcf6f59d487a"},{"name":"Cargo Acceptances (IATA IMP FSU FOH)","id":"6cec6979-8a39-4f39-9bc9-65f30e518812","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"e3422f6d-9f1f-4930-b841-39ebf22ec777"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/cargo-acceptances/fsu","description":"Requirement Reference: G.E21GHA.28, G.E21ACA.29, G.E21CUS.30, G.E21AL.31, G.E21CGNR.32
\nUse Case: Finalize Physical Cargo Acceptance
\nDescription: GHA records actual weight/dimensions, transmit Cargo acceptance information and reports any damage
\nProcess Flows:
\nGHA → ACS System → ACA
\nGHA → ACS System → Customs
\nGHA → ACS System → Airline system
\nGHA → ACS System → Consignor system
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-IMP (FSU - Freight Status Update)
\nFSU Format Structure:
\nFSU\n<AWB>/<Status><Location><Date><Time>/<Pieces><Weight>\n\nExample Breakdown:
\nFSU: Message type
176-12345678: AWB number
FOH: Freight On Hand status
KHI: Location code (Karachi)
27NOV1400: Date and time (27 November, 14:00)
T50: Total 50 pieces
K252.3: Kilograms 252.3
Business Context: FSU FOH is the legacy but widely-used IATA Cargo-IMP format for cargo acceptance status.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","cargo-acceptances","fsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"6cec6979-8a39-4f39-9bc9-65f30e518812"}],"id":"76ea4f5b-58bf-4d5c-ae87-a74e359b2f79","_postman_id":"76ea4f5b-58bf-4d5c-ae87-a74e359b2f79","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Declarations","item":[{"name":"Send Undertaking Declarations","id":"3442752d-e2aa-466c-9ebc-e852474774c1","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"23ee5205-50cf-438e-b0eb-de92f8860d1e"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/undertaking-declarations","description":"Requirement Reference: G.E22CGNR.33
\nUse Case: Update Inspection Status
\nDescription: Consignor sends undertaking declaration
\nProcess Flows: E21GHA → E22CGNR (Consignor submits) → ACS → E22ACA (ACA receives)
\nPriority: P1 (Critical Integration)
\nActors: Consignor (sender) → ACS → ACA (receiver)
\nMessage Formats: JSON
\nBusiness Context:
Undertaking Declaration is a legal document submitted by the Consignor to declare that:
All shipment information is accurate and truthful
\nGoods are properly described, packaged, and labeled
\nNo dangerous goods or prohibited items are included (unless declared)
\nDeclared value is accurate for customs and insurance purposes
\nConsignor accepts liability for any inaccuracies or omissions
\nThis declaration is required AFTER cargo acceptance (E21GHA) and BEFORE security declaration (E22ACA). It serves as:
\nLegal protection for ACA and GHA
\nCompliance with aviation security regulations
\nFoundation for insurance claims
\nCustoms declaration validation
\nRequest Body Fields:
\ndeclarationReference: Unique declaration identifier
mawbNumber: Master Air Waybill number
hawbNumber: House AWB number (if applicable)
consignor: Complete consignor details with tax ID
declarationType: GENERAL_DECLARATION, DANGEROUS_GOODS_DECLARATION, HIGH_VALUE_DECLARATION
declarationText: Full text of the declaration statement
undertakings: Array of specific undertakings
undertakingType: Category of undertaking
ACCURATE_DESCRIPTION: Goods description is accurate
\nPROPER_PACKAGING: Packaging meets standards
\nNO_DANGEROUS_GOODS: No DG unless declared
\nACCURATE_VALUE: Value declaration is correct
\nEXPORT_COMPLIANCE: Complies with export regulations
\nSANCTIONS_COMPLIANCE: No sanctioned parties involved
\ndescription: Detailed undertaking text
inspectionStatus: PENDING, CLEARED, INSPECTION_REQUIRED, REJECTED
inspectionRequired: Boolean flag
signatoryDetails: Digital signature information
cnicNumber: Pakistani National ID (13 digits with hyphens)
signatureDate: Date of signature
signatureTime: Time of signature with timezone
ipAddress: IP address for audit trail
attachments: Supporting documents (company letterhead, authorization letters)
submittedBy: Consignor name
submittedAt: Submission timestamp
Validation Rules:
\nMAWB number must exist in system
\nCNIC number must be valid Pakistani format (5-7-1)
\nSignatory must be authorized representative of consignor
\nAll required undertakings must be present
\nAttachments must not exceed 10MB each
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"utd-001\",\n \"declarationReference\": \"UTD-KEL-20251128-001\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-27T10:05:00Z\",\n \"acaPushPending\": true,\n \"legallyBinding\": true,\n \"nextStep\": \"ACS will push to ACA\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T10:05:00Z\",\n \"requestId\": \"req-utd-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"INVALID_CNIC_FORMAT\",\n \"message\": \"CNIC number format is invalid\",\n \"details\": [\n {\n \"field\": \"signatoryDetails.cnicNumber\",\n \"issue\": \"CNIC must be in format: 5digits-7digits-1digit (e.g., 42101-1234567-1)\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T10:05:00Z\",\n \"requestId\": \"req-utd-001\"\n }\n}\n\nStatus Codes:
\n201: Undertaking declaration received successfully
\n400: Invalid request data (CNIC format, missing undertakings)
\n401: Unauthorized
\n403: Signatory not authorized
\n404: MAWB not found
\n409: Duplicate declaration reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"de8335ea-f738-4233-b8b0-7a0cb52dc5e3"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/security-declarations","description":"Requirement Reference: G.E22ACA.34, G.E22GHA.35
\nUse Case: Submit & Receive Security Declaration
\nDescription: ACA submits security declaration to GHA for regulatory compliance
\nProcess Flow: E22CGNR → E22ACA (ACA submits) → ACS → E22GHA (GHA receives)
\nPriority: P1 (Critical Integration)
\nActors: ACA (sender) → ACS → GHA (receiver)
\nMessage Formats: JSON
\nBusiness Context:
Security Declaration is a mandatory document submitted by the Air Cargo Agent (ACA) to declare that:
Shipment has undergone security screening (X-ray, EDD, or ETD)
\nSecurity controls per ICAO Annex 17 have been applied
\nSecure chain of custody maintained from consignor to GHA
\nACA is certified and compliant with Pakistan NCASP
\nShipment is safe for air transport
\nThis declaration is required AFTER undertaking declaration (E22CGNR) and BEFORE final AWB distribution (E23ACA). It is critical for:
\nAviation security compliance
\nRegulatory audit trail
\nGHA acceptance procedures
\nAirline cargo loading authorization
\nRequest Body Fields:
\nsecurityDeclarationReference: Unique security declaration ID
mawbNumber: Master Air Waybill number
hawbNumbers: Array of House AWB numbers
flightNumber: Booked flight
flightDate: Departure date
aca: Complete ACA details with license number
undertakingDeclarationRef: Reference to consignor's undertaking
shipmentSecurityDetails: Security measures applied
securityControlsApplied: Boolean flag
screeningPerformed: Boolean flag
screeningMethod: X-RAY, EDD (Explosive Detection Dog), ETD (Explosive Trace Detection), PHYSICAL_INSPECTION
screeningDate: Date of screening
screeningLocation: Facility where screening occurred
secureChainOfCustody: Boolean flag
tamperProofPackaging: Boolean flag
accessControlMeasures: Array of security measures at ACA facility
regulatoryCompliance: Compliance certifications
icaoAnnex17Compliance: ICAO Annex 17 (Aviation Security)
ncaspCompliance: National Civil Aviation Security Programme (Pakistan)
iataStandards: IATA cargo security standards
localRegulations: Pakistan CAA regulations
certificateNumbers: Array of certification numbers
dangerousGoods: DG information (if present)
valueDeclaration: High-value cargo information
securityDeclarationText: Full declaration statement
signatoryDetails: ACA security manager signature
certificationNumber: Security certification number
digitalSignature: Encrypted signature
attachments: Security certificates, screening reports
submittedBy: ACA name
submittedAt: Submission timestamp
Validation Rules:
\nACA must have valid security certification
\nScreening must be performed within 24 hours of submission
\nUndertaking declaration must exist and be linked
\nSignatory must be certified security personnel
\nAll required security controls must be confirmed
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"secdec-001\",\n \"securityDeclarationReference\": \"SECDEC-SAC-20251127-001\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-27T11:05:00Z\",\n \"ghaPushPending\": true,\n \"securityCompliance\": \"VERIFIED\",\n \"nextStep\": \"ACS will push to GHA\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T11:05:00Z\",\n \"requestId\": \"req-secdec-001\"\n }\n}\n\nError Response (403 Forbidden):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"INVALID_SECURITY_CERTIFICATION\",\n \"message\": \"ACA security certification is expired or invalid\",\n \"details\": [\n {\n \"field\": \"regulatoryCompliance.certificateNumbers\",\n \"issue\": \"Certificate ICAO-CERT-12345 expired on 2025-11-01\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T11:05:00Z\",\n \"requestId\": \"req-secdec-001\"\n }\n}\n\nStatus Codes:
\n201: Security declaration received successfully
\n400: Invalid request data
\n401: Unauthorized
\n403: Invalid or expired security certification
\n404: Undertaking declaration not found
\n409: Duplicate security declaration
\n500: Internal server error
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","security-declarations"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"2776ffb9-d6b0-4963-9937-2b1399b12b39"},{"name":"e-CSD Submissions (JSON)","id":"cdbdc546-b5e8-4a03-8606-6a6ac8590bb1","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"44a7f57d-3ce4-4936-abfa-f0c56f0adba3"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/e-csd-submissions","description":"Requirement Reference: G.E28GHA.41, G.E28AL.42
\nUse Case: Transmit and Receive e-CSD
\nDescription: GHA issues e-Consignment Security Declaration and distributes to airline and regulators
\nProcess Flow: E27GHA → E28GHA (GHA issues e-CSD) → ACS → Broadcast to E28AL, E28EPO, E29CUS
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Airline, EPO, Customs (receivers)
\nMessage Formats: JSON, IATA e-CSD XML
\nBusiness Context:
e-CSD (Electronic Consignment Security Declaration) is the FINAL security document issued by GHA certifying that:
Cargo has undergone ALL required security screening
\nScreening results are CLEAR (no prohibited items)
\nSecure chain of custody maintained
\nTamper-proof seals applied
\nCargo is SAFE for air transport
\nThe e-CSD is based on:
\nICAO Doc 8973 - Aviation Security Manual (Chapter 13, Appendix 33)
\nIATA e-CSD Standards - Electronic Consignment Security Declaration format
\nPakistan NCASP - National Civil Aviation Security Programme
\ne-CSD is the AUTHORIZATION for:
\nAirline: To load cargo onto aircraft
\nEPO: To accept express shipments for flight
\nCustoms: Final evidence of security compliance
\nWithout e-CSD, cargo CANNOT be loaded.
\nRequest Body Fields:
\necsdReference: Unique e-CSD identifier
mawbNumber: Master Air Waybill number
hawbNumbers: House AWB numbers (if consolidated)
flightNumber: Flight for which cargo is cleared
flightDate: Departure date
departureAirport: Origin airport (IATA code)
destinationAirport: Destination airport (IATA code)
entityResponsible: GHA name (who performed security screening)
entityLicenseNumber: GHA license number
commodityContent: General description of goods
screeningDetails: Summary of all screening performed
Links to primary and secondary screening records
\nFinal screening result must be CLEAR
\nsecurityControls: Security measures applied
sealNumbers: Array of tamper-proof seal numbers
All security controls must be true
\npersonIssuingSecurity: GHA security supervisor
Must have valid PCAA certification
\nDigital signature required
\ndateOfIssuance: Date e-CSD issued
timeOfIssuance: Time e-CSD issued (with timezone)
placeOfIssuance: Location where e-CSD issued
regulatoryReferences: Standards and regulations applied
declarationStatement: Full e-CSD declaration text
distributionList: Stakeholders to receive e-CSD
submittedBy: GHA name
submittedAt: Submission timestamp
Validation Rules:
\nPrimary screening must exist and result must be CLEAR
\nIf secondary screening performed, result must be CLEAR
\nPerson issuing security must have valid certification
\nTamper-proof seals must be applied (seal numbers required)
\nAll security controls must be confirmed
\ne-CSD must be issued within 4 hours of final screening
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"ecsd-001\",\n \"ecsdReference\": \"ECSD-GHA-KHI-20251127-001\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"ISSUED\",\n \"issuedAt\": \"2025-11-27T14:40:00Z\",\n \"distributionPending\": true,\n \"distributionTargets\": [\"AIRLINE\", \"EPO\", \"CUSTOMS\"],\n \"cargoAuthorized\": true,\n \"nextStep\": \"ACS will distribute to stakeholders. Cargo authorized for loading.\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:40:00Z\",\n \"requestId\": \"req-ecsd-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"SCREENING_NOT_CLEAR\",\n \"message\": \"Cannot issue e-CSD when screening result is not CLEAR\",\n \"details\": [\n {\n \"field\": \"screeningDetails.screeningResult\",\n \"issue\": \"Primary screening result: SUSPICIOUS. e-CSD can only be issued when ALL screening results are CLEAR.\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:40:00Z\",\n \"requestId\": \"req-ecsd-001\"\n }\n}\n\nStatus Codes:
\n201: e-CSD issued successfully
\n400: Invalid data (screening not clear, missing seals)
\n401: Unauthorized
\n403: Issuing person not certified
\n404: Screening records not found
\n409: Duplicate e-CSD reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"be8dc9f8-a96c-4bf7-8e9a-10879b7ea82b"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/e-csd-submissions/xml","description":"Requirement Reference: G.E28GHA.41, G.E28AL.42
\nUse Case: Transmit and Receive e-CSD
\nIntegration Point (from Excel IP #58): GHA issues e-Consignment Security Declaration and distributes to airline and regulators
\nMessage Formats: IATA e-CSD XML (per ICAO Doc 8973 standards)
\nContent-Type: application/xml
Business Context: IATA e-CSD XML format is the industry standard for e-Consignment Security Declaration. Used by airlines and GHA systems globally for automated security compliance.
\nXML Schema: IATA e-CSD XML 3.0 (ICAO Doc 8973 compliant)
\nSuccess Response (201 Created): Same structure as JSON endpoint with format indicator
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","e-csd-submissions","xml"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"2ba80108-3ad6-4971-be13-ee67bcea49f7"}],"id":"daa0a420-122f-45ed-a6d3-a2fb94ba89f5","_postman_id":"daa0a420-122f-45ed-a6d3-a2fb94ba89f5","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Scans","item":[{"name":"Security Scans (Primary X-ray)","id":"118a5d1f-947b-4d57-adc9-a79772f36637","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"8c4f3b65-c4c4-40b9-98d4-06d593721859"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/security-scans","description":"Requirement Reference: G.E26GHA.38, G.E26CUS.39
\nUse Case: Submit Cargo for Security Screening
\nDescription: GHA performs X-ray scan and submits results to Customs for risk analysis
\nProcess Flow: E24GHA → E26GHA (GHA performs scan) → ACS → E26CUS (Customs receives)
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Customs/WeBOC (receiver)
\nMessage Formats: JSON
\nBusiness Context:
Primary Security Screening using X-ray is mandatory for ALL export cargo before loading onto aircraft. This screening:
Identifies prohibited items (weapons, explosives, etc.)
\nVerifies cargo contents match declared goods
\nDetects anomalies requiring further inspection
\nComplies with ICAO Annex 17 and Pakistan NCASP
\nProvides evidence for customs risk analysis
\nX-ray scan results are submitted to Customs for review. If suspicious items detected, secondary screening (EDD or ETD) may be required.
\nRequest Body Fields:
\nscanReference: Unique scan identifier
mawbNumber: Master Air Waybill number
hawbNumber: House AWB number (if applicable)
scanType: X-RAY, EDD (Explosive Detection Dog), ETD (Explosive Trace Detection)
scanMethod: PRIMARY_SCREENING, SECONDARY_SCREENING
scanResult: CLEAR, SUSPICIOUS, REQUIRES_SECONDARY_SCREENING, PROHIBITED_ITEM_DETECTED
scanLocation: Physical location of screening
scanFacility: Facility details with PCAA certification
scanEquipment: X-ray machine details
Must be calibrated within last 12 months
\nCertification from Pakistan Civil Aviation Authority (PCAA)
\nscanOperator: Certified X-ray operator
Must have valid PCAA certification
\nTraining on equipment operation
\nscanDetails: Technical scan parameters
scanDuration: Time taken for scan
numberOfPasses: Multiple passes for thorough screening
imageResolution: HIGH, MEDIUM, LOW
penetrationLevel: X-ray penetration (STANDARD, ENHANCED)
findings: Scan results and observations
suspiciousItems: Boolean flag
anomaliesDetected: Boolean flag
description: Detailed findings
secondaryScreeningRequired: Boolean flag
complianceChecks: Regulatory compliance validation
submittedBy: GHA name
submittedAt: Submission timestamp
Validation Rules:
\nScan must be performed within 24 hours of submission
\nEquipment must have valid calibration (within 12 months)
\nOperator must have valid PCAA certification
\nImages must be attached separately (see next endpoint)
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"xray-scan-001\",\n \"scanReference\": \"XRAY-GHA-KHI-20251127-001\",\n \"mawbNumber\": \"176-12345678\",\n \"scanResult\": \"CLEAR\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-27T13:10:00Z\",\n \"customsPushPending\": true,\n \"imageUploadRequired\": true,\n \"nextStep\": \"Upload scan images, then push to Customs\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T13:10:00Z\",\n \"requestId\": \"req-xray-001\"\n }\n}\n\nError Response (403 Forbidden):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"OPERATOR_CERTIFICATION_EXPIRED\",\n \"message\": \"X-ray operator certification has expired\",\n \"details\": [\n {\n \"field\": \"scanOperator.certificationExpiry\",\n \"issue\": \"Certification expired on 2025-11-01. Current date: 2025-11-27\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T13:10:00Z\",\n \"requestId\": \"req-xray-001\"\n }\n}\n\nStatus Codes:
\n201: Security scan received successfully
\n400: Invalid request data
\n401: Unauthorized
\n403: Invalid certification (equipment or operator)
\n404: MAWB not found
\n409: Duplicate scan reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"780ae2ff-46c8-498e-acd6-be274132dab6"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/secondary-screenings","description":"Requirement Reference: G.E27GHA.40
\nUse Case: Secondary scanning, EDD, ETD
\nDescription: GHA to send secondary scan information digitally to ACA, Airline, EPO and customs
\nProcess Flow:
\nGHA → ACS → ACA
\nGHA → ACS → Airline system
\nGHA → ACS → EPO
\nGHA → ACS → Customs
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → ACA, Airline, EPO, Customs (receivers)
\nMessage Formats: JSON
\nBusiness Context:
Secondary Screening is performed when:
Primary X-ray scan detects suspicious items
\nCustoms requests additional verification
\nHigh-risk shipment requiring enhanced security
\nAnomalies detected in primary scan
\nTwo secondary screening methods:
\n1. EDD (Explosive Detection Dog):
\nTrained dog sniffs cargo for explosives
\nDog alerts handler if explosives detected
\nNon-invasive method (no package opening)
\nFast and effective for explosives detection
\nRequires certified dog and handler
\n2. ETD (Explosive Trace Detection):
\nSwab samples collected from cargo surface
\nSwabs analyzed by ETD machine
\nDetects trace amounts of explosives residue
\nMore precise than EDD
\nRequires specialized equipment
\nSecondary screening results distributed to:
\nACA: To inform consignor if issues found
\nAirline: To make loading decision
\nEPO: For express shipments
\nCustoms: For clearance decision
\nRequest Body Fields:
\nscreeningReference: Unique secondary screening ID
primaryScanRef: Link to primary X-ray scan
screeningTrigger: Why secondary screening was performed
X-RAY_SUSPICIOUS: Primary scan showed anomalies
\nCUSTOMS_REQUEST: Customs requested additional screening
\nHIGH_RISK_SHIPMENT: Risk assessment flagged shipment
\nRANDOM_SELECTION: Random security check
\nscreeningType: EDD (Explosive Detection Dog) or ETD (Explosive Trace Detection)
screeningMethod: EXPLOSIVE_DETECTION_DOG, EXPLOSIVE_TRACE_DETECTION, PHYSICAL_INSPECTION
screeningResult: CLEAR, EXPLOSIVES_DETECTED, SUSPICIOUS, REQUIRES_PHYSICAL_INSPECTION
eddDetails: EDD-specific information (if screeningType = EDD)
Dog certification and training details
\nHandler certification
\nDog must have training within last 3 months
\netdDetails: ETD-specific information (if screeningType = ETD)
Equipment details
\nSwab locations
\nAnalysis results
\nscreeningProcess: Process details
numberOfPasses: How many times screening performed
packagesOpened: Boolean flag (if physical inspection done)
findings: Screening results
explosivesDetected: Boolean flag
suspiciousReaction: Boolean flag (for EDD)
description: Detailed findings
furtherActionRequired: Boolean flag
furtherActionType: PHYSICAL_INSPECTION, REJECT_SHIPMENT, ALLOW_WITH_CONDITIONS
complianceChecks: Regulatory compliance
photosAttached: Boolean flag (photos uploaded separately)
videoRecorded: Boolean flag (for EDD sessions)
Validation Rules:
\nPrimary scan must exist and be linked
\nIf EDD: Dog and handler must have valid certifications
\nIf ETD: Equipment must have valid calibration
\nScreening must be performed within 2 hours of primary scan
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"edd-screen-001\",\n \"screeningReference\": \"EDD-GHA-KHI-20251127-002\",\n \"mawbNumber\": \"176-12345678\",\n \"screeningType\": \"EDD\",\n \"screeningResult\": \"CLEAR\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-27T14:15:00Z\",\n \"distributionPending\": true,\n \"distributionTargets\": [\"ACA\", \"AIRLINE\", \"EPO\", \"CUSTOMS\"],\n \"nextStep\": \"ACS will distribute to all stakeholders\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:15:00Z\",\n \"requestId\": \"req-edd-001\"\n }\n}\n\nError Response (403 Forbidden):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"DOG_TRAINING_EXPIRED\",\n \"message\": \"EDD dog training is not current\",\n \"details\": [\n {\n \"field\": \"eddDetails.dogLastTrainingDate\",\n \"issue\": \"Last training was on 2025-08-15. Dogs must be trained within 3 months. Current date: 2025-11-27\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:15:00Z\",\n \"requestId\": \"req-edd-001\"\n }\n}\n\nStatus Codes:
\n201: Secondary screening received successfully
\n400: Invalid request data
\n401: Unauthorized
\n403: Invalid certification (dog, handler, or equipment)
\n404: Primary scan not found
\n409: Duplicate screening reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"01c0702f-06ea-43d8-acc9-048697dd8531"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/allow-loading-authorizations/receipts","description":"Requirement Reference: G.E29CUS.43, G.E29GHA.44
\nUse Case: Final Customs Clearance for Loading
\nDescription: Customs gives final \"Allow Loading\" authorization
\nProcess Flow:
\nCustoms → ACS → GHA
\nCustoms → ACS →Customs Broker
\nCustoms → ACS → Airline system
\nCustoms → ACS → ACA
\nCustoms → ACS → Consignor system
\nPriority: P1 (Critical Integration)
\nActors: Customs/WeBOC (sender) → ACS → GHA, Customs Broker, Airline, ACA, Consignor (receivers)
\nBusiness Context:
\"Allow Loading\" is the final customs authorization after all export checks are complete:
Security screening completed (X-ray, EDD, ETD)
\ne-CSD (Consignment Security Declaration) issued by GHA
\nGoods Declaration (GD) approved
\nRisk assessment cleared
\nPhysical inspection completed (if required)
\nExport duties/taxes paid (if applicable)
\nAll regulatory requirements satisfied
\nWithout this authorization, GHA CANNOT load cargo onto aircraft. This is the final gate before cargo loading.
\nThe authorization is typically issued 2-4 hours before flight departure, giving GHA time to:
\nComplete final cargo preparation
\nBuild ULDs (Unit Load Devices)
\nMove cargo to aircraft parking position
\nCoordinate with airline for loading sequence
\nAuthorization Types:
\nFULL_CLEARANCE: All conditions satisfied, load immediately
CONDITIONAL_CLEARANCE: Load permitted with specific conditions
PARTIAL_CLEARANCE: Only certain shipments/packages cleared
DELAYED_CLEARANCE: Clearance granted but loading delayed
Request Body Fields:
\nauthorizationReference: Unique WeBOC authorization ID
mawbNumber: Master Air Waybill number
hawbNumbers: House AWB numbers (for consolidated shipments)
gdNumber: Goods Declaration number
flightNumber: Target flight for loading
flightDate: Scheduled departure date
authorizationType: Type of clearance granted
clearanceStatus: APPROVED, CONDITIONAL, REJECTED
customsDecision: Final decision code
inspectionRequired: Was physical inspection required?
inspectionCompleted: Is inspection completed?
inspectionResult: CLEAR, SUSPICIOUS, REJECTED
additionalConditions: Array of special conditions (if any)
restrictions: Array of loading restrictions (if any)
authorizedBy: Customs officer details
authorizedAt: Authorization timestamp
validUntil: Authorization expiry (typically flight departure time)
remarks: Additional notes from customs
Validation Rules:
\nGD number must exist and be in APPROVED status
\nAll security checks must be completed
\ne-CSD must be issued
\nFlight must be departing within next 24 hours
\nAuthorization validity must not exceed flight departure time
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"alw-001\",\n \"authorizationReference\": \"WBC-ALW-20251128-001\",\n \"mawbNumber\": \"176-12345678\",\n \"flightNumber\": \"EK-606\",\n \"customsDecision\": \"ALLOW_LOADING\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-27T16:35:00Z\",\n \"validUntil\": \"2025-11-28T14:00:00Z\",\n \"broadcastPending\": true,\n \"broadcastTargets\": [\"GHA\", \"Customs Broker\", \"Airline\", \"ACA\", \"Consignor\"],\n \"nextStep\": \"ACS will broadcast authorization to all stakeholders\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T16:35:00Z\",\n \"requestId\": \"req-alw-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"SECURITY_CHECKS_INCOMPLETE\",\n \"message\": \"Cannot issue Allow Loading authorization - security checks not completed\",\n \"details\": [\n {\n \"field\": \"inspectionCompleted\",\n \"issue\": \"e-CSD not issued by GHA. Security clearance pending.\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T16:35:00Z\",\n \"requestId\": \"req-alw-001\"\n }\n}\n\nStatus Codes:
\n201: Allow Loading authorization received
\n400: Invalid request - checks incomplete
\n401: Unauthorized
\n404: GD or MAWB not found
\n409: Duplicate authorization
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"5694ad1a-b4be-46a4-863a-24a54bf34e69"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/gha-invoices","description":"Requirement Reference: G.E30GHA.45, G.E30ACA.46, G.E30CB.47, G.E30CGNR.48
\nUse Case: Issue & Distribute Ground Handling Invoice
\nDescription: GHA issues invoice for storage/acceptance charges to all liable parties
\nProcess Flow:
\nGHA → ACS → Customs Broker
\nGHA → ACS → ACA
\nGHA → ACS → Consignor system
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Customs Broker, ACA, Consignor (receivers)
\nBusiness Context:
GHA issues an invoice for ground handling services after cargo acceptance and security clearance. Services billed include:
Cargo Acceptance Fee: Receiving, weighing, measuring cargo
\nHandling Fee: Physical handling, ULD building
\nSecurity Screening: X-ray, EDD, ETD scanning
\nStorage Fee: Warehouse storage (if cargo arrived early)
\nDocumentation Fee: Processing shipping documents
\nSpecial Handling Fee: Dangerous goods, valuables, perishables
\nEquipment Usage: ULD rental, pallet usage
\nInvoice Types:
\nCARGO_ACCEPTANCE: Standard cargo acceptance charges
STORAGE: Warehouse storage charges (per day)
HANDLING: Special handling services
SCREENING: Additional security screening
EQUIPMENT: Equipment rental (ULDs, pallets)
DOCUMENTATION: Document processing fees
COMBINED: Multiple charge types in one invoice
Billed Party Types:
\nACA: Air Cargo Agent (most common - pays on behalf of consignor)
CONSIGNOR: Direct shipper payment
CUSTOMS_BROKER: Broker pays for expedited services
AIRLINE: Airline pays (rare - contractual arrangements)
Charge Codes (IATA standard):
\nACC: Cargo Acceptance
HND: Handling
SCN: Security Screening
STG: Storage
DOC: Documentation
DGR: Dangerous Goods Handling
PER: Perishable Handling
VAL: Valuable Cargo Handling
ULD: ULD Usage
Request Body Fields:
\ninvoiceNumber: Unique GHA invoice ID
invoiceType: Type of invoice
mawbNumber: MAWB number
hawbNumbers: HAWB numbers (for consolidated shipments)
flightNumber: Departure flight
flightDate: Scheduled departure
ghaDetails: GHA billing information
billedTo: Customer billing information
chargeBreakdown: Itemized charges
chargeCode: IATA charge code
chargeDescription: Human-readable description
basis: Charging basis (PER_KILOGRAM, PER_PIECE, PER_SHIPMENT, PER_DAY, FLAT_FEE)
quantity: Number of units
unitPrice: Price per unit
amount: Total amount (quantity × unitPrice)
currency: ISO currency code
subtotal: Sum of all charges before tax
taxDetails: Tax breakdown (GST, VAT, etc.)
totalTax: Total tax amount
totalAmount: Grand total (subtotal + totalTax)
currency: Invoice currency
invoiceDate: Invoice issuance date
dueDate: Payment due date
paymentTerms: Payment terms description
paymentMethod: PSW_UPS, BANK_TRANSFER, CASH, CREDIT_CARD
notes: Additional notes
Validation Rules:
\nInvoice number must be unique
\nMAWB must exist in system
\nFlight must be scheduled within next 48 hours
\nDue date must be before or at flight departure time
\nSubtotal must equal sum of all charge amounts
\nTotal amount must equal subtotal + total tax
\nAll amounts must be positive
\nCurrency must be valid ISO code
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"gha-inv-001\",\n \"invoiceNumber\": \"GHA-KHI-INV-20251128-001\",\n \"invoiceType\": \"CARGO_ACCEPTANCE\",\n \"mawbNumber\": \"176-12345678\",\n \"billedTo\": {\n \"partyType\": \"ACA\",\n \"name\": \"Swift Air Cargo\"\n },\n \"totalAmount\": 24599.25,\n \"currency\": \"PKR\",\n \"invoiceDate\": \"2025-11-27T17:00:00Z\",\n \"dueDate\": \"2025-11-28T12:00:00Z\",\n \"status\": \"ISSUED\",\n \"paymentStatus\": \"PENDING\",\n \"broadcastPending\": true,\n \"broadcastTargets\": [\"Customs Broker\", \"ACA\", \"Consignor\"],\n \"psid\": \"UPS-GHA-CARGO-20251128-001\",\n \"paymentLink\": \"https://ups.psw.gov.pk/pay/UPS-GHA-CARGO-20251128-001\",\n \"qrCode\": \"base64-encoded-qr-code\",\n \"nextStep\": \"ACS will broadcast invoice to all liable parties\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T17:05:00Z\",\n \"requestId\": \"req-inv-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"INVOICE_CALCULATION_ERROR\",\n \"message\": \"Invoice total calculation mismatch\",\n \"details\": [\n {\n \"field\": \"totalAmount\",\n \"issue\": \"Total amount (24599.25) does not equal subtotal (21025.00) + tax (3574.25) = 24599.25. Calculation verified. Error in provided totalAmount field.\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T17:05:00Z\",\n \"requestId\": \"req-inv-001\"\n }\n}\n\nStatus Codes:
\n201: Invoice created successfully
\n400: Invalid invoice data
\n401: Unauthorized
\n404: MAWB or flight not found
\n409: Duplicate invoice number
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"bc89b9af-c957-4018-9122-25102c7496f3"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/gha-payments","description":"Requirement Reference: G.E31ACA.49, G.E31CGNR.50, G.E31CB.51, G.E31GHA.52
\nUse Case: Process Ground Handling Payments
\nDescription: ACA, Consignor or CB makes payment for storage/acceptance charges
\nProcess Flow:
\nPriority: P1 (Critical Integration)
\nActors: ACA/Consignor/Customs Broker (payer) → ACS → PSW UPS Gateway → GHA (receiver)
\nBusiness Context:
Payment processing through PSW UPS (Unified Payment System) enables:
Real-time payment confirmation: GHA receives instant notification
\nSecure B2B transactions: Bank-grade security
\nAutomated reconciliation: No manual payment matching
\nDigital receipts: Automatic receipt generation
\nAudit trail: Complete payment history
\nMulti-party support: ACA, Consignor, or Customs Broker can pay
\nPSW UPS Payment Flow:
\nGHA creates invoice with PSID (Payment Service ID)
\nPSID = UPS-GHA-{TYPE}-{DATE}-{ID} format
Payer receives invoice with payment link and QR code
\nPayer initiates payment via PSW UPS portal or API
\nPSW UPS processes payment through banking system
\nACS receives payment confirmation from PSW UPS
\nACS pushes confirmation to GHA
\nGHA updates invoice status to PAID
\nCargo can now be loaded (payment required before loading)
\nPayment Methods:
\nPSW_UPS: PSW Unified Payment System (primary method)
BANK_TRANSFER: Direct bank transfer (requires manual verification)
CREDIT_CARD: Card payment via PSW UPS gateway
MOBILE_WALLET: JazzCash, Easypaisa integration
CASH: Cash payment at GHA counter (rare)
Payer Party Types:
\nACA: Air Cargo Agent (most common - pays on behalf of consignor)
CONSIGNOR: Direct shipper payment
CUSTOMS_BROKER: Broker pays for expedited services
Request Body Fields:
\npaymentReference: Unique payment transaction ID
invoiceId: GHA invoice ID (from invoice creation response)
invoiceNumber: GHA invoice number
psid: Payment Service ID (from invoice)
payerDetails: Payer information
partyType: ACA, CONSIGNOR, CUSTOMS_BROKER
name: Payer organization name
code: Payer code in ACS
accountNumber: PSW UPS account number
contactName: Contact person
phone: Contact phone
email: Contact email
paymentAmount: Amount paid (must match invoice total)
currency: Payment currency
paymentMethod: Payment method used
paymentDetails: PSW UPS transaction details
upsTransactionId: PSW UPS transaction identifier
bankName: Bank used for payment
accountNumber: Bank account number
transactionType: ONLINE_TRANSFER, CARD_PAYMENT, MOBILE_WALLET
authorizationCode: Bank authorization code
paymentDate: Payment timestamp
remarks: Additional payment notes
Validation Rules:
\nInvoice must exist and be in ISSUED or PENDING status
\nPayment amount must exactly match invoice total amount
\nCurrency must match invoice currency
\nPSID must match invoice PSID
\nPSW UPS transaction ID must be valid and unique
\nPayment must be made before invoice due date
\nCannot pay already-paid invoice
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"gha-pay-001\",\n \"paymentReference\": \"PAY-GHA-20251128-001\",\n \"invoiceId\": \"gha-inv-001\",\n \"invoiceNumber\": \"GHA-KHI-INV-20251128-001\",\n \"psid\": \"UPS-GHA-CARGO-20251128-001\",\n \"upsTransactionId\": \"UPS-TXN-20251128-ABC123\",\n \"paymentAmount\": 24599.25,\n \"currency\": \"PKR\",\n \"paymentStatus\": \"COMPLETED\",\n \"paymentDate\": \"2025-11-28T08:00:00Z\",\n \"payerName\": \"Swift Air Cargo\",\n \"payerType\": \"ACA\",\n \"receiptNumber\": \"GHA-RCP-20251128-001\",\n \"receiptUrl\": \"https://api.psw.gov.pk/receipts/GHA-RCP-20251128-001.pdf\",\n \"ghaPushPending\": true,\n \"nextStep\": \"ACS will push payment confirmation to GHA\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T08:05:00Z\",\n \"requestId\": \"req-pay-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"PAYMENT_AMOUNT_MISMATCH\",\n \"message\": \"Payment amount does not match invoice total\",\n \"details\": [\n {\n \"field\": \"paymentAmount\",\n \"issue\": \"Payment amount (24500.00) does not match invoice total (24599.25). Difference: 99.25 PKR\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T08:05:00Z\",\n \"requestId\": \"req-pay-001\"\n }\n}\n\nError Response (409 Conflict):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"INVOICE_ALREADY_PAID\",\n \"message\": \"Invoice has already been paid\",\n \"details\": [\n {\n \"field\": \"invoiceId\",\n \"issue\": \"Invoice gha-inv-001 status is PAID. Payment ID: gha-pay-001. Cannot accept duplicate payment.\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T08:05:00Z\",\n \"requestId\": \"req-pay-001\"\n }\n}\n\nStatus Codes:
\n201: Payment processed successfully
\n400: Invalid payment data (amount mismatch, currency mismatch)
\n401: Unauthorized
\n404: Invoice not found
\n409: Invoice already paid or payment conflict
\n502: PSW UPS gateway unavailable
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"94cbfd1a-e659-4c40-a069-60c47e92e1d3"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/digital-pouches","description":"Requirement Reference: G.E32GHA.53, G.E33AL.54
\nUse Case: Create and Receive Digital Pouch
\nDescription: GHA compiles and shares the Digital Pouch (all export docs)
\nProcess Flows: E31GHA → E32GHA (GHA creates pouch) → Add documents → Finalize → E32GHA → E33AL (Share with airline)
\nPriority: P1 (Critical Integration)
\nActors: GHA (creator) → Airline (receiver)
\nBusiness Context:
Digital Pouch is the electronic replacement for the physical document pouch traditionally carried with cargo. It contains all export documents required by:
Airline: For cargo manifest and flight documentation
\nDestination Airport: For cargo handling and customs clearance
\nDestination Customs: For import clearance
\nTraditional Process (Paper-based):
\nGHA prints all documents
\nPlaces in physical pouch (sealed envelope)
\nAttaches pouch to ULD or gives to flight crew
\nPouch travels with cargo
\nDestination GHA opens pouch and distributes documents
\nDigital Process (Electronic):
\nGHA creates digital pouch in ACS (status: DRAFT)
\nAdds electronic documents (PDFs, scans)
\nFinalizes pouch (locked from edits)
\nShares with airline via ACS
\nAirline downloads documents
\nACS pushes to destination systems automatically
\nDigital Pouch State Machine:
\nDRAFT: GHA creating pouch, can add/remove documents
FINALIZED: Locked from edits, ready to share
SHARED: Shared with airline, airline can download
ACKNOWLEDGED: Airline confirmed receipt
DELIVERED: Pushed to destination systems
Required Documents:
\nMAWB (Master Air Waybill) - Mandatory
\nHAWB (House Air Waybill) - Mandatory for consolidations
\nGD (Goods Declaration) - Mandatory for customs
\nCommercial Invoice - Mandatory
\nPacking List - Mandatory
\nCertificate of Origin - If required by destination country
\nPhytosanitary Certificate - For agricultural products
\nNOC (No Objection Certificate) - For restricted goods
\ne-CSD (Consignment Security Declaration) - Mandatory
\nDangerous Goods Declaration - If DG cargo
\nGHA Invoice & Payment Receipt - Financial documents
\nBusiness Rules:
\nCannot add documents after finalization
\nCannot finalize empty pouch (must have at least MAWB)
\nCannot share un-finalized pouch
\nMAWB is mandatory, HAWB mandatory for consolidations
\nGD number must match customs clearance
\nAll document files must be PDF format (max 10MB each)
\nMaximum 50 documents per pouch
\nCannot delete finalized pouch
\nCan only share with airline operating the flight
\nRequest Body Fields:
\npouchReference: Unique digital pouch identifier
flightNumber: Target flight
flightDate: Scheduled departure
origin: Departure airport (IATA code)
destination: Arrival airport (IATA code)
airline: Airline name
airlineCode: IATA airline code
mawbNumbers: Array of MAWB numbers in this pouch
ghaDetails: GHA creating the pouch
createdBy: GHA employee details
createdAt: Creation timestamp
Validation Rules:
\nPouch reference must be unique
\nFlight must exist and be scheduled within next 24 hours
\nMAWB numbers must exist in system
\nAll MAWBs must be for the same flight
\nOrigin must match flight origin
\nAirline code must match flight airline
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"dpo-001\",\n \"pouchReference\": \"DPO-KHI-EK606-20251128-001\",\n \"flightNumber\": \"EK-606\",\n \"flightDate\": \"2025-11-28\",\n \"status\": \"DRAFT\",\n \"documentCount\": 0,\n \"mawbCount\": 2,\n \"createdAt\": \"2025-11-28T09:00:00Z\",\n \"nextStep\": \"Add documents to pouch\",\n \"canEdit\": true,\n \"canFinalize\": false,\n \"canShare\": false\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T09:05:00Z\",\n \"requestId\": \"req-dpo-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"MAWB_FLIGHT_MISMATCH\",\n \"message\": \"MAWB numbers are not all for the same flight\",\n \"details\": [\n {\n \"field\": \"mawbNumbers\",\n \"issue\": \"MAWB 176-12345679 is booked on flight PK-307, not EK-606\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T09:05:00Z\",\n \"requestId\": \"req-dpo-001\"\n }\n}\n\nStatus Codes:
\n201: Digital pouch created
\n400: Invalid pouch data
\n401: Unauthorized
\n404: Flight or MAWB not found
\n409: Duplicate pouch reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"10101c3c-8c60-453a-b9da-b19c0c159c7e"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/digital-pouches/:id/documents","description":"Requirement Reference: G.E32GHA.53, G.E33AL.54
\nUse Case: Create and Receive Digital Pouch
\nDescription: GHA compiles and shares the Digital Pouch (all export docs)
\nProcess Flow: E32GHA (GHA adds documents to DRAFT pouch)
\nPriority: P1 (Critical Integration)
\nActors: GHA (adds documents)
\nBusiness Context: GHA adds export documents one by one to the digital pouch. Documents can only be added when pouch is in DRAFT status.
\nDocument Types:
\nMAWB: Master Air Waybill (mandatory)
HAWB: House Air Waybill (mandatory for consolidations)
GD: Goods Declaration (mandatory)
COMMERCIAL_INVOICE: Commercial invoice (mandatory)
PACKING_LIST: Packing list (mandatory)
CERTIFICATE_OF_ORIGIN: Certificate of origin
PHYTOSANITARY_CERT: Phytosanitary certificate
NOC: No Objection Certificate
E_CSD: Electronic Consignment Security Declaration (mandatory)
DANGEROUS_GOODS_DECL: Dangerous goods declaration
GHA_INVOICE: GHA invoice
PAYMENT_RECEIPT: Payment receipt
OTHER: Other supporting documents
URL Parameters:
\n:id: Digital pouch IDRequest Body Fields:
\ndocumentType: Type of document (from list above)
documentNumber: Document reference number
documentTitle: Display title
documentFile: Base64-encoded PDF file content
fileSize: File size in bytes (max 10MB = 10485760 bytes)
fileType: Must be application/pdf
issuer: Organization that issued the document
issueDate: Document issue date
isMandatory: Is this a mandatory document?
remarks: Additional notes
Validation Rules:
\nPouch must be in DRAFT status
\nFile must be PDF format
\nFile size must not exceed 10MB
\nDocument type must be valid
\nCannot add more than 50 documents per pouch
\nCannot add duplicate document types (except HAWB, NOC, OTHER)
\nBase64 content must be valid
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"dpo-doc-001\",\n \"pouchId\": \"dpo-001\",\n \"documentType\": \"MAWB\",\n \"documentNumber\": \"176-12345678\",\n \"documentTitle\": \"Master Air Waybill - 176-12345678\",\n \"fileSize\": 2048576,\n \"addedAt\": \"2025-11-28T09:15:00Z\",\n \"downloadUrl\": \"https://api.psw.gov.pk/documents/dpo-doc-001.pdf\",\n \"pouchStatus\": \"DRAFT\",\n \"totalDocuments\": 1\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T09:15:00Z\",\n \"requestId\": \"req-add-doc-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"POUCH_NOT_EDITABLE\",\n \"message\": \"Cannot add documents to finalized pouch\",\n \"details\": [\n {\n \"field\": \"pouchId\",\n \"issue\": \"Pouch dpo-001 is in FINALIZED status. Documents can only be added to DRAFT pouches.\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T09:15:00Z\",\n \"requestId\": \"req-add-doc-001\"\n }\n}\n\nStatus Codes:
\n201: Document added successfully
\n400: Invalid document or pouch not editable
\n404: Pouch not found
\n413: File size exceeds limit
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"2a437715-2abb-4da6-b316-1c59115eff6e"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/rcs-status-updates","description":"Requirement Reference: G.E34GHA.55, G.E34AL.56, G.E34ACA.57, G.E34CGNR.58
\nUse Case: Transmit/Receive RCS Status
\nDescription: GHA transmits Ready for Carriage status to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Airline system
\nGHA → ACS → ACA
\nGHA → ACS → Consignor system
\nGHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Airline, ACA, Consignor, EPO (receivers)
\nMessage Formats: JSON (this endpoint), IATA Cargo-XML (XFSU RCS), IATA Cargo-IMP (FSU RCS)
\nBusiness Context:
RCS (Ready for Carriage) is an IATA Freight Status Update indicating that:
Cargo has been fully accepted by GHA
\nAll documentation is complete and verified
\nCargo has passed all security screenings
\nCustoms has given \"Allow Loading\" clearance
\nCargo is physically ready to be loaded onto aircraft
\nULD build-up is completed (if applicable)
\nCargo is positioned in warehouse ready-for-loading area
\nRCS is transmitted after:
\nCargo acceptance completed (weight/dimensions verified)
\nSecurity screening passed (X-ray, EDD, ETD)
\nDangerous goods check completed
\nCustoms clearance received
\nDigital pouch finalized
\nULD build-up completed
\nCargo moved to loading area
\nStakeholders use RCS to:
\nAirline: Confirm cargo ready for loading, plan aircraft loading sequence
\nACA: Track shipment progress, inform consignor
\nConsignor: Confirm cargo on track for scheduled flight
\nEPO: Track express shipment status
\nIATA FSU Status Codes:
\nRCS = Ready for Carriage
\nPRE = Prepared for Loading (next status after RCS)
\nDEP = Departed (final export status)
\nRequest Body Fields:
\nstatusReference: Unique RCS status message identifier
statusCode: Always \"RCS\" for this endpoint
mawbNumber: Master Air Waybill number
hawbNumbers: House AWB numbers (for consolidations)
flightNumber: Booked flight
flightDate: Scheduled departure date
origin: IATA airport code (departure)
destination: IATA airport code (arrival)
pieces: Number of cargo pieces
weight: Total weight
volume: Total volume
ulds: Array of Unit Load Devices
uldType: IATA ULD type code (AKE, AKN, PMC, etc.)
uldNumber: ULD serial number
contentsWeight: Weight of cargo in ULD
position: Planned position on aircraft (LOWER_DECK_FWD, LOWER_DECK_AFT, MAIN_DECK, BULK)
statusDateTime: When cargo became ready for carriage (ISO 8601)
location: IATA airport code where status occurred
remarks: Additional notes
reportedBy: GHA personnel who confirmed RCS status
submittedAt: Timestamp when submitted to ACS
Validation Rules:
\nStatus must be submitted before flight departure
\nMAWB number must exist in system
\nFlight booking must exist
\nULD types must be valid IATA codes
\nWeight and pieces must match cargo acceptance data
\nAllow Loading clearance must be received from Customs
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"rcs-001\",\n \"statusReference\": \"RCS-GHA-KHI-20251128-001\",\n \"statusCode\": \"RCS\",\n \"mawbNumber\": \"176-12345678\",\n \"flightNumber\": \"EK-606\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T12:06:00Z\",\n \"broadcastPending\": true,\n \"broadcastTargets\": [\"Airline\", \"ACA\", \"Consignor\", \"EPO\"],\n \"nextStep\": \"ACS will broadcast to all stakeholders\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T12:06:00Z\",\n \"requestId\": \"req-rcs-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"ALLOW_LOADING_NOT_RECEIVED\",\n \"message\": \"Cannot submit RCS status - Allow Loading clearance not received from Customs\",\n \"details\": [\n {\n \"field\": \"mawbNumber\",\n \"issue\": \"MAWB 176-12345678 does not have Customs clearance. Status: PENDING\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T12:06:00Z\",\n \"requestId\": \"req-rcs-001\"\n }\n}\n\nStatus Codes:
\n201: RCS status received successfully
\n400: Invalid request data or business rule violation
\n401: Unauthorized
\n404: MAWB or flight booking not found
\n409: Duplicate status reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"90199489-626a-48e0-a51e-7d1a4289021a"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/rcs-status-updates/xfsu","description":"Requirement Reference: G.E34GHA.55, G.E34AL.56, G.E34ACA.57, G.E34CGNR.58
\nUse Case: Transmit/Receive RCS Status
\nDescription: GHA transmits Ready for Carriage status to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Airline system
\nGHA → ACS → ACA
\nGHA → ACS → Consignor system
\nGHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-XML (XFSU)
\nContent-Type: application/xml
Business Context:
XFSU (Freight Status Update) in IATA Cargo-XML format is the standard for status notifications. The RCS status code indicates Ready for Carriage.
XML Schema: IATA Cargo-XML 3.00 XFSU message with StatusCode=RCS
\nKey XML Elements:
\nMasterAirWaybillID: MAWB number
StatusCode: RCS (Ready for Carriage)
StatusDate: Date in YYYY-MM-DD format
StatusTime: Time in HH:MM format (24-hour)
StatusLocation: IATA airport code where status occurred
FlightIdentification: Flight details
PieceQuantity: Number of pieces
Weight/WeightUnit: Cargo weight (KGM = kilograms)
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"rcs-xfsu-001\",\n \"format\": \"IATA_CARGO_XML\",\n \"messageType\": \"XFSU\",\n \"statusCode\": \"RCS\",\n \"mawbNumber\": \"176-12345678\",\n \"flightNumber\": \"EK-606\",\n \"status\": \"RECEIVED\",\n \"parsedSuccessfully\": true,\n \"receivedAt\": \"2025-11-28T12:10:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T12:10:00Z\",\n \"requestId\": \"req-rcs-xfsu-001\"\n }\n}\n\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","rcs-status-updates","xfsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"84fb94e8-4b97-44ad-924a-917eab23a443"},{"name":"RCS Status Updates (IATA IMP FSU)","id":"588ed2eb-0e04-4940-affd-d4aed9cbebfb","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"13c8efc2-a5bf-4731-81a8-24e1c4efa244"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/rcs-status-updates/fsu","description":"Requirement Reference: G.E34GHA.55, G.E34AL.56, G.E34ACA.57, G.E34CGNR.58
\nUse Case: Transmit/Receive RCS Status
\nDescription: GHA transmits Ready for Carriage status to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Airline system
\nGHA → ACS → ACA
\nGHA → ACS → Consignor system
\nGHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-IMP (FSU)
\nContent-Type: text/plain
Business Context:
FSU (Freight Status Update) in IATA Cargo-IMP format is the legacy format for status notifications. The RCS status code indicates Ready for Carriage.
FSU Format Structure:
\nFSU\n<AWB>/<StatusCode>/<DateTime>/<Location>\n<Flight>/<Date>.<Origin><Destination>/<Details>\n\nExample Breakdown:
\nFSU: Message type identifier
176-12345678: MAWB number
RCS: Status code (Ready for Carriage)
28NOV1200: Date and time (28 November at 12:00)
KHI: Location where status occurred
EK606/28NOV.KHIDXB: Flight details
T10K250.5: Total 10 pieces, 250.5 kilograms
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"rcs-fsu-001\",\n \"format\": \"IATA_CARGO_IMP\",\n \"messageType\": \"FSU\",\n \"statusCode\": \"RCS\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"RECEIVED\",\n \"parsedSuccessfully\": true,\n \"receivedAt\": \"2025-11-28T12:15:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T12:15:00Z\",\n \"requestId\": \"req-rcs-fsu-001\"\n }\n}\n\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","rcs-status-updates","fsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"588ed2eb-0e04-4940-affd-d4aed9cbebfb"}],"id":"0a8b2078-a971-49b7-914e-a5e564d9dcda","_postman_id":"0a8b2078-a971-49b7-914e-a5e564d9dcda","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"PRE","item":[{"name":"PRE Status Updates (JSON)","id":"77b619dc-b61f-4db2-8899-e7b23f9976d8","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"96be1caa-ad51-4540-bb7a-0ff0a61b74be"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/pre-status-updates","description":"Requirement Reference: G.E35GHA.59, G.E35AL.60, G.E35ACA.61, G.E35CGNR.62
\nUse Case: Transmit/Receive PRE Status
\nDescription: GHA transmits Prepared for Loading status to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Airline system
\nGHA → ACS → ACA
\nGHA → ACS → Consignor system
\nGHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Airline, ACA, Consignor, EPO (receivers)
\nMessage Formats: JSON (this endpoint), IATA Cargo-XML (XFSU PRE), IATA Cargo-IMP (FSU PRE)
\nBusiness Context:
PRE (Prepared for Loading) is an IATA Freight Status Update indicating that:
Cargo has been moved from warehouse to aircraft side
\nULDs are positioned at aircraft parking bay
\nCargo is physically prepared and ready to be loaded onto aircraft
\nLoading sequence has been determined
\nGround equipment is in place for loading
\nAircraft is at gate and ready to receive cargo
\nPRE is transmitted after:
\nRCS status confirmed (cargo ready for carriage)
\nAircraft arrived at gate
\nCargo/ULDs transported from warehouse to aircraft
\nLoading equipment positioned (cargo loader, belt loader)
\nLoading supervisor on-site
\nLoad plan finalized
\nPRE typically occurs 1-2 hours before scheduled departure time.
\nStakeholders use PRE to:
\nAirline: Confirm cargo at aircraft, monitor loading progress
\nACA: Track shipment milestone, provide real-time updates to consignor
\nConsignor: Confirm cargo boarding in progress
\nEPO: Track express shipment loading
\nIATA FSU Status Codes Sequence:
\nRequest Body Fields:
\nstatusReference: Unique PRE status message identifier
statusCode: Always \"PRE\" for this endpoint
mawbNumber: Master Air Waybill number
hawbNumbers: House AWB numbers (for consolidations)
flightNumber: Flight being loaded
flightDate: Departure date
origin: IATA airport code
destination: IATA airport code
pieces: Number of cargo pieces
weight: Total weight
volume: Total volume
ulds: Array of Unit Load Devices
uldType: IATA ULD type code
uldNumber: ULD serial number
contentsWeight: Weight of cargo in ULD
position: Position on aircraft
loadingSequence: Order in which ULD will be loaded (1, 2, 3...)
statusDateTime: When cargo prepared for loading (ISO 8601)
location: IATA airport code
aircraftRegistration: Aircraft tail number
parkingBay: Gate/bay number where aircraft is parked
remarks: Additional notes
reportedBy: GHA loading supervisor
submittedAt: Submission timestamp
Validation Rules:
\nPRE must be submitted after RCS
\nStatus must be submitted before flight departure
\nAircraft registration must match flight booking
\nLoading sequence must be sequential (1, 2, 3...)
\nULD positions must match load plan
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"pre-001\",\n \"statusReference\": \"PRE-GHA-KHI-20251128-001\",\n \"statusCode\": \"PRE\",\n \"mawbNumber\": \"176-12345678\",\n \"flightNumber\": \"EK-606\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T13:06:00Z\",\n \"broadcastPending\": true,\n \"broadcastTargets\": [\"Airline\", \"ACA\", \"Consignor\", \"EPO\"],\n \"nextStep\": \"ACS will broadcast to all stakeholders\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T13:06:00Z\",\n \"requestId\": \"req-pre-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"RCS_NOT_SUBMITTED\",\n \"message\": \"Cannot submit PRE status - RCS status not yet submitted\",\n \"details\": [\n {\n \"field\": \"statusCode\",\n \"issue\": \"PRE status requires prior RCS status. Last status: FOH (Freight on Hand)\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T13:06:00Z\",\n \"requestId\": \"req-pre-001\"\n }\n}\n\nStatus Codes:
\n201: PRE status received successfully
\n400: Invalid request data or business rule violation
\n401: Unauthorized
\n404: MAWB or flight booking not found
\n409: Duplicate status reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"bb581cc6-10c5-4b93-bfad-438a8001a23b"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/pre-status-updates/xfsu","description":"Requirement Reference: G.E35GHA.59, G.E35AL.60, G.E35ACA.61, G.E35CGNR.62
\nUse Case: Transmit/Receive PRE Status
\nDescription: GHA transmits Prepared for Loading status to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Airline system
\nGHA → ACS → ACA
\nGHA → ACS → Consignor system
\nGHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-XML (XFSU)
\nContent-Type: application/xml
XML Schema: IATA Cargo-XML 3.00 XFSU message with StatusCode=PRE
\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","pre-status-updates","xfsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"915de4c6-ea75-4146-a4ad-58ebb50ba896"},{"name":"PRE Status Updates (IATA IMP FSU)","id":"018a076a-8549-4cf8-9d34-efcaeff4a227","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"eddeb8d9-573c-4941-86b9-13634f2df984"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/pre-status-updates/fsu","description":"Requirement Reference: G.E35GHA.59, G.E35AL.60, G.E35ACA.61, G.E35CGNR.62
\nUse Case: Transmit/Receive PRE Status
\nDescription: GHA transmits Prepared for Loading status to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Airline system
\nGHA → ACS → ACA
\nGHA → ACS → Consignor system
\nGHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-IMP (FSU)
\nContent-Type: text/plain
FSU Format: Standard IATA Cargo-IMP with StatusCode=PRE
\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","pre-status-updates","fsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"018a076a-8549-4cf8-9d34-efcaeff4a227"}],"id":"0e16ec83-73d2-48e6-89d6-e1abfc4fc0b0","_postman_id":"0e16ec83-73d2-48e6-89d6-e1abfc4fc0b0","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Flight manifest","item":[{"name":"Flight Manifests (JSON)","id":"e10db6df-504d-40d7-89ab-0bf5ee954b7c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"ecee2cdd-5309-4c19-b869-e851df747ff7"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/flight-manifests","description":"Requirement Reference: G.E36GHA.63, G.E36CUS.64, G.E36AL.65, G.E36ANF.66, G.E36PAA.67
\nUse Case: Transmit/Receive Flight Manifest
\nDescription: GHA transmits the Flight Manifest to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Customs
\nGHA → ACS → Airline system
\nGHA → ACS → ANF
\nGHA → ACS → Pakistan Airport Authority
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Customs, Airline, ANF, PAA (receivers)
\nMessage Formats: JSON (this endpoint), IATA Cargo-XML (XFFM), IATA Cargo-IMP (FFM)
\nBusiness Context:
FFM (Flight Manifest) is a complete list of all cargo shipments loaded on a specific flight. The manifest is created after:
All cargo loaded onto aircraft
\nFinal piece count and weight confirmed
\nULD loading positions confirmed
\nLoad plan finalized
\nAircraft closed and ready for departure
\nThe FFM is transmitted to multiple stakeholders for different purposes:
\nFor Customs (WeBOC):
\nVerify all shipments have proper export clearance
\nCross-check against Goods Declarations (GDs)
\nIdentify any discrepancies
\nComplete export manifest reconciliation (MR) process
\nClose customs records for export shipments
\nFor Airline:
\nConfirm cargo loaded matches booking
\nVerify weight and balance calculations
\nUpdate flight operations system
\nProvide to destination station for arrival planning
\nFor ANF (Anti-Narcotics Force):
\nMonitor high-risk shipments
\nTrack special cargo flagged for inspection
\nCross-reference against watchlist
\nFor PAA (Pakistan Airport Authority):
\nCollect flight statistics
\nMonitor cargo throughput
\nAirport capacity planning
\nPerformance metrics
\nFFM is typically transmitted 30-60 minutes before scheduled departure, after all cargo loading is complete.
\nRequest Body Fields:
\nmanifestReference: Unique FFM identifier
manifestType: Always \"FFM\" for export flight manifest
flightNumber: IATA flight number
flightDate: Departure date
origin: IATA airport code (departure)
destination: IATA airport code (arrival)
aircraftType: IATA aircraft type code
aircraftRegistration: Aircraft tail number
scheduledDepartureTime: Original scheduled departure
estimatedDepartureTime: Current estimated departure (may differ due to delays)
shipments: Array of all cargo on flight
mawbNumber: Master Air Waybill
hawbNumbers: House AWBs (for consolidations)
shipper: Shipper name
consignee: Consignee name
pieces: Number of pieces
weight: Total weight
volume: Total volume
commodityDescription: Cargo description
specialHandlingCodes: IATA SHC codes
originAirport: May differ from flight origin (for transfer cargo)
destinationAirport: May differ from flight destination (for transfer cargo)
ulds: ULDs containing this shipment
totalShipments: Count of unique MAWBs
totalPieces: Sum of all pieces
totalWeight: Sum of all weights
totalVolume: Sum of all volumes
totalULDs: Count of ULDs on flight
preparedBy: GHA manifest clerk
preparedAt: Manifest creation timestamp
Validation Rules:
\nManifest must be submitted before departure
\nAll MAWBs must have RCS or PRE status
\nAll shipments must have customs clearance
\nTotal weight must not exceed aircraft capacity
\nULD positions must match load plan
\nNo duplicate MAWB numbers
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"ffm-001\",\n \"manifestReference\": \"FFM-GHA-KHI-EK606-20251128\",\n \"flightNumber\": \"EK-606\",\n \"flightDate\": \"2025-11-28\",\n \"totalShipments\": 1,\n \"totalPieces\": 10,\n \"totalWeight\": 250.5,\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T13:35:00Z\",\n \"broadcastPending\": true,\n \"broadcastTargets\": [\"Customs\", \"Airline\", \"ANF\", \"PAA\"],\n \"nextStep\": \"ACS will broadcast to all stakeholders\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T13:35:00Z\",\n \"requestId\": \"req-ffm-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"CUSTOMS_CLEARANCE_MISSING\",\n \"message\": \"Cannot submit FFM - some shipments do not have customs clearance\",\n \"details\": [\n {\n \"field\": \"shipments[0].mawbNumber\",\n \"issue\": \"MAWB 176-12345678 does not have Allow Loading clearance\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T13:35:00Z\",\n \"requestId\": \"req-ffm-001\"\n }\n}\n\nStatus Codes:
\n201: FFM received successfully
\n400: Invalid data or business rule violation
\n401: Unauthorized
\n404: Flight booking not found
\n409: Duplicate manifest reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"068fcbc5-2987-46e9-9113-433c4af6cc80"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/flight-manifests/xffm","description":"Requirement Reference: G.E36GHA.63, G.E36CUS.64, G.E36AL.65, G.E36ANF.66, G.E36PAA.67
\nUse Case: Transmit/Receive Flight Manifest
\nDescription: GHA transmits the Flight Manifest to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Customs
\nGHA → ACS → Airline system
\nGHA → ACS → ANF
\nGHA → ACS → Pakistan Airport Authority
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-XML (XFFM)
\nContent-Type: application/xml
XML Schema: IATA Cargo-XML 3.00 XFFM message
\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","flight-manifests","xffm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"f498a010-80e3-4a99-a69a-df713ba01027"},{"name":"Flight Manifests (IATA IMP FFM)","id":"1ae52d73-4cde-45b3-b055-f79c4461960a","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"225c4433-0808-4877-a3e8-6eb0d82e6d81"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/flight-manifests/ffm","description":"Requirement Reference: G.E36GHA.63, G.E36CUS.64, G.E36AL.65, G.E36ANF.66, G.E36PAA.67
\nUse Case: Transmit/Receive Flight Manifest
\nDescription: GHA transmits the Flight Manifest to all relevant stakeholders
\nProcess Flow:
\nGHA → ACS → Customs
\nGHA → ACS → Airline system
\nGHA → ACS → ANF
\nGHA → ACS → Pakistan Airport Authority
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-IMP (FFM)
\nContent-Type: text/plain
FFM Format: Standard IATA Cargo-IMP
\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","flight-manifests","ffm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"1ae52d73-4cde-45b3-b055-f79c4461960a"}],"id":"d67d5a9d-83a9-4018-a591-56879abffaf5","_postman_id":"d67d5a9d-83a9-4018-a591-56879abffaf5","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Departure","item":[{"name":"Departure Status Updates (JSON)","id":"42638e45-cc65-48fe-a1c4-3137b243836e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"b9bd4bbb-de28-434b-844c-d8093379068d"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/departure-status-updates","description":"Requirement Reference: G.E37GHA.68, G.E37AL.69, G.E37CUS.70, G.E37PAA.71, G.E37P.72, G.E37ACA.73, G.E37CGNR.74
\nUse Case: Transmit/Receive Departure Status
\nDescription: GHA transmits Departure status to all stakeholders
\nProcess Flow:
\nE36GHA → ACS → Airline system
\nE36GHA → ACS → Customs
\nE36GHA → ACS → Pakistan Airport Authority
\nE36GHA → ACS → P
\nE36GHA → ACS → ACA
\nE36GHA → ACS → Consignor system
\nE36GHA → ACS → Customs Broker
\nE36GHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Airline, Customs, PAA, Pakistan Post, ACA, Consignor, Customs Broker, EPO (receivers)
\nMessage Formats: JSON (this endpoint), IATA Cargo-XML (XFSU DEP), IATA Cargo-IMP (FSU DEP)
\nBusiness Context:
DEP (Departed) is the final IATA Freight Status Update for export cargo, indicating that:
Aircraft has physically departed with cargo on board
\nCargo is en route to destination
\nExport process is complete at origin station
\nNo further changes possible at origin
\nDEP is transmitted immediately after:
\nAircraft pushback from gate
\nWheels off ground (actual takeoff time)
\nFlight confirmed departed by airport operations
\nDEP status is critical for:
\nFor Customs/WeBOC:
\nCLOSES the export Manifest Reconciliation (MR) process
\nConfirms cargo physically left Pakistan
\nCompletes export customs clearance cycle
\nUpdates export statistics
\nNo further amendments allowed after DEP
\nFor Airline:
\nUpdates flight status system
\nNotifies destination station of en route cargo
\nTriggers arrival preparation at destination
\nFor ACA:
\nConfirms shipment departed
\nProvides real-time tracking to consignor
\nUpdates shipment status to \"In Transit\"
\nFor Consignor:
\nConfirms cargo successfully shipped
\nProvides actual departure time
\nEnables tracking to destination
\nFor Customs Broker:
\nCompletes export documentation
\nCloses GD (Goods Declaration) record
\nFor EPO:
\nTracks express shipment progress
\nCalculates estimated arrival time
\nFor Pakistan Post:
\nTracks postal items
\nUpdates mail tracking system
\nFor PAA (Airport Authority):
\nUpdates airport statistics
\nFlight departure confirmation
\nCargo throughput metrics
\nIATA FSU Status Codes Sequence (Complete Export Flow):
\nRequest Body Fields:
\nstatusReference: Unique DEP status message identifier
statusCode: Always \"DEP\" for this endpoint
mawbNumber: Master Air Waybill number
hawbNumbers: House AWB numbers
flightNumber: Departed flight
flightDate: Departure date
origin: IATA airport code (departure)
destination: IATA airport code (arrival)
pieces: Number of cargo pieces
weight: Total weight
volume: Total volume
ulds: Array of ULDs on flight
actualDepartureTime: Actual wheels-off time (ISO 8601)
scheduledDepartureTime: Original scheduled departure
departureDelay: Delay in minutes (0 if on time or early)
delayReason: Reason for delay (if applicable)
location: IATA airport code where status occurred
aircraftRegistration: Aircraft tail number
remarks: Additional notes
reportedBy: GHA ramp supervisor
submittedAt: Submission timestamp
Validation Rules:
\nDEP must be submitted after PRE status
\nActual departure time must be after scheduled time (or equal/earlier)
\nDEP cannot be submitted for future flights
\nFlight must have departed (confirmed by airport operations)
\nAll cargo must be manifested (FFM submitted)
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"dep-001\",\n \"statusReference\": \"DEP-GHA-KHI-20251128-001\",\n \"statusCode\": \"DEP\",\n \"mawbNumber\": \"176-12345678\",\n \"flightNumber\": \"EK-606\",\n \"actualDepartureTime\": \"2025-11-28T14:35:00Z\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:41:00Z\",\n \"broadcastPending\": true,\n \"broadcastTargets\": [\"Airline\", \"Customs\", \"PAA\", \"Pakistan Post\", \"ACA\", \"Consignor\", \"Customs Broker\", \"EPO\"],\n \"customsMRTrigger\": true,\n \"nextStep\": \"ACS will broadcast to all stakeholders and trigger Customs MR completion\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:41:00Z\",\n \"requestId\": \"req-dep-001\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"FLIGHT_NOT_DEPARTED\",\n \"message\": \"Cannot submit DEP status - flight has not departed yet\",\n \"details\": [\n {\n \"field\": \"actualDepartureTime\",\n \"issue\": \"Departure time is in the future. Current time: 2025-11-28T14:20:00Z, Provided: 2025-11-28T14:35:00Z\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:25:00Z\",\n \"requestId\": \"req-dep-001\"\n }\n}\n\nStatus Codes:
\n201: DEP status received successfully
\n400: Invalid data or business rule violation
\n401: Unauthorized
\n404: MAWB or flight not found
\n409: Duplicate status reference
\n500: Internal server error
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"ed3ffacb-be0b-4d18-93db-ef7bae28be06"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/departure-status-updates/xfsu","description":"Requirement Reference: G.E37GHA.68, G.E37AL.69, G.E37CUS.70
\nUse Case: Transmit/Receive Departure Status
\nDescription: GHA transmits Departure status to all stakeholders
\nProcess Flow:
\nE36GHA → ACS → Airline system
\nE36GHA → ACS → Customs
\nE36GHA → ACS → Pakistan Airport Authority
\nE36GHA → ACS → P
\nE36GHA → ACS → ACA
\nE36GHA → ACS → Consignor system
\nE36GHA → ACS → Customs Broker
\nE36GHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-XML (XFSU)
\nContent-Type: application/xml
XML Schema: IATA Cargo-XML 3.00 XFSU message with StatusCode=DEP
\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","departure-status-updates","xfsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"aa0fc09a-7d04-4dfe-a13f-69a8e515ceda"},{"name":"Departure Status Updates (IATA IMP FSU)","id":"e16e1a67-3952-4223-a48c-5ca173f42344","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"ea6a775c-3916-4c4f-b4b2-9d2463fc84bc"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/departure-status-updates/fsu","description":"Requirement Reference: G.E37GHA.68, G.E37AL.69, G.E37CUS.70
\nUse Case: Transmit/Receive Departure Status
\nDescription: GHA transmits Departure status to all stakeholders
\nProcess Flow:
\nE36GHA → ACS → Airline system
\nE36GHA → ACS → Customs
\nE36GHA → ACS → Pakistan Airport Authority
\nE36GHA → ACS → P
\nE36GHA → ACS → ACA
\nE36GHA → ACS → Consignor system
\nE36GHA → ACS → Customs Broker
\nE36GHA → ACS → EPO
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-IMP (FSU)
\nContent-Type: text/plain
FSU Format: Standard IATA Cargo-IMP with StatusCode=DEP
\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","departure-status-updates","fsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"e16e1a67-3952-4223-a48c-5ca173f42344"}],"id":"15ee2202-0745-42c4-966e-392613ab1ecc","_postman_id":"15ee2202-0745-42c4-966e-392613ab1ecc","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Offload","item":[{"name":"Offload Notifications (JSON)","id":"5260e4e8-2e89-406c-8762-0c78ae0bcb7b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"d179732f-82af-47ff-af54-c78eb153ce72"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/offload-notifications","description":"Requirement Reference: G.E38GHA.75, G.E38CGNR.76, G.E38ACA.77, G.E38AL.78, G.E38CUS.79, G.E38PAA.80, G.E38P.81
\nUse Case (from Excel IP #87): Manage/Receive Offload Updates
\nIntegration Point (from Excel IP #87): GHA manages and notifies all stakeholders about offloaded consignments
\nProcess Flow: E37GHA → E38GHA (GHA reports offload) → ACS → E38AL, E38CGNR, E38ACA, E38P, E38EPO, E38CUS, E38PAA (Stakeholders receive)
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → Airline, Consignor, ACA, Pakistan Post, EPO, Customs, PAA (receivers)
\nMessage Formats: JSON (this endpoint), IATA Cargo-XML (XFSU BKD, XFFM), IATA Cargo-IMP (FSU BKD, FFM)
\nBusiness Context:\nOffload occurs when cargo that was prepared for loading cannot be loaded onto the aircraft due to various operational constraints. Common offload reasons:
\nOperational Reasons:
\nRegulatory Reasons:
\nCommercial Reasons:
\nWhen offload occurs:
\nImpact on Stakeholders:
\nFor Airline:
\nFor Consignor:
\nFor ACA:
\nFor Customs:
\nFor EPO/Pakistan Post:
\nFor PAA:
\nIATA Status Code:
\nRequest Body Fields:
\noffloadReference: Unique offload notification identifierstatusCode: Always \"BKD\" (Booked/Rebooked)flightNumber: Flight from which cargo was offloadedflightDate: Original flight dateorigin: IATA airport codedestination: IATA airport codeoffloadDateTime: When cargo was offloaded (ISO 8601)offloadedShipments: Array of shipments removed from flightmawbNumber: Master AWB numberhawbNumbers: House AWB numberspieces: Number of piecesweight: Weightvolume: Volumeaca: Air Cargo Agent nameconsignor: Shipper nameoffloadReason: Reason code (from list above)offloadReasonDetails: Human-readable explanationulds: ULDs that were offloadedcurrentLocation: Where cargo is stored nowstorageChargesApplicable: Whether storage fees will be chargedremainingShipments: Cargo that remained on flight (summary)updatedFlightManifest: New manifest totals after offloadreportedBy: GHA personnel who reported offloadsubmittedAt: Submission timestampValidation Rules:
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"offload-001\",\n \"offloadReference\": \"OFL-GHA-KHI-20251128-001\",\n \"statusCode\": \"BKD\",\n \"flightNumber\": \"EK-606\",\n \"offloadedShipments\": 1,\n \"offloadedPieces\": 10,\n \"offloadedWeight\": 250.5,\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T14:26:00Z\",\n \"broadcastPending\": true,\n \"broadcastTargets\": [\"Airline\", \"Consignor\", \"ACA\", \"Pakistan Post\", \"EPO\", \"Customs\", \"PAA\"],\n \"customsSDCheck\": true,\n \"nextStep\": \"ACS will broadcast to all stakeholders. Customs will check for SD cancellation requirement.\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:26:00Z\",\n \"requestId\": \"req-offload-001\"\n }\n}\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"INVALID_OFFLOAD_REASON\",\n \"message\": \"Offload reason code is not valid\",\n \"details\": [\n {\n \"field\": \"offloadedShipments[0].offloadReason\",\n \"issue\": \"UNKNOWN_REASON is not a valid offload reason code. Valid codes: WEIGHT_RESTRICTION, SPACE_RESTRICTION, LATE_ARRIVAL, TECHNICAL_ISSUE, CUSTOMS_HOLD, SECURITY_ISSUE, etc.\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:26:00Z\",\n \"requestId\": \"req-offload-001\"\n }\n}\nStatus Codes:
\nTimestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"a50d236f-4fb2-44c4-889f-206769038c7b"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/offload-notifications/xfsu","description":"Requirement Reference: G.E38GHA.75, G.E38CGNR.76, G.E38ACA.77
\nUse Case (from Excel IP #88): Manage/Receive Offload Updates
\nIntegration Point (from Excel IP #88): GHA manages and notifies all stakeholders about offloaded consignments
\nProcess Flow: E37GHA → E38GHA → ACS → Broadcast
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-XML (XFSU)
\nContent-Type: application/xml
Business Context: XFSU with StatusCode=BKD indicates cargo was offloaded and rebooked. StatusReason provides offload explanation.
\nXML Schema: IATA Cargo-XML 3.00 XFSU message with StatusCode=BKD
\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","offload-notifications","xfsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"ab9e3fb2-e4e4-4346-b28a-e5db3de0d390"},{"name":"Offload Notifications (IATA IMP FSU BKD)","id":"433ccee4-4b41-4492-97e1-4941edd84904","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"fa1b4f50-69ac-4dd9-a248-96bfaf358704"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/offload-notifications/fsu","description":"Requirement Reference: G.E38GHA.75, G.E38CGNR.76, G.E38ACA.77
\nUse Case (from Excel IP #89): Manage/Receive Offload Updates
\nIntegration Point (from Excel IP #89): GHA manages and notifies all stakeholders about offloaded consignments
\nProcess Flow: E37GHA → E38GHA → ACS → Broadcast
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-IMP (FSU)
\nContent-Type: text/plain
FSU Format: Standard IATA Cargo-IMP with StatusCode=BKD
\nStatus Codes: Same as JSON endpoint
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","offload-notifications","fsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"433ccee4-4b41-4492-97e1-4941edd84904"},{"name":"Offload Updated Manifests (IATA XML XFFM)","id":"bf5eaab1-7c3f-49de-9925-cfe79d528e6e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"cee758f8-7e43-4af0-af1a-99909334179e"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/offload-notifications/xffm","description":"Payload: Flight Manifest (FFM/XFFM) data
\nRequirement Reference: G.E38GHA.75, G.E38AL.78, G.E38CUS.79
\nUse Case (from Excel IP #87): Manage Offload & Update Flight Manifest
\nIntegration Point (from Excel IP #87): GHA manages and notifies all stakeholders about offloaded consignments with updated manifest
\nProcess Flow: E38GHA → ACS → Broadcast
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-XML (XFFM Updated Manifest)
\nContent-Type: application/xml
Business Context:\nUpdated FFM (Flight Manifest) is sent after offload to reflect actual cargo loaded on aircraft. This replaces the original manifest and shows:
\nThis updated manifest is critical for:
\nXML Schema: IATA Cargo-XML 3.00 XFFM message with ManifestType=UPDATED
\nStatus Codes: Same as offload notification endpoints
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","offload-notifications","xffm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"bf5eaab1-7c3f-49de-9925-cfe79d528e6e"},{"name":"Offload Updated Manifests (IATA IMP FFM)","id":"b845b227-b2fc-4005-b037-eff2f3648036","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"b445abe4-d9ed-47fe-932d-4b1b93eefc7e"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/offload-notifications/ffm","description":"Payload: Flight Manifest (FFM/XFFM) data
\nRequirement Reference: G.E38GHA.75, G.E38AL.78, G.E38CUS.79
\nUse Case (from Excel IP #87): Manage Offload & Update Flight Manifest
\nIntegration Point (from Excel IP #87): GHA manages and notifies all stakeholders about offloaded consignments with updated manifest
\nProcess Flow: E38GHA → ACS → Broadcast
\nPriority: P1 (Critical Integration)
\nMessage Formats: IATA Cargo-IMP (FFM Updated Manifest)
\nContent-Type: text/plain
FFM Format: Standard IATA Cargo-IMP with UPDATED flag and OFFLOADED status
\nStatus Codes: Same as offload notification endpoints
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","offload-notifications","ffm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"b845b227-b2fc-4005-b037-eff2f3648036"}],"id":"aecdac49-c2f5-4145-beb3-0280b714037f","_postman_id":"aecdac49-c2f5-4145-beb3-0280b714037f","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"SD Cancellation","item":[{"name":"SD Cancellation Request Receipts","id":"12ec9c9f-6e59-44c8-84f4-00f49041b90b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Timestamp of the request in ISO 8601 format (YYYY-MM-DDTHH:mm:ss.sssZ)
\n","key":"X-Request-Timestamp","value":"1775395334"},{"description":"Identifier of the system making the request (e.g., ACA_SYSTEM, AIRLINE_SYSTEM, GHA_SYSTEM)
\n","key":"X-Request-System","value":"{{system_identifier}}"},{"key":"X-Request-ID","value":"96e377b6-a85f-4990-aaa5-31425fa6f8f1"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/export/sd-cancellation-requests/receipts","description":"Requirement Reference: G.E38CUS.79
\nUse Case (from Excel IP #93): Process SD Cancellation & Dray-off from Updated Manifest
\nIntegration Point (from Excel IP #93): ACS will allow Customs to initiate SD cancellation and begin the dray-off process based on the updated manifest, subject to the consignor's request.
\nProcess Flow: E38GHA → E38CUS (Customs receives offload) → E38CUS → ACS (Customs submits SD cancellation)
\nPriority: P1 (Critical Integration)
\nActors: Customs (sender) → ACS
\nBusiness Context:\nWhen cargo is offloaded from a flight, and a Shipping Declaration (SD) was already created in WeBOC customs system, the SD must be cancelled. This triggers the dray-off process:
\nWhat is SD (Shipping Declaration):
\nWhat is Dray-Off:\nDray-off is the customs process of removing cargo from the export manifest system when it does not actually depart:
\nWhen SD Cancellation Required:
\nWhen SD Cancellation NOT Required:
\nCancellation Reason Codes:
\nConsignor Request Flag:
\nfalse: SD cancellation due to operational offload (airline/GHA decision)true: SD cancellation requested by consignor (customer decision)Request Body Fields:
\ncancellationReference: Unique SD cancellation request IDoffloadReference: Links to offload notification that triggered thissdNumber: Shipping Declaration number in WeBOCmawbNumber: Master AWB numberhawbNumbers: House AWB numbersgdNumber: Goods Declaration numberflightNumber: Original flight numberflightDate: Original flight dateorigin: IATA airport codedestination: IATA airport codecancellationReason: Reason code (from list above)cancellationDetails: Human-readable explanationconsignorRequest: Boolean - was this requested by consignor?drayOffRequired: Boolean - does this require dray-off process? (usually true)submittedBy: Customs officer detailssubmittedAt: Submission timestampValidation Rules:
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"sd-cancel-001\",\n \"cancellationReference\": \"SDC-CUS-20251128-001\",\n \"sdNumber\": \"SD-2025-KHI-12345\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"PENDING_PROCESSING\",\n \"receivedAt\": \"2025-11-28T15:31:00Z\",\n \"drayOffInitiated\": true,\n \"nextStep\": \"ACS will process SD cancellation and initiate dray-off workflow in WeBOC\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T15:31:00Z\",\n \"requestId\": \"req-sd-cancel-001\"\n }\n}\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"SD_ALREADY_CANCELLED\",\n \"message\": \"Cannot cancel SD - it is already cancelled\",\n \"details\": [\n {\n \"field\": \"sdNumber\",\n \"issue\": \"SD-2025-KHI-12345 has status CANCELLED as of 2025-11-28T14:00:00Z\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T15:31:00Z\",\n \"requestId\": \"req-sd-cancel-001\"\n }\n}\nStatus Codes:
\nRequirement Reference: G.E16GHA.1
\nFunction: UPDATE Express Parcel Operator \"Allow Loading\"
\nUse Case: GHA receives \"allow loading\" message from Customs via EPO for items cleared by customs
\nDescription: ACS will enable GHA to receive digitally \"allow loading\" information from customs via Express Parcel Operator for items cleared by customs.
\nProcess Flow: E15EPO → E16GHA
\nPriority: P1 (Critical Integration)
\nActors: EPO (sender) → ACS → GHA (receiver)
\nMessage Formats: JSON
\nBusiness Context:
\nEPO has unique pre-clearance capability where items are cleared BEFORE loading
\n\"Allow Loading\" confirms customs clearance is complete
\nGHA can proceed with cargo acceptance and loading
\nPart of WCO Immediate Release Guidelines for express cargo
\nRequest Body Fields:
\nallowLoadingReference: Unique allow loading message ID
hawbNumber: EPO HAWB number (format: PKEPO00012345)
mawbNumber: Master AWB number (format: prefix-serial)
clearanceDate: Timestamp when customs cleared the item
customsOfficer: Name of customs officer who cleared
decision: Must be \"ALLOW_LOADING\" for this endpoint
pieces: Number of pieces cleared
weight: Total weight cleared
flightNumber: Scheduled flight
flightDate: Scheduled departure date
remarks: Additional clearance notes
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"allow-loading-001\",\n \"allowLoadingReference\": \"AL-EPO-12345\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T10:05:00Z\",\n \"ghaAcknowledged\": false\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T10:05:00Z\",\n \"requestId\": \"req-123456\"\n }\n}\n\nError Response (400 Bad Request):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"INVALID_HAWB\",\n \"message\": \"HAWB number format is invalid. EPO HAWBs must start with PKEPO\",\n \"details\": [\n {\n \"field\": \"hawbNumber\",\n \"issue\": \"Invalid format - expected PKEPO followed by 8 digits\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T10:05:00Z\",\n \"requestId\": \"req-123456\"\n }\n}\n\nStatus Codes:
\n201: Allow loading received successfully
\n400: Invalid request data
\n401: Unauthorized
\n409: Duplicate allow loading reference
\n500: Internal server error
\nRequirement Reference: G.E20EPO.2
\nFunction: Cargo delivered to GHA / XFWB+XFZB messages sent
\nUse Case: EPO delivers cargo to GHA with MAWB and HAWB data
\nDescription: ACS will enable Express Parcel Operator to digitally send MAWB and HAWB data on the delivery of the items to GHA and Airline.
\nProcess Flow: E15EPO → E20EPO → E21GHA (GHA), E20EPO → E24AL (Airline)
\nPriority: P1 (Critical Integration)
\nActors: EPO
\nMessage Formats: JSON (this endpoint), IATA Cargo-XML (XFWB, XFZB), IATA Cargo-IMP (FWB, FHL)
\nBusiness Context:
\nEPO physically delivers pre-cleared cargo to GHA facility
\nDigital delivery note includes both MAWB (Master) and HAWB (House) data
\nGHA uses this data for cargo acceptance and verification
\nAirline receives copy for manifest preparation
\nPart of paperless cargo handling initiative
\nRequest Body Fields:
\ndeliveryReference: Unique delivery transaction ID
deliveryDateTime: Physical delivery timestamp
mawb: Master Air Waybill data
hawb: House Air Waybill data
EPO HAWB number format: PKEPO + 8 digits
\nComplete shipper and consignee details
\nflightNumber: Scheduled flight
flightDate: Departure date
ghaFacility: GHA receiving facility
deliveredBy: EPO courier/driver ID
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"delivery-001\",\n \"deliveryReference\": \"DEL-EPO-12345\",\n \"status\": \"DELIVERED\",\n \"mawbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"deliveredAt\": \"2025-11-28T11:00:00Z\",\n \"ghaReceiptPending\": true,\n \"nextSteps\": \"Awaiting GHA cargo acceptance\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T11:05:00Z\",\n \"requestId\": \"req-123456\"\n }\n}\n\nStatus Codes:
\n201: Delivery recorded successfully
\n400: Invalid MAWB/HAWB data
\n401: Unauthorized
\n404: Flight not found
\n409: Duplicate delivery reference
\n500: Internal server error
\nRequirement Reference: G.E20EPO.2
\nFunction: Cargo delivered to GHA / XFWB messages sent (IATA Cargo-XML format)
\nUse Case: EPO sends MAWB data in IATA Cargo-XML format
\nDescription: ACS will enable Express Parcel Operator to digitally send MAWB and HAWB data on the delivery of the items to GHA and Airline.
\nProcess Flow: E15EPO → E20EPO → E21GHA, E24AL
\nPriority: P1 (Critical Integration)
\nActors: EPO
\nMessage Formats: IATA Cargo-XML (XFWB for MAWB)
\nContent-Type: application/xml
Business Context:
\nXFWB = Master Air Waybill message in IATA Cargo-XML format
\nIndustry standard for airline interoperability
\nUsed by airlines and ground handlers worldwide
\nSeparate XFZB message used for House Air Waybills
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"delivery-002\",\n \"format\": \"IATA_CARGO_XML\",\n \"messageType\": \"XFWB\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"RECEIVED\",\n \"parsedSuccessfully\": true\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T11:10:00Z\",\n \"requestId\": \"req-123457\"\n }\n}\n\nStatus Codes:
\n201: XML message received and parsed
\n400: Invalid XML or schema validation failed
\n401: Unauthorized
\n500: Internal server error
\nRequirement Reference: G.E20EPO.2
\nFunction: Cargo delivered to GHA / FWB messages sent (IATA Cargo-IMP format)
\nUse Case: EPO sends MAWB data in IATA Cargo-IMP format
\nDescription: ACS will enable Express Parcel Operator to digitally send MAWB and HAWB data on the delivery of the items to GHA and Airline.
\nProcess Flow: E15EPO → E20EPO → E21GHA, E24AL
\nPriority: P1 (Critical Integration)
\nActors: EPO
\nMessage Formats: IATA Cargo-IMP (FWB for MAWB)
\nContent-Type: text/plain
Business Context:
\nFWB = Freight Waybill message in legacy IATA Cargo-IMP format
\nWidely used format, especially by older airline systems
\nCryptic format but backward compatible
\nFHL message used for House Air Waybills
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"delivery-003\",\n \"format\": \"IATA_CARGO_IMP\",\n \"messageType\": \"FWB\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"RECEIVED\",\n \"parsedSuccessfully\": true\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T11:15:00Z\",\n \"requestId\": \"req-123458\"\n }\n}\n\nStatus Codes:
\n201: IMP message received and parsed
\n400: Invalid IMP format
\n401: Unauthorized
\n500: Internal server error
\nRequirement Reference: G.E21GHA.3
\nFunction: Cargo Acceptance - Weighing + measuring and piece count of the shipment / checking of packing for transport
\nUse Case: GHA performs physical cargo acceptance - weighing, measuring, piece count, packing inspection
\nDescription: ACS will enable GHA to transmit Cargo acceptance information digitally to Consignor, ACA, Airline and customs. ACS will enable GHA to transmit any irregularities on packing to EPO for corrective action digitally.
\nProcess Flow: E20EPO → E21GHA → E26GHA, E21AL
\nPriority: P1 (Critical Integration)
\nActors: GHA
\nMessage Formats: JSON
\nBusiness Context:
\nCritical checkpoint where GHA physically inspects cargo
\nWeighing: GHA weighs cargo (NOT truck full/empty) - best practice
\nMeasuring: Dimensions captured per piece for volumetric weight
\nPiece count: Verify expected vs actual pieces
\nPacking inspection: Check if packaging suitable for air transport
\nWeight variance: Minor differences acceptable, major discrepancies require investigation
\nPacking issues: If found, EPO must correct before loading
\nRequest Body Fields:
\nacceptanceReference: Unique acceptance transaction ID
mawbNumber, hawbNumber: Shipment identifiers
acceptanceDateTime: When GHA completed acceptance
deliveryReference: Links to delivery record
acceptedPieces: Actual pieces received
expectedPieces: Expected from MAWB/HAWB
actualWeight: Weighed by GHA
declaredWeight: From MAWB/HAWB
weightVariance: Difference between actual and declared
dimensions: Per-piece measurements
packingStatus: ACCEPTABLE, ISSUES_FOUND, REJECTED
packingIssues: Array of issues if found
inspectionNotes: Free-text observations
acceptedBy: GHA inspector ID
warehouseLocation: Where cargo stored
Packing Status Values:
\nACCEPTABLE: Packing suitable for transport
\nISSUES_FOUND: Minor issues, may need correction
\nREJECTED: Packing unsuitable, EPO must re-pack
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"acceptance-001\",\n \"acceptanceReference\": \"ACC-EPO-12345\",\n \"status\": \"ACCEPTED\",\n \"mawbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"acceptedAt\": \"2025-11-28T11:30:00Z\",\n \"weightVariancePercentage\": 0.78,\n \"packingStatus\": \"ACCEPTABLE\",\n \"readyForCarriage\": true,\n \"nextStep\": \"Security screening\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T11:35:00Z\",\n \"requestId\": \"req-123459\"\n }\n}\n\nError Response (422 Unprocessable Entity):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"PACKING_REJECTED\",\n \"message\": \"Cargo packaging rejected - unsuitable for air transport\",\n \"details\": [\n {\n \"field\": \"packingStatus\",\n \"issue\": \"REJECTED - EPO must re-pack cargo before resubmission\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T11:35:00Z\",\n \"requestId\": \"req-123459\"\n }\n}\n\nStatus Codes:
\n201: Cargo accepted
\n400: Invalid request data
\n401: Unauthorized
\n404: Delivery reference not found
\n422: Packing rejected or major discrepancy
\n500: Internal server error
\nRequirement Reference: G.E24AL.4
\nFunction: Receives MAWB + HAWB as XFWB + XFZB Express Parcel Operator
\nUse Case: Airline receives final MAWB + HAWB from EPO in IATA Cargo-XML format
\nDescription: ACS will enable Airlines to digitally receive final HAWB + MAWB from EPO.
\nProcess Flow: E20EPO → E24AL → E25AL
\nPriority: P1 (Critical Integration)
\nActors: Airline (receiver)
\nMessage Formats: IATA Cargo-XML (XFWB for MAWB, XFZB for HAWB)
\nContent-Type: application/xml
Business Context:
\nAirline receives copy of MAWB/HAWB for manifest preparation
\nUses actual weight from GHA cargo acceptance (25.7 kg vs declared 25.5 kg)
\nXFWB = Master Air Waybill message
\nXFZB = House Air Waybill message (separate call)
\nRequired for airline cargo systems and FFM (Flight Manifest) generation
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"airline-receipt-001\",\n \"format\": \"IATA_CARGO_XML\",\n \"messageType\": \"XFWB\",\n \"mawbNumber\": \"176-12345678\",\n \"airline\": \"EK\",\n \"status\": \"RECEIVED_BY_AIRLINE\",\n \"receivedAt\": \"2025-11-28T11:40:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T11:40:00Z\",\n \"requestId\": \"req-123460\"\n }\n}\n\nStatus Codes:
\n201: MAWB received by airline
\n400: Invalid XML format
\n401: Unauthorized
\n500: Internal server error
\nRequirement Reference: G.E24AL.4
\nFunction: Receives MAWB + HAWB as FWB + FHL Express Parcel Operator
\nUse Case: Airline receives final MAWB + HAWB from EPO in IATA Cargo-IMP format
\nDescription: ACS will enable Airlines to digitally receive final HAWB + MAWB from EPO.
\nProcess Flow: E20EPO → E24AL → E25AL
\nPriority: P1 (Critical Integration)
\nActors: Airline (receiver)
\nMessage Formats: IATA Cargo-IMP (FWB for MAWB, FHL for HAWB)
\nContent-Type: text/plain
Business Context:
\nLegacy IATA Cargo-IMP format
\nFWB = Freight Waybill (MAWB)
\nFHL = House Waybill List (HAWB)
\nBackward compatible with older airline systems
\nSame data as XML format, different encoding
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"airline-receipt-002\",\n \"format\": \"IATA_CARGO_IMP\",\n \"messageType\": \"FWB\",\n \"mawbNumber\": \"176-12345678\",\n \"airline\": \"EK\",\n \"status\": \"RECEIVED_BY_AIRLINE\",\n \"receivedAt\": \"2025-11-28T11:45:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T11:45:00Z\",\n \"requestId\": \"req-123461\"\n }\n}\n\nStatus Codes:
\n201: MAWB received by airline
\n400: Invalid IMP format
\n401: Unauthorized
\n500: Internal server error
\nRequirement Reference: G.E28EPO.5
\nFunction: E-CSD received
\nUse Case: EPO receives Electronic Consignment Security Declaration from GHA
\nDescription: ACS will enable Express Parcel Operator to receive this information in digital format.
\nProcess Flow: E28GHA → E28EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → EPO (receiver)
\nMessage Formats: JSON, IATA e-CSD XML
\nStandards Reference: IATA e-CSD standards, ICAO Doc 8973/Chapter 13/Appendix 33
\nBusiness Context:
\ne-CSD = Electronic Consignment Security Declaration
\nMandatory security document for all air cargo
\nCertifies cargo has been screened according to aviation security standards
\nIssued by entity responsible for screening (GHA in this case)
\nMust be signed by certified security personnel
\nRequired before cargo can be loaded onto aircraft
\nDigital replacement for paper security declaration
\nRequest Body Fields:
\necsdReference: Unique e-CSD document ID
mawbNumber, hawbNumber: Shipment identifiers
entityResponsible: Name of entity responsible for security (GHA)
commodityContent: Description of cargo screened
departureAirport, destinationAirport: Route
screeningMethod: X-RAY, ETD (Explosive Trace Detection), EDD (Explosive Detection Dog), PHYSICAL_INSPECTION
screeningDateTime: When screening performed
screeningResult: CLEAR, SUSPICIOUS, REJECTED
screeningLocation: Facility where screening done
personIssuingSecurity: Certified security officer details
dateOfIssuance, timeOfIssuance: e-CSD issuance timestamp
securityStatus: SECURE (cleared), UNDER_REVIEW, REJECTED
Screening Methods:
\nX-RAY: Most common for express cargo
\nETD: Explosive Trace Detection (swab test)
\nEDD: Explosive Detection Dog
\nPHYSICAL_INSPECTION: Manual inspection
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"ecsd-receipt-001\",\n \"ecsdReference\": \"ECSD-EPO-12345\",\n \"mawbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"status\": \"RECEIVED\",\n \"receivedAt\": \"2025-11-28T12:10:00Z\",\n \"securityStatus\": \"SECURE\",\n \"screeningMethod\": \"X-RAY\",\n \"readyForLoading\": true\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T12:10:00Z\",\n \"requestId\": \"req-123462\"\n }\n}\n\nError Response (422 Unprocessable Entity):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"SECURITY_CERTIFICATION_EXPIRED\",\n \"message\": \"Security officer certification has expired\",\n \"details\": [\n {\n \"field\": \"personIssuingSecurity.certificationExpiry\",\n \"issue\": \"Certification expired on 2025-11-01. Current date: 2025-11-28\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T12:10:00Z\",\n \"requestId\": \"req-123462\"\n }\n}\n\nStatus Codes:
\n201: e-CSD received successfully
\n400: Invalid e-CSD data
\n401: Unauthorized
\n404: HAWB not found
\n422: Security certification invalid or expired
\n500: Internal server error
\nRequirement Reference: G.E34GHA.6
\nFunction: Shipment is accepted by GHA / RCS status transmitted
\nUse Case: GHA transmits RCS (Ready for Carriage Status) to stakeholders
\nDescription: ACS will enable GHA to transmit Cargo accepted status RCS to Consignor, ACA, Airline and Express Parcel Operator.
\nProcess Flow: E28GHA → E34GHA → E34EPO, E35GHA
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → EPO, Airline, ACA, Consignor (receivers)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nFSU Status Code: RCS (Ready for Carriage/Shipment)
\nBusiness Context:
\nRCS = Ready for Carriage Status (IATA FSU code)
\nCritical milestone in export workflow
\nIndicates cargo has passed all checks:
\nPhysical acceptance completed
\nWeighing and measuring done
\nPacking verified
\nSecurity screening completed (e-CSD issued)
\nCustoms pre-clearance received (for EPO)
\nCargo ready to be loaded onto aircraft
\nTriggers notification to all stakeholders
\nEPO can inform shipper cargo is secure and ready
\nFSU Status Message:
\nFSU = Freight Status Update (IATA standard)
\nRCS = One of many FSU status codes
\nOther codes: PRE (Prepared), DEP (Departed), ARR (Arrived), etc.
\nRequest Body Fields:
\nstatusReference: Unique status message ID
awbNumber: Master AWB number
departureAirport, destinationAirport: Route
pieces: Number of pieces ready
weight: Actual weight (from cargo acceptance)
volume: Calculated volume
statusCode: Must be \"RCS\" for this endpoint
statusDescription: Human-readable description
statusDateTime: When status achieved
agent: GHA name
flightNumber, flightDate: Scheduled flight
warehouseLocation: Current cargo location
readyForLoading: Boolean flag
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"rcs-status-001\",\n \"statusReference\": \"RCS-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"statusCode\": \"RCS\",\n \"statusDateTime\": \"2025-11-28T12:30:00Z\",\n \"notificationsSent\": {\n \"epo\": true,\n \"airline\": true,\n \"aca\": false,\n \"consignor\": true\n },\n \"nextStatus\": \"PRE (Prepared for Loading)\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T12:35:00Z\",\n \"requestId\": \"req-123463\"\n }\n}\n\nStatus Codes:
\n201: RCS status recorded and broadcast
\n400: Invalid status data
\n401: Unauthorized
\n404: AWB not found
\n409: RCS already sent for this AWB
\n500: Internal server error
\nRequirement Reference: G.E34EPO.7
\nFunction: RCS status received
\nUse Case: EPO receives Ready for Carriage status from GHA
\nDescription: ACS will enable Express Parcel Operator to digitally receive ready for carriage status.
\nProcess Flow: E34GHA → E34EPO
\nPriority: P1 (Critical Integration)
\nActors: EPO (receiver)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nBusiness Context:
\nEPO receives notification that cargo is ready for carriage
\nConfirms all handling steps completed by GHA
\nEPO can now inform shipper of progress
\nPart of shipment tracking and visibility
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"rcs-receipt-001\",\n \"statusReference\": \"RCS-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"status\": \"ACKNOWLEDGED\",\n \"acknowledgedAt\": \"2025-11-28T12:32:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T12:32:00Z\",\n \"requestId\": \"req-123464\"\n }\n}\n\nStatus Codes:
\n201: RCS receipt acknowledged
\n400: Invalid receipt data
\n401: Unauthorized
\n404: Status reference not found
\n500: Internal server error
\nRequirement Reference: G.E35GHA.8
\nFunction: Cargo prepared for loading
\nUse Case: GHA transmits PRE (Prepared for Loading) status to EPO
\nDescription: ACS will enable GHA to transmit Cargo being prepared for loading status PRE to Express Parcel Operator.
\nProcess Flow: E34GHA → E35GHA → E35EPO, E37GHA
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → EPO (receiver)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nFSU Status Code: PRE (Prepared for Loading)
\nBusiness Context:
\nPRE = Prepared for Loading (IATA FSU code)
\nFollows RCS status in the workflow
\nIndicates cargo is being prepared for physical loading onto aircraft
\nMay be placed in ULD (Unit Load Device) or bulk cargo hold
\nImminent loading - typically 1-3 hours before departure
\nFinal operational status before departure
\nRequest Body Fields:
\nstatusReference: Unique status message ID
awbNumber: Master AWB number
statusCode: Must be \"PRE\" for this endpoint
statusDateTime: When preparation started
uldNumber: ULD number if containerized (optional for express cargo)
loadingPosition: Where cargo will be loaded (ULD or bulk position)
estimatedLoadingTime: When loading expected to occur
ULD (Unit Load Device):
\nContainer or pallet used for loading cargo
\nExpress cargo often loaded as bulk (not in ULD)
\nULD number format: Type + Serial + Airline (e.g., AKE12345EK)
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"pre-status-001\",\n \"statusReference\": \"PRE-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"statusCode\": \"PRE\",\n \"statusDateTime\": \"2025-11-28T14:00:00Z\",\n \"notificationsSent\": {\n \"epo\": true\n },\n \"nextStatus\": \"DEP (Departed)\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:05:00Z\",\n \"requestId\": \"req-123465\"\n }\n}\n\nStatus Codes:
\n201: PRE status recorded and sent
\n400: Invalid status data
\n401: Unauthorized
\n404: AWB not found or RCS not sent yet
\n409: PRE already sent
\n500: Internal server error
\nRequirement Reference: G.E35EPO.9
\nFunction: Status update
\nUse Case: EPO receives PRE (Prepared for Loading) status from GHA
\nIntegration Point: ACS will enable Express Parcel Operator to receive this information digital format.
\nProcess Flow: E35GHA → E35EPO
\nPriority: P1 (Critical Integration)
\nActors: EPO (receiver)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nBusiness Context:
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"pre-receipt-001\",\n \"statusReference\": \"PRE-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"status\": \"ACKNOWLEDGED\",\n \"acknowledgedAt\": \"2025-11-28T14:02:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T14:02:00Z\",\n \"requestId\": \"req-123466\"\n }\n}\nStatus Codes:
\nRequirement Reference: G.E37GHA.10
\nFunction: Departure message received
\nUse Case: GHA transmits DEP (Departed) status to all stakeholders
\nDescription: ACS will enable GHA to transmit departure status to Airline, ACA, Consignor, Customs, CB, PAA, EPO, Post digitally.
\nProcess Flow: E35GHA → E37GHA → E38GHA, E37EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → EPO, Airline, ACA, Consignor, Customs, CB, PAA, Post (receivers)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nFSU Status Code: DEP (Departed)
\nBusiness Context:
\nDEP = Departed (IATA FSU code)
\nMost critical status update in export workflow
\nConfirms cargo loaded and flight departed
\nSent after aircraft wheels-up (takeoff)
\nTriggers multiple downstream actions:
\nEPO notifies shipper of departure
\nCustoms closes export record
\nAirline updates manifest
\nDestination airport prepares for arrival
\nConsignee/ACA notified of imminent arrival
\nIncludes actual departure time (not scheduled)
\nPart of international tracking chain
\nRequest Body Fields:
\nstatusReference: Unique departure status ID
awbNumber: Master AWB number
statusCode: Must be \"DEP\" for this endpoint
statusDateTime: Actual departure timestamp (wheels-up)
actualDepartureTime: Same as statusDateTime for clarity
estimatedArrivalTime: ETA at destination
manifestReference: Reference to flight manifest (FFM)
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"dep-status-001\",\n \"statusReference\": \"DEP-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"statusCode\": \"DEP\",\n \"statusDateTime\": \"2025-11-28T18:15:00Z\",\n \"flightNumber\": \"EK-606\",\n \"notificationsSent\": {\n \"epo\": true,\n \"airline\": true,\n \"aca\": true,\n \"consignor\": true,\n \"customs\": true,\n \"customsBroker\": true,\n \"paa\": true,\n \"post\": true\n },\n \"broadcastComplete\": true,\n \"nextStatus\": \"ARR (Arrived at destination)\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T18:20:00Z\",\n \"requestId\": \"req-123467\"\n }\n}\n\nStatus Codes:
\n201: DEP status recorded and broadcast to all stakeholders
\n400: Invalid status data
\n401: Unauthorized
\n404: AWB or flight not found
\n409: DEP already sent
\n500: Internal server error
\nRequirement Reference: G.E37EPO.11
\nFunction: Departure message received
\nUse Case: EPO receives DEP (Departed) status from GHA
\nDescription: ACS will enable Express Parcel Operator receive this information digital format.
\nProcess Flow: E37GHA → E37EPO
\nPriority: P1 (Critical Integration)
\nActors: EPO (receiver)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nBusiness Context:
\nEPO receives confirmation of departure
\nTriggers shipper notification of successful export
\nBegins destination tracking
\nEPO destination office prepares for arrival
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"dep-receipt-001\",\n \"statusReference\": \"DEP-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"status\": \"ACKNOWLEDGED\",\n \"acknowledgedAt\": \"2025-11-28T18:17:00Z\",\n \"shipperNotified\": true\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T18:17:00Z\",\n \"requestId\": \"req-123468\"\n }\n}\n\nStatus Codes:
\n201: DEP receipt acknowledged
\n400: Invalid receipt data
\n401: Unauthorized
\n404: Status reference not found
\n500: Internal server error
\nRequirement Reference: G.E38GHA.12
\nFunction: In case of offloading
\nUse Case: GHA notifies EPO and stakeholders of offloaded cargo with new booking
\nDescription: ACS will enable GHA to transmit updated consignment status, in case of offloaded consignment, to Consignor, ACA, Post and Express Parcel Operator.
\nProcess Flow: E37GHA → E38GHA → E38EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → EPO, ACA, Post, Consignor (receivers)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nFSU Status Code: BKD (Booked)
\nBusiness Context:
\nOffloading occurs when cargo cannot be loaded on scheduled flight
\nCommon reasons:
\nWeight restrictions (aircraft weight limits)
\nVolume restrictions (cargo hold full)
\nLate arrival at airport
\nTechnical issues with aircraft
\nPrioritization (higher priority cargo takes space)
\nGHA immediately re-books cargo on next available flight
\nCritical to notify all stakeholders quickly
\nHigh priority notification
\nEPO must inform shipper of delay
\nMay impact delivery commitments
\nOffload Reasons:
\nWEIGHT_RESTRICTION: Aircraft weight limit
\nVOLUME_RESTRICTION: Cargo hold full
\nLATE_ARRIVAL: Cargo arrived after cut-off
\nAIRCRAFT_TECHNICAL: Technical issue
\nPRIORITY_CARGO: Higher priority cargo took space
\nWEATHER: Weather-related offload
\nOTHER: Other operational reasons
\nRequest Body Fields:
\nstatusReference: Unique offload notification ID
awbNumber: Master AWB number
originalFlightNumber, originalFlightDate: Missed flight
offloadReason: Reason code (see above)
offloadDateTime: When offload decision made
statusCode: \"BKD\" (Booked on new flight)
newBooking: New flight booking details
flightNumber: Next available flight
flightDate: New departure date
departureTime, estimatedArrivalTime: New schedule
bookingReference: New booking ID
notificationPriority: HIGH (offloads are urgent)
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"offload-001\",\n \"statusReference\": \"BKD-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"offloadReason\": \"WEIGHT_RESTRICTION\",\n \"originalFlight\": \"EK-606 on 2025-11-28\",\n \"newFlight\": \"EK-608 on 2025-11-29\",\n \"delayHours\": 24,\n \"notificationsSent\": {\n \"epo\": true,\n \"aca\": true,\n \"post\": true,\n \"consignor\": true\n },\n \"priorityAlert\": true,\n \"status\": \"RE_BOOKED\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T17:50:00Z\",\n \"requestId\": \"req-123469\"\n }\n}\n\nStatus Codes:
\n201: Offload notification sent, cargo re-booked
\n400: Invalid notification data
\n401: Unauthorized
\n404: AWB or flight not found
\n409: Cargo already departed (too late to offload)
\n500: Internal server error
\nRequirement Reference: G.E38EPO.13
\nFunction: Status update
\nUse Case: EPO receives offload notification from GHA
\nDescription: ACS will enable Express Parcel Operator to receive this information in case of offloading of the items in digital format.
\nProcess Flow: E38GHA → E38EPO
\nPriority: P1 (Critical Integration)
\nActors: EPO (receiver)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nBusiness Context:
\nEPO receives urgent notification of offload
\nMust immediately inform shipper of delay
\nUpdate delivery commitments
\nCoordinate with destination office
\nMay offer compensation or alternate service
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"offload-receipt-001\",\n \"statusReference\": \"BKD-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"status\": \"ACKNOWLEDGED\",\n \"acknowledgedAt\": \"2025-11-28T17:52:00Z\",\n \"shipperNotified\": true,\n \"escalated\": false\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T17:52:00Z\",\n \"requestId\": \"req-123470\"\n }\n}\n\nStatus Codes:
\n201: Offload receipt acknowledged
\n400: Invalid receipt data
\n401: Unauthorized
\n404: Status reference not found
\n500: Internal server error
\nUse Case: List all EPO export shipments with filtering and pagination
\nPriority: P2
\nActors: EPO, GHA, Airline
\nQuery Parameters:
\nstatus: Filter by shipment statusdateFrom, dateTo: Date range filterflightNumber: Filter by flighthawbNumber: Search by HAWBpage: Page number (default 1)limit: Results per page (default 20, max 100)Success Response (200 OK):
\n{\n \"success\": true,\n \"data\": [\n {\n \"id\": \"shipment-001\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"IN_TRANSIT\",\n \"currentStatus\": \"DEP\",\n \"flightNumber\": \"EK-606\",\n \"flightDate\": \"2025-11-28\",\n \"pieces\": 5,\n \"weight\": 25.7,\n \"weightUnit\": \"kg\",\n \"origin\": \"KHI\",\n \"destination\": \"DXB\",\n \"departedAt\": \"2025-11-28T18:15:00Z\",\n \"estimatedArrival\": \"2025-11-28T20:45:00Z\"\n }\n ],\n \"meta\": {\n \"pagination\": {\n \"currentPage\": 1,\n \"totalPages\": 5,\n \"pageSize\": 20,\n \"totalCount\": 87\n },\n \"timestamp\": \"2025-11-28T19:00:00Z\",\n \"requestId\": \"req-123471\"\n }\n}\nStatus Codes:
\nFilter by status: ALLOW_LOADING_RECEIVED, DELIVERED_TO_GHA, ACCEPTED, READY_FOR_CARRIAGE, PREPARED, DEPARTED, OFFLOADED
\n","type":"text/plain"},"key":"status","value":"IN_TRANSIT"},{"description":{"content":"Start date for date range filter
\n","type":"text/plain"},"key":"dateFrom","value":"2025-11-01"},{"description":{"content":"End date for date range filter
\n","type":"text/plain"},"key":"dateTo","value":"2025-11-30"},{"description":{"content":"Filter by flight number
\n","type":"text/plain"},"key":"flightNumber","value":"EK-606"},{"description":{"content":"Filter by HAWB number
\n","type":"text/plain"},"key":"hawbNumber","value":"PKEPO00012345"},{"description":{"content":"Page number (default: 1)
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Results per page (default: 20, max: 100)
\n","type":"text/plain"},"key":"limit","value":"20"}],"variable":[]}},"response":[],"_postman_id":"512f68f0-2dc9-46a4-aa82-4546c9ad24aa"}],"id":"6e2664fc-082b-450f-9136-72bdae64d651","_postman_id":"6e2664fc-082b-450f-9136-72bdae64d651","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"EPO Import Operations","item":[{"name":"Arrival Receipts (ARR/RCF)","id":"5f69581d-9740-447e-bdb9-128661fd70ff","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"X-Request-ID","value":"b6a6d184-748e-4c33-b552-30e36420d4fc"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/epo/import/arrival-receipts","description":"Requirement Reference: G.I10EPO.1
\nFunction: Receives arrival notice
\nUse Case: EPO receives arrival information in digital format
\nDescription: ACS will enable Express Parcel Operator to receive arrival information in digital format.
\nProcess Flow: I3EPO → I10EPO → I11EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → EPO (receiver)
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nFSU Status Codes: ARR (Arrived), RCF (Received from Flight)
\nBusiness Context:
\nARR/RCF = First status update for import cargo
\nSent when cargo unloaded from aircraft and received by GHA
\nARR = Aircraft arrived (flight-level status)
\nRCF = Cargo received from flight (piece-level status)
\nTriggers EPO import workflow
\nEPO uses this to prepare for customs clearance and delivery
\nPart of international tracking chain
\nRequest Body Fields:
\narrivalReference: Unique arrival notification ID
awbNumber: Master AWB number
hawbNumber: EPO HAWB number
flightNumber: Arriving flight
arrivalDate, arrivalTime: Actual arrival timestamp
statusCode: \"ARR\" or \"RCF\"
departureAirport, destinationAirport: Route
pieces: Number of pieces received
weight: Actual weight
cargoCondition: INTACT, DAMAGED, PARTIAL
warehouseLocation: Where cargo stored after unloading
receivedBy: GHA officer who received cargo
Cargo Condition Values:
\nINTACT: All pieces received in good condition
\nDAMAGED: Damage noted during unloading
\nPARTIAL: Not all pieces received (shortage)
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"arrival-001\",\n \"arrivalReference\": \"ARR-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"statusCode\": \"ARR\",\n \"arrivalDateTime\": \"2025-11-28T20:15:00Z\",\n \"cargoCondition\": \"INTACT\",\n \"receivedAt\": \"2025-11-28T20:20:00Z\",\n \"nextStep\": \"Delivery order issuance\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T20:20:00Z\",\n \"requestId\": \"req-123456\"\n }\n}\n\nError Response (422 Unprocessable Entity):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"CARGO_DAMAGED\",\n \"message\": \"Cargo received with damage - inspection required\",\n \"details\": [\n {\n \"field\": \"cargoCondition\",\n \"issue\": \"DAMAGED - 2 pieces show external damage, detailed inspection report required\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T20:20:00Z\",\n \"requestId\": \"req-123456\"\n }\n}\n\nStatus Codes:
\n201: Arrival received successfully
\n400: Invalid arrival data
\n401: Unauthorized
\n404: Flight or AWB not found
\n422: Cargo condition issues (damage, shortage)
\n500: Internal server error
\nRequirement Reference: G.I15GHA.2
\nFunction: Issues delivery order (e-DO)
\nUse Case: GHA issues electronic Delivery Order to EPO
\nDescription: ACS will enable GHA to issue delivery order digitally to EPO.
\nProcess Flow: I13GHA → I15GHA → I16EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA
\nMessage Formats: JSON
\nBusiness Context:
\ne-DO = Electronic Delivery Order
\nAuthorizes EPO to collect cargo from GHA warehouse
\nIssued after customs clearance completed
\nEPO must pay e-DO fee before collection
\nReplaces paper delivery order
\nValid for limited period (typically 7 days)
\nCritical document for cargo release
\nRequest Body Fields:
\ndoReference: Unique e-DO reference number
awbNumber, hawbNumber: Shipment identifiers
issueDateTime: When e-DO issued
consignee: Complete consignee details including CNIC
pieces, weight: Cargo details
warehouseLocation: Where cargo located
gdNumber: Customs Goods Declaration number
gdStatus: Must be \"CLEARED\" to issue e-DO
clearedDate: When customs clearance completed
releaseConditions: Any special conditions
doFee: e-DO fee amount
currency: Fee currency (typically PKR)
validUntil: e-DO expiry date
issuedBy: GHA officer ID
GD Status Requirements:
\nMust be \"CLEARED\" before e-DO can be issued
\nIf \"UNDER_REVIEW\", \"EXAMINATION_REQUIRED\", or \"HELD\" - cannot issue e-DO
\nIf \"REJECTED\" - shipment cannot be released
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"edo-001\",\n \"doReference\": \"EDO-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"status\": \"ISSUED\",\n \"issuedAt\": \"2025-11-29T09:00:00Z\",\n \"doFee\": 1000,\n \"currency\": \"PKR\",\n \"paymentStatus\": \"UNPAID\",\n \"validUntil\": \"2025-12-06T23:59:59Z\",\n \"nextStep\": \"EPO must pay e-DO fee to collect cargo\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T09:05:00Z\",\n \"requestId\": \"req-123457\"\n }\n}\n\nError Response (422 Unprocessable Entity):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"CUSTOMS_NOT_CLEARED\",\n \"message\": \"Cannot issue e-DO - customs clearance not completed\",\n \"details\": [\n {\n \"field\": \"gdStatus\",\n \"issue\": \"GD status is UNDER_REVIEW - must be CLEARED before e-DO issuance\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T09:05:00Z\",\n \"requestId\": \"req-123457\"\n }\n}\n\nStatus Codes:
\n201: e-DO issued successfully
\n400: Invalid e-DO data
\n401: Unauthorized
\n404: AWB or GD not found
\n422: Customs not cleared or other blocking condition
\n500: Internal server error
\nRequirement Reference: G.I16EPO.3, G.I17GHA.4
\nFunction: E-DO received / Payment received for e-DO
\nUse Case: EPO pays e-DO fee via PSW payment gateway
\nDescription: ACS will enable Express Parcel Operator to receive delivery order in digital format. ACS will enable GHA to receive payment for e-delivery order via payment gateway from EPO digitally.
\nProcess Flow: I15GHA → I16EPO → I17GHA (via Payment Gateway) → I21GHA
\nPriority: P1 (Critical Integration)
\nActors: EPO (payer) → PSW UPS (Payment Gateway) → GHA (receiver)
\nMessage Formats: JSON
\nPayment Gateway: PSW UPS (Unified Payment System)
\nBusiness Context:
\nEPO must pay e-DO fee before collecting cargo
\nPayment processed through PSW Unified Payment System (UPS)
\nPSID = PSW System ID for payment tracking
\nReal-time payment confirmation
\nGHA receives payment notification
\nPayment enables cargo release
\nReceipt generated automatically
\nRequest Body Fields:
\npaymentReference: Unique payment transaction ID
doReference: e-DO reference being paid
doId: e-DO record ID from ACS
paymentDateTime: When payment made
amount: Payment amount
currency: Payment currency
paymentMethod: Payment method (PSW_UPS, BANK_TRANSFER, etc.)
psid: PSW System ID for payment
transactionId: Bank/gateway transaction ID
paymentStatus: COMPLETED, PENDING, FAILED
paidBy: EPO officer making payment
receiptNumber: Official receipt number
Payment Methods:
\nPSW_UPS: PSW Unified Payment System (primary)
\nBANK_TRANSFER: Direct bank transfer
\nONLINE_BANKING: Internet banking
\nCREDIT_CARD: Credit card payment
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"payment-001\",\n \"paymentReference\": \"PAY-EDO-12345\",\n \"doReference\": \"EDO-EPO-12345\",\n \"amount\": 1000,\n \"currency\": \"PKR\",\n \"paymentStatus\": \"COMPLETED\",\n \"paidAt\": \"2025-11-29T09:30:00Z\",\n \"receiptNumber\": \"RCP-EDO-12345\",\n \"receiptUrl\": \"https://acs.psw.gov.pk/receipts/RCP-EDO-12345.pdf\",\n \"doStatus\": \"PAID\",\n \"readyForCollection\": true\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T09:35:00Z\",\n \"requestId\": \"req-123458\"\n }\n}\n\nError Response (422 Unprocessable Entity):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"PAYMENT_FAILED\",\n \"message\": \"Payment processing failed at gateway\",\n \"details\": [\n {\n \"field\": \"paymentStatus\",\n \"issue\": \"Payment gateway returned FAILED - insufficient funds\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T09:35:00Z\",\n \"requestId\": \"req-123458\"\n }\n}\n\nStatus Codes:
\n201: Payment processed successfully
\n400: Invalid payment data
\n401: Unauthorized
\n404: e-DO not found
\n409: e-DO already paid
\n422: Payment failed at gateway
\n500: Internal server error
\nRequirement Reference: G.I21EPO.5
\nFunction: Update received
\nUse Case: EPO receives handling & storage charges invoice from GHA
\nDescription: ACS will enable GHA to issue invoice for handling & storage digitally to Express Parcel Operator.
\nProcess Flow: I20GHA → I21EPO → I22EPO
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → EPO (receiver)
\nMessage Formats: JSON, E-invoice
\nPayment Gateway: PSW UPS (for B2B payments)
\nBusiness Context:
\nGHA charges handling and storage fees for import cargo
\nHandling charge: One-time fee for cargo handling
\nStorage charge: Daily fee for warehouse storage
\nFree storage period: Typically 24-48 hours
\nAfter free period: Daily storage charges apply
\nEPO must pay before cargo can be released
\nInvoice integrated with PSW UPS for B2B payments
\nRequest Body Fields:
\ninvoiceReference: Unique invoice number
awbNumber, hawbNumber: Shipment identifiers
invoiceDate: Invoice issuance date
charges: Detailed charge breakdown
handlingCharge: One-time handling fee
storageDays: Number of days in storage
storageChargePerDay: Daily storage rate
totalStorageCharge: Storage days × rate
securityCharge: Security screening fee
documentationCharge: Document processing fee
otherCharges: Miscellaneous charges
subtotal: Sum of all charges
tax: Sales tax amount
taxRate: Tax rate percentage
totalAmount: Subtotal + tax
currency: Invoice currency
chargeTo: Who pays (EPO, ACA, Consignee)
dueDate: Payment due date
paymentTerms: Payment terms description
issuedBy: GHA finance officer
Storage Charge Calculation:
\nFree period: 24 hours (Day 0)
\nDay 1: First chargeable day
\nExample: Arrived 2025-11-28 20:15, Free until 2025-11-29 20:15
\nStorage from 2025-11-29 20:15 onwards is chargeable
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"invoice-receipt-001\",\n \"invoiceReference\": \"INV-GHA-12345\",\n \"awbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"totalAmount\": 4720,\n \"currency\": \"PKR\",\n \"receivedAt\": \"2025-11-29T10:05:00Z\",\n \"dueDate\": \"2025-12-06\",\n \"paymentStatus\": \"UNPAID\",\n \"psid\": \"PSID-2025-11-29-67890\",\n \"paymentLink\": \"https://ups.psw.gov.pk/pay/PSID-2025-11-29-67890\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T10:05:00Z\",\n \"requestId\": \"req-123459\"\n }\n}\n\nStatus Codes:
\n201: Invoice received by EPO
\n400: Invalid invoice data
\n401: Unauthorized
\n404: AWB not found
\n409: Invoice already issued
\n500: Internal server error
\nRequirement Reference: G.I22EPO.7
\nFunction: Payment for Handling & storage fees
\nUse Case: EPO pays handling & storage fees to GHA via payment gateway
\nDescription: ACS will enable Express Parcel Operator to make the payment of handling & storage fees via payment gateway to GHA.
\nProcess Flow: I21EPO → I22EPO → I22GHA (via Payment Gateway)
\nPriority: P1 (Critical Integration)
\nActors: EPO (payer) → PSW UPS → GHA (receiver)
\nMessage Formats: JSON
\nPayment Gateway: PSW UPS (B2B payments)
\nBusiness Context:
\nEPO pays handling & storage invoice
\nRequired before cargo can be collected
\nB2B payment through PSW UPS
\nAutomatic receipt generation
\nGHA receives payment notification
\nFinal financial settlement before release
\nRequest Body Fields:
\npaymentReference: Unique payment ID
invoiceReference: Invoice being paid
invoiceId: Invoice record ID
paymentDateTime: Payment timestamp
amount: Payment amount (must match invoice)
currency: Payment currency
paymentMethod: Payment method (PSW_UPS)
psid: PSW System ID
transactionId: Gateway transaction ID
paymentStatus: COMPLETED, PENDING, FAILED
paidBy: EPO officer
receiptNumber: Official receipt
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"handling-payment-001\",\n \"paymentReference\": \"PAY-GHA-12345\",\n \"invoiceReference\": \"INV-GHA-12345\",\n \"amount\": 4720,\n \"currency\": \"PKR\",\n \"paymentStatus\": \"COMPLETED\",\n \"paidAt\": \"2025-11-29T11:00:00Z\",\n \"receiptNumber\": \"RCP-GHA-12345\",\n \"receiptUrl\": \"https://acs.psw.gov.pk/receipts/RCP-GHA-12345.pdf\",\n \"invoiceStatus\": \"PAID\",\n \"ghaNotified\": true\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T11:05:00Z\",\n \"requestId\": \"req-123460\"\n }\n}\n\nStatus Codes:
\n201: Payment processed successfully
\n400: Invalid payment data
\n401: Unauthorized
\n404: Invoice not found
\n409: Invoice already paid
\n422: Payment failed at gateway or amount mismatch
\n500: Internal server error
\nRequirement Reference: G.I24EPO.8
\nFunction: Payment received / Shipment out for delivery
\nUse Case: EPO receives shipment release after payment & clearance / Shipment out for delivery
\nDescription: ACS will enable Express Parcel Operator to digitally receives payment for duties, taxes and transportation costs. ACS will enable Express Parcel Operator to digitally inform consignee, that the shipment is out for delivery.
\nProcess Flow: I23GHA → I24EPO → I28EPO (via Payment Gateway I22FIN → I24EPO)
\nPriority: P1 (Critical Integration)
\nActors: GHA (sender) → ACS → EPO, Consignee (receivers)
\nMessage Formats: JSON
\nBusiness Context:
\nFinal release of cargo to EPO after all conditions met
\nRequirements for release:
\nCustoms clearance completed (GD status = CLEARED)
\ne-DO fee paid
\nHandling & storage fees paid
\nValid e-DO presented
\nPhysical handover of cargo from GHA to EPO
\nEPO courier collects cargo with vehicle
\nCargo now \"out for delivery\" to consignee
\nTriggers consignee notification
\nRelease Conditions Checklist:
\n✓ Customs cleared
\n✓ e-DO issued and paid
\n✓ Handling fees paid
\n✓ Authorized person collecting
\n✓ Valid ID (CNIC) presented
\n✓ Vehicle registered
\nRequest Body Fields:
\nreleaseReference: Unique release transaction ID
awbNumber, hawbNumber: Shipment identifiers
releaseDateTime: When cargo released
doReference: e-DO reference
doPaid: e-DO payment status (must be true)
doPaymentReference: e-DO payment ID
handlingInvoiceReference: Handling invoice reference
handlingPaid: Handling payment status (must be true)
handlingPaymentReference: Handling payment ID
gdNumber: Goods Declaration number
gdStatus: Must be \"CLEARED\"
customsClearanceDate: When cleared
pieces, weight: Cargo details
releasedTo: Person collecting cargo
warehouseLocation: Collection point
releasedBy: GHA officer releasing cargo
releaseNotes: Additional notes
Success Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"release-001\",\n \"releaseReference\": \"REL-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"status\": \"RELEASED\",\n \"releasedAt\": \"2025-11-29T11:30:00Z\",\n \"releasedTo\": \"EPO-Courier-456\",\n \"vehicleRegistration\": \"KHI-5678\",\n \"outForDelivery\": true,\n \"consigneeNotified\": true,\n \"nextStep\": \"Delivery to consignee with POD\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T11:35:00Z\",\n \"requestId\": \"req-123461\"\n }\n}\n\nError Response (422 Unprocessable Entity):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"PAYMENT_NOT_COMPLETE\",\n \"message\": \"Cannot release cargo - payments not complete\",\n \"details\": [\n {\n \"field\": \"handlingPaid\",\n \"issue\": \"Handling & storage fees not paid - invoice INV-GHA-12345 pending\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T11:35:00Z\",\n \"requestId\": \"req-123461\"\n }\n}\n\nStatus Codes:
\n201: Cargo released to EPO
\n400: Invalid release data
\n401: Unauthorized
\n404: Shipment not found
\n422: Release conditions not met (payments pending, customs not cleared)
\n500: Internal server error
\nRequirement Reference: G.I28EPO.9
\nFunction: Delivery to Consignee
\nUse Case: EPO confirms delivery to consignee with Proof of Delivery (POD)
\nDescription: ACS will enable Express Parcel Operator to digitally communicate to Consignor, Consignee shipment delivered information.
\nProcess Flow: I24EPO → I28EPO → I28CGNR, I28CNE
\nPriority: P1 (Critical Integration)
\nActors: EPO
\nMessage Formats: JSON, IATA Cargo-XML (XFSU), IATA Cargo-IMP (FSU)
\nFSU Status Code: DLV (Delivered)
\nBusiness Context:
\nDLV = Delivered (IATA FSU code)
\nFinal status in import workflow
\nConfirms successful delivery to consignee
\nPOD = Proof of Delivery (mandatory for EPO)
\nPOD requirements:
\nReceiver name and CNIC
\nSignature (digital or scanned)
\nPhoto of delivered cargo (optional but recommended)
\nTimestamp and location
\nPOD protects EPO from disputes
\nNotifies shipper of successful delivery
\nCloses shipment lifecycle
\nReceiver Relation Values:
\nSELF: Consignee personally received
\nAUTHORIZED_PERSON: Authorized representative
\nFAMILY_MEMBER: Family member of consignee
\nEMPLOYEE: Company employee
\nNEIGHBOR: Neighbor (with authorization)
\nRequest Body Fields:
\ndeliveryReference: Unique delivery confirmation ID
awbNumber, hawbNumber: Shipment identifiers
statusCode: Must be \"DLV\"
deliveryDateTime: Actual delivery timestamp
deliveryAddress: Where cargo delivered
consignee: Consignee details
pieces, weight: Cargo details
proofOfDelivery: POD details
receiverName: Who received the cargo
receiverCNIC: Receiver's CNIC for verification
receiverSignature: Base64-encoded signature image
receiverRelation: Relation to consignee
deliveryPhoto: Base64-encoded photo (optional)
podDateTime: POD timestamp
deliveryNotes: Any special notes
deliveredBy: Courier details
consignorNotification: Send notification to shipper
shipper: Shipper contact for notification
POD Image Requirements:
\nSignature: Max 500KB, PNG/JPG format
\nDelivery photo: Max 5MB, PNG/JPG format
\nBase64 encoding for transmission
\nImages stored for minimum 2 years (regulatory requirement)
\nSuccess Response (201 Created):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"delivery-001\",\n \"deliveryReference\": \"DLV-EPO-12345\",\n \"awbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"statusCode\": \"DLV\",\n \"deliveredAt\": \"2025-11-29T14:30:00Z\",\n \"receiverName\": \"Ali Ahmed\",\n \"receiverCNIC\": \"42101-1234567-1\",\n \"podReceived\": true,\n \"podUrl\": \"https://acs.psw.gov.pk/pod/DLV-EPO-12345.pdf\",\n \"notificationsSent\": {\n \"consignor\": true,\n \"consignee\": true,\n \"shipper\": true\n },\n \"shipmentStatus\": \"COMPLETED\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T14:35:00Z\",\n \"requestId\": \"req-123462\"\n }\n}\n\nError Response (422 Unprocessable Entity):
\n{\n \"success\": false,\n \"error\": {\n \"code\": \"POD_INCOMPLETE\",\n \"message\": \"Proof of Delivery incomplete - signature required\",\n \"details\": [\n {\n \"field\": \"proofOfDelivery.receiverSignature\",\n \"issue\": \"Signature is required for POD - cannot confirm delivery without signature\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T14:35:00Z\",\n \"requestId\": \"req-123462\"\n }\n}\n\nStatus Codes:
\n201: Delivery confirmed with POD
\n400: Invalid delivery data
\n401: Unauthorized
\n404: Shipment not found or not released
\n422: POD incomplete (missing signature, CNIC, etc.)
\n500: Internal server error
\nUse Case: List all EPO import shipments with filtering and pagination
\nPriority: P2
\nActors: EPO, GHA
\nQuery Parameters:
\nstatus: Filter by shipment statusdateFrom, dateTo: Date range filter (arrival date)flightNumber: Filter by flighthawbNumber: Search by HAWBpage: Page number (default 1)limit: Results per page (default 20, max 100)Success Response (200 OK):
\n{\n \"success\": true,\n \"data\": [\n {\n \"id\": \"shipment-001\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"OUT_FOR_DELIVERY\",\n \"currentStatus\": \"Released to EPO\",\n \"flightNumber\": \"EK-606\",\n \"arrivalDate\": \"2025-11-28\",\n \"pieces\": 5,\n \"weight\": 25.7,\n \"weightUnit\": \"kg\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"arrivedAt\": \"2025-11-28T20:15:00Z\",\n \"releasedAt\": \"2025-11-29T11:30:00Z\",\n \"estimatedDelivery\": \"2025-11-29T17:00:00Z\",\n \"consignee\": \"Ali Trading Company\",\n \"paymentStatus\": \"PAID\"\n }\n ],\n \"meta\": {\n \"pagination\": {\n \"currentPage\": 1,\n \"totalPages\": 3,\n \"pageSize\": 20,\n \"totalCount\": 56\n },\n \"timestamp\": \"2025-11-29T15:00:00Z\",\n \"requestId\": \"req-123463\"\n }\n}\nStatus Codes:
\nFilter by status: ARRIVED, EDO_ISSUED, EDO_PAID, HANDLING_INVOICE_RECEIVED, HANDLING_PAID, RELEASED, OUT_FOR_DELIVERY, DELIVERED
\n","type":"text/plain"},"key":"status","value":"OUT_FOR_DELIVERY"},{"description":{"content":"Start date for date range filter
\n","type":"text/plain"},"key":"dateFrom","value":"2025-11-01"},{"description":{"content":"End date for date range filter
\n","type":"text/plain"},"key":"dateTo","value":"2025-11-30"},{"description":{"content":"Filter by flight number
\n","type":"text/plain"},"key":"flightNumber","value":"EK-606"},{"description":{"content":"Filter by HAWB number
\n","type":"text/plain"},"key":"hawbNumber","value":"PKEPO00012345"},{"description":{"content":"Page number (default: 1)
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Results per page (default: 20, max: 100)
\n","type":"text/plain"},"key":"limit","value":"20"}],"variable":[]}},"response":[],"_postman_id":"af0f6a3f-ad59-4654-8db1-208d771616e7"},{"name":"View EPO Shipment Details","id":"75a5b1f2-7313-4f65-a4dd-7feae6456c3f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/epo/import/shipments/:id","description":"Use Case: View detailed information for specific EPO import shipment
\nPriority: P2
\nActors: EPO, GHA
\nPath Parameters:
\nid: Shipment IDSuccess Response (200 OK):
\n{\n \"success\": true,\n \"data\": {\n \"id\": \"shipment-001\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"mawbNumber\": \"176-12345678\",\n \"status\": \"OUT_FOR_DELIVERY\",\n \"flightNumber\": \"EK-606\",\n \"arrivalDate\": \"2025-11-28\",\n \"arrivalTime\": \"20:15:00Z\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 5,\n \"weight\": 25.7,\n \"weightUnit\": \"kg\",\n \"shipper\": {\n \"name\": \"Dubai Express Logistics\",\n \"address\": \"456 Airport Road, Dubai\",\n \"country\": \"AE\"\n },\n \"consignee\": {\n \"name\": \"Ali Trading Company\",\n \"address\": \"123 Main Street, Karachi\",\n \"city\": \"Karachi\",\n \"phone\": \"+92-300-1234567\"\n },\n \"customs\": {\n \"gdNumber\": \"GD-2025-123456\",\n \"gdStatus\": \"CLEARED\",\n \"clearedDate\": \"2025-11-29T08:30:00Z\"\n },\n \"deliveryOrder\": {\n \"doReference\": \"EDO-EPO-12345\",\n \"issuedAt\": \"2025-11-29T09:00:00Z\",\n \"paidAt\": \"2025-11-29T09:30:00Z\",\n \"doFee\": 1000,\n \"paymentStatus\": \"PAID\"\n },\n \"handlingCharges\": {\n \"invoiceReference\": \"INV-GHA-12345\",\n \"totalAmount\": 4720,\n \"paidAt\": \"2025-11-29T11:00:00Z\",\n \"paymentStatus\": \"PAID\"\n },\n \"release\": {\n \"releaseReference\": \"REL-EPO-12345\",\n \"releasedAt\": \"2025-11-29T11:30:00Z\",\n \"releasedTo\": \"EPO-Courier-456\",\n \"vehicleRegistration\": \"KHI-5678\"\n },\n \"statusHistory\": [\n {\n \"status\": \"ARR\",\n \"description\": \"Arrived\",\n \"timestamp\": \"2025-11-28T20:15:00Z\"\n },\n {\n \"status\": \"EDO_ISSUED\",\n \"description\": \"Delivery Order Issued\",\n \"timestamp\": \"2025-11-29T09:00:00Z\"\n },\n {\n \"status\": \"RELEASED\",\n \"description\": \"Released to EPO\",\n \"timestamp\": \"2025-11-29T11:30:00Z\"\n },\n {\n \"status\": \"OUT_FOR_DELIVERY\",\n \"description\": \"Out for Delivery\",\n \"timestamp\": \"2025-11-29T12:00:00Z\"\n }\n ],\n \"estimatedDelivery\": \"2025-11-29T17:00:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-29T15:00:00Z\",\n \"requestId\": \"req-123464\"\n }\n}\nStatus Codes:
\nShipment ID
\n","type":"text/plain"},"type":"any","value":"shipment-001","key":"id"}]}},"response":[],"_postman_id":"75a5b1f2-7313-4f65-a4dd-7feae6456c3f"}],"id":"a9e0ccb4-0e0f-401f-8adc-51a1cc65bf2b","_postman_id":"a9e0ccb4-0e0f-401f-8adc-51a1cc65bf2b","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"d891ce04-3d56-4cc6-8c24-49c9c716bf11","_postman_id":"d891ce04-3d56-4cc6-8c24-49c9c716bf11","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"8d1dbd5d-c051-42a4-b6cc-50b6eb98a2db","_postman_id":"8d1dbd5d-c051-42a4-b6cc-50b6eb98a2db","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"e-Flight module","item":[{"name":"PLACI Data Submission","item":[{"name":"Airline & EPO PLACI Submission","item":[{"name":"Submit PLACI Data","id":"109599b4-41a8-4958-8869-55ef3986951e","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"accept":true,"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi","description":"Requirement Reference: PF.I1AL.1, PF.I1EPO.1
\nUse Cases:
\nAirline sends PLACI data to Customs
\nSend PLACI data before flight departure 4 hours before flight departure
\nIntegration Point: ACS will enable Customs to receive PLACI data for risk analysis. ACS will enable Customs to reply to this request via ACS in digital format.
\nProcess Flow:
\nAirline System → ACS System → WeBOC
\nExpress Parcel Operator → ACS System → WeBOC
\nStandard: WCO PLACI Standard
\nAction:
\nPUSH
\nPOST
\nPriority: P1
\nPLACI Data Elements:
\nConsignor name and address
\nConsignee name and address
\nNumber of packages
\nTotal gross weight with unit qualifier
\nBrief cargo description
\nData filer identification (HAWB/MAWB)
\nAPI Parameters:
\nCondition Legend:
\nM (Mandatory): Field must be provided in all requests
\nO (Optional): Field is optional but recommended
\nC (Conditional): Required under specific conditions (see validation rule)
\nUnique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi/wco-xml","description":"Requirement Reference: PF.I1AL.1, PF.I1EPO.1
\nUse Cases:
\nAirline sends PLACI data to Customs
\nExpress Parcel Operator sends PLACI data before flight departure (4 hours before)
\nIntegration Point: Submit PLACI data in WCO PLACI XML standard format.
\nMessage Format: WCO PLACI XML Standard
\nProcess Flow:
\nAirline System → ACS System → WeBOC
\nExpress Parcel Operator → ACS System → WeBOC
\nAction:
\nPUSH
\nPOST
\nPriority: P1
\nAPI Parameters:
\nCondition Legend:
\nM (Mandatory): Field must be provided in all requests
\nO (Optional): Field is optional but recommended
\nC (Conditional): Required under specific conditions (see validation rule)
\nRequirement Reference: PF.I1CUS.2
\nUse Case: Starts risk analysis (PLACI)
\nIntegration Point: ACS will enable Customs to receive PLACI data in digital format from airlines. Initiates automated or manual risk analysis process.
\nProcess Flow: Airline System → ACS System → WeBOC
\nStandard: WCO PLACI Standard
\nAction:
\nPUSH
\nPOST
\nPriority: N/A
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","placi",":placiId"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"placi-2025112101","key":"placiId"}]}},"response":[{"id":"0c07c007-d0f8-4d26-b5f3-c8c34447c90d","name":"Success","originalRequest":{"method":"PATCH","header":[{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerUnique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/trade-lane/consignments","description":"Requirement Reference: PF.I1CGNR.3
\nUse Case: Consignor initiates digital trade lane submission
\nIntegration Point: ACS will enable Consignor to submit consignment documents to ACS via digital trade lane in digital format. This initiates the risk analysis and customs process directly from the origin.
\nAction: POST
\nPriority: N/A
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","trade-lane","consignments"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"8b252850-4a66-4498-acd2-40289a4173e2"}],"id":"b45ff1c5-66a2-4cf9-9631-bb081ebe3975","_postman_id":"b45ff1c5-66a2-4cf9-9631-bb081ebe3975","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Postal PLACI","item":[{"name":"Submit Postal CN Data","id":"5a3cf962-ad9a-4a30-b845-f1dcb95e3a89","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"accept":true,"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi/postal","description":"Requirement Reference: PF.I1P.4
\nUse Case: Postal Authority / Consigner sends CN data
\nIntegration Point: ACS will enable Postal authorities from the country of departure to send Postal shipment data in digital format. ACS will enable customs to perform PLACI analysis for risk assessment.
\nProcess Flow: Postal Authority System → ACS System → WeBOC
\nStandard: UPU Standards
\nAction: PUSH
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","placi","postal"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"5a3cf962-ad9a-4a30-b845-f1dcb95e3a89"},{"name":"Submit Postal CN Data (UPU XML)","id":"5be8e676-a176-49e9-9b14-fc48363b6adb","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi/postal/upu-xml","description":"Requirement Reference: PF.I1P.4
\nUse Case: Postal Authority / Consigner sends CN data
\nIntegration Point: Submit postal shipment data in UPU ITMATT XML format.
\nMessage Format: UPU ITMATT Standard
\nProcess Flow: Postal Authority System → ACS System → WeBOC
\nAction: PUSH
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","placi","postal","upu-xml"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"5be8e676-a176-49e9-9b14-fc48363b6adb"}],"id":"afb841cf-46db-4e46-b698-b61000e2517e","_postman_id":"afb841cf-46db-4e46-b698-b61000e2517e","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"2159cbfe-3220-4a8d-b5b7-5b58d351ffd8","_postman_id":"2159cbfe-3220-4a8d-b5b7-5b58d351ffd8","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Risk Analysis & Response","item":[{"name":"Risk Analysis Results","item":[{"name":"Submit Risk Analysis Result","id":"29098908-1b42-4376-9c83-89e456830811","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"accept":true,"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"CUSTOMS-WEBOC"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi/:placiId/risk-result","description":"Requirement Reference: PF.I2CUS.5, PF.I2AL.6, PF.I2P.7
\nUse Cases:
\nCustoms communicates risk analysis results
\nACS delivers risk analysis messages to Airline
\nACS delivers risk analysis & screening results to Postal Authority
\nIntegration Point: ACS will enable Customs to digitally communicate results of risk analysis to Express Parcel Operator and airline digitally. ACS will enable Customs to receive the additional information and results of additional screening digitally.
\nDecision Types:
\nload: Cleared for loading
\nadditional_information: Requires more info from consignor
\nadditional_screening: Requires physical/x-ray screening
\ndo_not_load: Prohibited from loading
\nProcess Flow: I2CUS → I2AL, I2CUS → I2P
\nWeBOC → ACS System → Airline System
\nWeBOC → ACS System → Postal Authority
\nStandard: WCO PLACI Standard
\nAction: PUSH
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","placi",":placiId","risk-result"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"placi-2025112101","key":"placiId"}]}},"response":[{"id":"60fe4592-e081-4e81-8589-4477eeb8bb05","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC","key":"X-Request-System","value":"CUSTOMS-WEBOC"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerUnique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi/:placiId/shipments/:awbNumber/request-info","description":"Requirement Reference: PF.I2AL.6, PF.I2P.7, PF.I2EPO.2
\nUse Case: Request for additional information / screening request
\nIntegration Point:
\nACS will enable Airline to reply to additional information and screening request via ACS in digital format. Airline forwards information request to consignor.
\nEPO forwards information request to consignor when Customs requires additional data.
\nProcess Flow:
\nAirline System → ACS System → Consignor
\nExpress Parcel Operator → ACS System → Consignor
\nAction: POST
\nPriority: N/A
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","placi",":placiId","shipments",":awbNumber","request-info"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"placi-2025112101","key":"placiId"},{"type":"any","value":"214-12345679","key":"awbNumber"}]}},"response":[],"_postman_id":"9931fcb5-4c4e-4a5f-99a6-bc1b4e10fd00"},{"name":"Submit Screening Results","id":"c0011826-501f-4f93-b4a4-f41f68e63b87","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"accept":true,"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi/:placiId/shipments/:awbNumber/screening-results","description":"Requirement Reference: PF.I2AL.6, PF.I2P.7, PF.I2EPO.2
\nUse Cases:
\nAirline replies to additional information / screening request
\nPostal Authority replies to additional info / screening or returns mail
\nEPO sends additional information / screening results
\nIntegration Points:
\nACS will enable Airline to submit screening results in response to additional screening request.
\nCS will enable Express Parcel Operator to send results of additional screening.
\nProcess Flow:
\nAirline System → ACS System → WeBOC
\nPostal Authority → ACS System → WeBOC
\nExpress Parcel Operator → ACS System → WeBOC
\nAction:
\nPOST
\nPUSH
\nPriority: P1
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","placi",":placiId","shipments",":awbNumber","screening-results"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"placi-2025112101","key":"placiId"},{"type":"any","value":"214-12345680","key":"awbNumber"}]}},"response":[],"_postman_id":"c0011826-501f-4f93-b4a4-f41f68e63b87"},{"name":"Process Return to Sender","id":"7b5346a5-2b89-48f1-a626-b6de5792bea8","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"accept":true,"content-type":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi/:placiId/postal-items/:itemId/return-to-sender","description":"Requirement Reference: PF.I2P.7, PF.I2EPO.2
\nUse Cases:
\nPostal Authority replies to additional info / screening or returns mail
\nEPO sends additional information / screening results
\nIntegration Point: Postal authority processes return of mail to sender for items marked 'do not load'.
\nProcess Flow: Postal Authority → ACS System → Consignor
\nAction: POST
\nPriority: N/A
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","placi",":placiId","postal-items",":itemId","return-to-sender"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"placi-2025112101","key":"placiId"},{"type":"any","value":"EMS123456789AE","key":"itemId"}]}},"response":[],"_postman_id":"7b5346a5-2b89-48f1-a626-b6de5792bea8"}],"id":"4f07a00d-916f-48ba-a73e-5cd83b44cebf","_postman_id":"4f07a00d-916f-48ba-a73e-5cd83b44cebf","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"EPO GD Processing","item":[{"name":"Submit GD for EPO Items","id":"9964d900-b054-459e-830d-bd987d85f90c","protocolProfileBehavior":{"disableBodyPruning":true,"disabledSystemHeaders":{"content-type":true,"accept":true}},"request":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"EPO-TCS-001"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/epo/goods-declarations","description":"Requirement Reference: PF.I3CUS.8, PF.I3EPO.3
\nUse Cases:
\nACS delivers GD data from Express Parcel Operator to Customs
\nEPO submits GD (Goods Declaration) for customs clearance
\nIntegration Point: ACS will enable Customs to digitally receive GD for all items prior to flight departure for customs clearance. ACS will enable Customs to digitally clear all items before flight departure and transmit the clearance data to Express Parcel Operator.
\nProcess Flow: Express Parcel Operator → ACS System → WeBOC
\nStandard: WCO Immediate Release Guidelines
\nAction:
\nPOST
\nPUSH
\nPriority: P1
\nAPI Parameters:
\nCondition Legend:
\nM (Mandatory): Field must be provided in all requests
\nO (Optional): Field is optional but recommended
\nC (Conditional): Required under specific conditions (see validation rule)
\nUnique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"EPO-TCS-001"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/xml"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/epo/goods-declarations/wco-xml","description":"Requirement Reference: PF.I3CUS.8, PF.I3EPO.3
\nUse Cases:
\nACS delivers GD data from Express Parcel Operator to Customs
\nEPO submits GD (Goods Declaration) for customs clearance
\nIntegration Point: Submit GD in WCO Immediate Release Guidelines XML format.
\nMessage Format: WCO Immediate Release Guidelines
\nProcess Flow: Express Parcel Operator → ACS System → WeBOC
\nAction:
\nPOST
\nPUSH
\nPriority: P1
\nAPI Parameters:
\nCondition Legend:
\nM (Mandatory): Field must be provided in all requests
\nO (Optional): Field is optional but recommended
\nC (Conditional): Required under specific conditions (see validation rule)
\nUnique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.
\n","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC
\n","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.
\n","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"MIME type of the request body
\n","key":"Content-Type","value":"application/json"},{"description":"Expected response MIME type
\n","key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/preflight/placi/:placiId/shipments/:awbNumber/additional-info","description":"Requirement Reference: PF.I3CGNR.9, PF.I2EPO.2
\nUse Cases:
\nProvide additional information or receive «do not load»
\nEPO sends additional information / screening results
\nIntegration Point: ACS will enable Consignor to digitally transmit additional information on the shipment against PLACI reply via ACS.
\nProcess Flow:
\nPostal Authority → ACS System → WeBOC
\nAirline System → ACS System → WeBOC
\nConsignor → ACS System → WeBOC
\nExpress Parcel Operator → ACS System → WeBOC
\nStandard: WCO Immediate Release Guidelines
\nAction: PUSH
\nPriority: P2
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","preflight","placi",":placiId","shipments",":awbNumber","additional-info"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"placi-2025112101","key":"placiId"},{"type":"any","value":"214-12345679","key":"awbNumber"}]}},"response":[{"id":"30ba9f8a-7a27-4780-8167-14d1bd04a1c4","name":"Success","originalRequest":{"method":"POST","header":[{"description":"Unique identifier for each API request (UUID v4 format). Used for request tracing, debugging, and idempotency.","key":"X-Request-ID","value":"550e8400-e29b-41d4-a716-446655440000"},{"description":"Identifier of the calling system. Format: {SYSTEM_TYPE}-{INSTANCE}. Examples: ACS-WEB, AIRLINE-PK-SYS, EPO-TCS-001, CUSTOMS-WEBOC","key":"X-Request-System","value":"AIRLINE-PK-SYS"},{"description":"Timestamp when the request was initiated by the client (ISO 8601 format). Must be within ±15 minutes of server time.","key":"X-Request-Timestamp","value":"2025-12-11T10:30:00.000Z"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E23ACA.1
\nUse Case: ACA receives final HAWB from Consignor
\nDescription: ACS enables ACA to digitally receive final HAWB from Consignor and send confirmation. Consignor submits completed HAWB to ACA after review and approval. ACA receives the final HAWB in the ACS system.
\nKey Activities:
\nConsignor submits final HAWB data to ACA via ACS
\nHAWB contains complete shipment details per IATA XFZB & FHL standards
\nAll mandatory fields validated (consignor, consignee, commodity, weights, charges)
\nCustoms declaration information included for export compliance
\nSecurity screening information captured
\nReferences to quote and booking maintained
\nDigital Information:
\nHAWB number (house air waybill identifier)
\nMAWB number (master air waybill reference)
\nConsignor details (name, address, contact, tax ID)
\nConsignee details (name, address, contact, tax ID)
\nCommodity description and HS code
\nWeight, dimensions, piece count
\nHandling instructions and special service requests
\nCharges declaration (prepaid/collect)
\nCustoms information (GD reference, export license)
\nFlight details (airline, flight number, date)
\nDistribution preferences
\nMessage Formats: API (JSON), XFWB, FWB, XFZB, FHL
\nProcess Flow:
\nConsignor → ACA → GHA
\nConsignor → ACA → Customs Broker
\nConsignor → ACA → Airline System
\nConsignor → ACA → Customs System
\nActors: Consignor (E23CGNR), ACA (E23ACA)
\nAuthentication: OAuth 2.0 Bearer Token - Required for all API calls
\nAction: PUSH
\nPriority: P1 (Critical Integration)
\nAPI Parameters:
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawb-submissions"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"7231c8f0-bf24-4e98-8bf7-39398caec751","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"58a3a799-8dad-439f-9aab-57716b5b5d9a"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E23ACA.1
\nUse Case: List HAWB submissions with filtering and pagination
\nDescription: ACA lists all HAWB submissions with filters for status, date range, origin/destination, and HAWB/MAWB numbers.
\nQuery Parameters:
\nstatus: Filter by submission status
\nacaAccountId: Filter by ACA account
\nhawbNumber: Filter by HAWB number
\nmawbNumber: Filter by MAWB number
\norigin: Filter by origin airport code
\ndestination: Filter by destination airport code
\ndateFrom/dateTo: Filter by date range
\npage: Page number (default: 1)
\nlimit: Items per page (default: 20, max: 100)
\nsort: Sort by field (createdAt, updatedAt, hawbNumber)
\nResponse Includes:
\nPaginated list of HAWB submissions
\nSummary information for each submission
\nPagination metadata
\nProcess Flow: E23ACA → List Submissions
\nActors: ACA (E23ACA)
\nAuthentication: OAuth 2.0 Bearer Token
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawb-submissions"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"description":{"content":"Filter by status (submitted, confirmed, distributed)
\n","type":"text/plain"},"key":"status","value":"submitted"},{"description":{"content":"Filter by ACA account ID
\n","type":"text/plain"},"key":"acaAccountId","value":"aca-khi-001"},{"description":{"content":"Filter by HAWB number
\n","type":"text/plain"},"key":"hawbNumber","value":"string"},{"description":{"content":"Filter by MAWB number
\n","type":"text/plain"},"key":"mawbNumber","value":"string"},{"description":{"content":"Filter by origin airport code
\n","type":"text/plain"},"key":"origin","value":"string"},{"description":{"content":"Filter by destination airport code
\n","type":"text/plain"},"key":"destination","value":"string"},{"description":{"content":"Filter by creation date (from)
\n","type":"text/plain"},"key":"dateFrom","value":"string"},{"description":{"content":"Filter by creation date (to)
\n","type":"text/plain"},"key":"dateTo","value":"string"},{"description":{"content":"Page number
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (max 100)
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort by field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-createdAt"}],"variable":[]}},"response":[{"id":"22aff933-66b4-47cf-a6b9-46368363fe59","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"4e548870-e5d4-4679-92f7-3969bbdace73"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E23ACA.1
\nUse Case: ACA confirms receipt and accuracy of HAWB from Consignor
\nDescription: ACS enables ACA to digitally receive final HAWB from Consignor and send confirmation. After receiving the HAWB, ACA reviews and confirms the data is accurate and complete before distributing to stakeholders.
\nKey Activities:
\nACA reviews HAWB submission from Consignor
\nValidates all mandatory fields and data accuracy
\nChecks security screening completion
\nConfirms charges calculation
\nMarks HAWB as confirmed and ready for distribution
\nRequest Body:
\nconfirmationType: accept or request_correction
\nconfirmedBy: ACA user ID who confirmed
\nconfirmedByName: Name of confirming user
\nnotes: Optional notes about confirmation
\nvalidationChecks: Checklist of validation items
\nBusiness Rules:
\nOnly ACA users can confirm HAWB submissions
\nHAWB must be in 'submitted' status to be confirmed
\nConfirmation triggers automatic distribution to stakeholders
\nOnce confirmed, HAWB cannot be edited (only corrected through amendment process)
\nProcess Flow: E23CGNR → E23ACA → Confirm → E23ACA
\nActors: ACA (E23ACA)
\nAuthentication: OAuth 2.0 Bearer Token
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawb-submissions",":id","confirm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"HAWB submission ID
\n","type":"text/plain"},"type":"any","value":"hawb-sub-KHI12345678","key":"id"}]}},"response":[{"id":"8c8bcf38-c767-4cdc-933d-57586781201a","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"6cf0606f-584c-4f8c-bf7f-3a0930a9c5b1"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E23ACA.1
\nUse Case: ACA sends final HAWB + MAWB to stakeholders
\nDescription: ACS enables ACA to digitally send final HAWB + MAWB to GHA, Airlines, Customs Broker, and WeBOC. This endpoint pushes HAWB and MAWB data to Ground Handling Agent (GHA) system.
\nKey Activities:
\nACS acts as middleware hub - NO direct ACA-to-GHA connection
\nACS receives push request from ACA
\nACS transforms data to GHA-preferred format (XFZB, FHL, or JSON)
\nACS pushes to GHA endpoint
\nGHA receives HAWB+MAWB for cargo handling operations
\nConfirmation sent back to ACA via ACS
\nRequest Body:
\ntargetGHAAccountId: GHA account ID in ACS
\ntargetGHAName: GHA organization name
\ntargetGHAEndpoint: GHA API endpoint (optional - ACS has registry)
\nmessageFormat: XFZB (XML), FHL (IMP), or JSON
\npriority: normal or urgent
\nincludeMAWBData: Include MAWB data with HAWB
\nnotificationEmail: Email for delivery notification
\nBusiness Rules:
\nHAWB must be confirmed before pushing to GHA
\nACS validates GHA account is active and authorized
\nMessage format transformed by ACS if needed
\nRetry mechanism for failed deliveries (3 attempts)
\nDelivery status tracked and logged
\nMessage Formats: API (JSON), XFZB (IATA Cargo-XML), FHL (IATA Cargo-IMP)
\nProcess Flow: E23ACA → ACS → E24GHA
\nActors: ACA (E23ACA), GHA (E24GHA), ACS (Middleware)
\nAuthentication: OAuth 2.0 Bearer Token
\nPriority: P1 (Critical Integration)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawb-submissions",":id","push","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"HAWB submission ID
\n","type":"text/plain"},"type":"any","value":"hawb-sub-KHI12345678","key":"id"}]}},"response":[{"id":"e178c24d-ba9f-4ce0-a16b-b4ba048630de","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"d6bc34bb-1c3a-4e7a-9aed-427846e9eff7"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E23ACA.1
\nUse Case: ACA sends final HAWB + MAWB to stakeholders
\nDescription: ACS enables ACA to digitally send final HAWB + MAWB to Airlines. This endpoint pushes HAWB and MAWB data to Airline system for flight manifest preparation and PLACI submission.
\nKey Activities:
\nACS acts as middleware hub
\nACS receives push request from ACA
\nACS transforms data to IATA Cargo-XML format (XFWB+XFZB)
\nACS pushes to Airline endpoint
\nAirline receives HAWB+MAWB for:
\nFlight manifest (FFM) preparation
\nPLACI (Pre-Loading Advance Cargo Info) submission to destination customs
\nCargo acceptance and loading
\nConfirmation sent back to ACA via ACS
\nRequest Body:
\ntargetAirlineCode: 2-letter IATA airline code (e.g., EK)
\ntargetAirlinePrefix: 3-digit airline prefix (e.g., 176)
\ntargetAirlineName: Airline name
\ntargetAirlineEndpoint: Airline API endpoint
\nmessageFormat: XFWB_XFZB (XML), FWB_FHL (IMP), or JSON
\npriority: normal or urgent
\nincludeMAWBData: Include MAWB data
\nincludeFlightDetails: Include flight number and date
\nflightNumber: Flight number for this shipment
\nflightDate: Scheduled flight date
\nnotificationEmail: Email for delivery notification
\nBusiness Rules:
\nHAWB must be confirmed before pushing to Airline
\nFlight details must be present
\nSecurity screening must be completed
\nMAWB must be associated with HAWB
\nAirline must be authorized for route
\nMessage Formats: XFWB+XFZB (IATA Cargo-XML), FWB+FHL (IATA Cargo-IMP), JSON
\nProcess Flow: E23ACA → ACS → E24AL
\nActors: ACA (E23ACA), Airline (E24AL), ACS (Middleware)
\nAuthentication: OAuth 2.0 Bearer Token
\nPriority: P1 (Critical Integration)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawb-submissions",":id","push","airline"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"HAWB submission ID
\n","type":"text/plain"},"type":"any","value":"hawb-sub-KHI12345678","key":"id"}]}},"response":[{"id":"f2c01383-4147-4380-8fb1-f0cce551143e","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"38e2015c-7bfd-461a-b3d6-31a2575d5a10"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E23ACA.1
\nUse Case: ACA sends final HAWB + MAWB to stakeholders
\nDescription: ACS enables ACA to digitally send final HAWB + MAWB to WeBOC (Web-Based One Customs). This endpoint pushes HAWB and MAWB data to Pakistan Customs WeBOC system for export clearance and risk assessment.
\nKey Activities:
\nACS acts as middleware hub
\nACS receives push request from ACA
\nACS transforms data to WeBOC-compatible format
\nACS pushes to WeBOC endpoint
\nWeBOC receives HAWB+MAWB for:
\nExport Goods Declaration (GD) validation
\nRisk assessment and profiling
\nExport clearance processing
\nDuty and tax assessment (if applicable)
\nExport statistics
\nConfirmation sent back to ACA via ACS
\nRequest Body:
\ntargetSystemId: WeBOC system identifier
\ntargetSystemName: System name
\ntargetSystemEndpoint: WeBOC API endpoint
\nmessageFormat: JSON (WeBOC standard format)
\npriority: high, normal, or low
\nincludeMAWBData: Include MAWB data
\nincludeCustomsDocuments: Include supporting customs documents
\nincludeGDReference: Include GD reference number
\ngdReferenceNumber: Export GD reference from WeBOC
\ncustomsBrokerAccountId: CB who prepared the GD
\nnotificationEmail: Email for delivery notification
\nBusiness Rules:
\nHAWB must be confirmed before pushing to WeBOC
\nGD reference number must be present for export clearance
\nCustoms information must be complete and accurate
\nExport license required for restricted/controlled goods
\nAll charges and duties must be calculated
\nSecurity screening must be completed
\nWeBOC Integration:
\nReal-time data transmission to Pakistan Customs
\nEliminates manual entry by customs officers
\nEnables automated risk assessment
\nProvides export clearance status updates
\nCompliance with Pakistan Customs regulations
\nMessage Formats: JSON (WeBOC Standard)
\nProcess Flow: E23ACA → ACS → E24CUS (WeBOC)
\nActors: ACA (E23ACA), Customs (E24CUS), ACS (Middleware)
\nAuthentication: OAuth 2.0 Bearer Token
\nPriority: P1 (Critical Integration - Regulatory Compliance)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawb-submissions",":id","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"HAWB submission ID
\n","type":"text/plain"},"type":"any","value":"hawb-sub-KHI12345678","key":"id"}]}},"response":[{"id":"7ba28170-0d4b-4bff-87d1-737cc400487e","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"aff97449-0fd1-4307-967d-bece58735bd6"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E23ACA.1
\nUse Case: ACA sends final HAWB + MAWB to stakeholders
\nDescription: ACS enables ACA to digitally send final HAWB + MAWB to Customs Broker. This endpoint pushes HAWB and MAWB data to Customs Broker system for customs declaration preparation.
\nKey Activities:
\nACS acts as middleware hub
\nACS receives push request from ACA
\nACS transforms data to CB-preferred format
\nACS pushes to Customs Broker endpoint
\nCB receives HAWB+MAWB for customs declaration (GD) preparation
\nCB uses data to prepare export declaration
\nConfirmation sent back to ACA via ACS
\nRequest Body:
\ntargetCBAccountId: Customs Broker account ID
\ntargetCBName: CB organization name
\ntargetCBEndpoint: CB API endpoint
\nmessageFormat: JSON, XFZB, or FHL
\npriority: normal or urgent
\nincludeMAWBData: Include MAWB data
\nincludeCustomsDocuments: Include customs-related documents
\nnotificationEmail: Email for delivery notification
\nBusiness Rules:
\nHAWB must be confirmed before pushing to CB
\nCustoms information must be complete
\nGD reference number should be present
\nExport license information required for restricted goods
\nMessage Formats: API (JSON), XFZB (IATA Cargo-XML), FHL (IATA Cargo-IMP)
\nProcess Flow: E23ACA → ACS → E24CB
\nActors: ACA (E23ACA), Customs Broker (E24CB), ACS (Middleware)
\nAuthentication: OAuth 2.0 Bearer Token
\nPriority: P1 (Critical Integration)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["hawb-submissions",":id","push","customs-broker"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"HAWB submission ID
\n","type":"text/plain"},"type":"any","value":"hawb-sub-KHI12345678","key":"id"}]}},"response":[{"id":"4ddf6888-d235-45c7-aa24-fe7681d07ec0","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"6b85872e-431d-4728-a251-64a5efc8576a"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerGlobal API reference:
\n--
\nRequirement Reference: CM.E24AL.2
\nUse Case: Airline receives MAWB + HAWB as XFWB + XFZB from ACA & Express Parcel Operator
\nDescription: Airline receives MAWB + HAWB in JSON format. ACS enables Airlines to digitally receive final HAWB + MAWB from ACA and EPO for cargo acceptance, flight manifest preparation, and PLACI submission to destination customs.
\nKey Activities:
\nAirline receives MAWB+HAWB data from ACA or EPO via ACS
\nData received in JSON format (standard API)
\nAirline validates cargo acceptance criteria
\nPrepares data for flight manifest (FFM)
\nExtracts PLACI data for destination customs submission
\nConfirms receipt back to ACA/EPO via ACS
\nDigital Information:
\nSource (ACA or EPO)
\nMAWB details (number, origin, destination, flight)
\nHAWB details (consignor, consignee, commodity)
\nTotal pieces and weight
\nScreening information (security compliance)
\nPLACI data elements (per WCO PLACI standard)
\nPLACI Data Elements (WCO Standard):
\nConsignor name and address
\nConsignee name and address
\nNumber of packages
\nTotal gross weight with unit
\nBrief cargo description
\nData filer identification (IATA code of ACA/EPO)
\nBusiness Rules:
\nMAWB must be valid for airline prefix
\nFlight must exist in airline schedule
\nSecurity screening must be completed
\nAll PLACI mandatory fields must be present
\nWeight must match consolidation totals
\nMessage Formats: API (JSON), XFWB+XFZB (IATA Cargo-XML), FWB+FHL (IATA Cargo-IMP)
\nProcess Flow: E23ACA → E24AL or EPOACA → E24AL
\nActors: Airline (E24AL), ACA (E23ACA), EPO
\nAuthentication: OAuth 2.0 Bearer Token
\nPriority: P1 (Critical Integration)
\nStandards: IATA Cargo-XML, IATA Cargo-IMP, WCO PLACI
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["mawb-hawb-receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"7528aaa4-456d-4404-a36a-149dfa8f0bb6","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"bb6f3469-9345-41cc-8f3f-c73c74230c44"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E24AL.2
\nUse Case: Airline receives MAWB + HAWB as XFWB + XFZB from ACA & Express Parcel Operator
\nDescription: Airline receives MAWB + HAWB in IATA Cargo-XML format (XFWB + XFZB). This is the preferred format for airline-to-airline and ACA-to-airline data exchange.
\nKey Activities:
\nAirline receives combined XFWB+XFZB XML message
\nACS parses and validates XML against IATA Cargo-XML v5.00 schema
\nExtracts MAWB data from XFWB message
\nExtracts HAWB data from XFZB message
\nCross-validates MAWB and HAWB consistency
\nStores in ACS database
\nConfirms receipt to sender
\nMessage Format: IATA Cargo-XML v5.00
\nXFWB: Master Waybill (Type Code 740)
\nXFZB: House Waybill (Type Code 703)
\nXML Structure:
\nMessageHeaderDocument: Metadata (sender, recipient, timestamp)
\nBusinessHeaderDocument: AWB/HAWB number, issue date, locations
\nMasterConsignment: Cargo details, routing, parties
\nIncludedHouseConsignment: HAWB-specific details
\nPLACI Integration:
\nApplicableCrossBorderRegulatoryProcedure: TypeCode=PLACI
\nIndicates PLACI submission requirement
\nPLACI data extracted for destination customs
\nProcess Flow: E23ACA → ACS → E24AL
\nActors: Airline (E24AL), ACA (E23ACA), EPO
\nAuthentication: OAuth 2.0 Bearer Token
\nPriority: P1 (Critical Integration)
\nStandards: IATA Cargo-XML v5.00, WCO PLACI
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["mawb-hawb-receipts","xfwb-xfzb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"42c56d55-8bd7-48cf-9900-20277d073376","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"499c8417-ea3f-445a-96ce-f71e0b0349e5"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E24AL.2
\nUse Case: Airline receives MAWB + HAWB as XFWB + XFZB from ACA & Express Parcel Operator
\nDescription: Airline receives MAWB + HAWB in IATA Cargo-IMP format (FWB + FHL). This is the legacy format still used by some airlines and systems.
\nKey Activities:
\nAirline receives combined FWB+FHL IMP message
\nACS parses IMP text format
\nExtracts MAWB data from FWB message
\nExtracts HAWB data from FHL message
\nConverts to structured data format
\nCross-validates MAWB and HAWB consistency
\nStores in ACS database
\nConfirms receipt to sender
\nMessage Format: IATA Cargo-IMP (Interchange Message Procedures)
\nFWB: Freight Waybill (Master AWB)
\nFHL: Freight House Manifest (House AWB)
\nIMP Structure:
\nLine-based text format
\nField codes (SND, RCF, FLT, ORI, DST, etc.)
\nFixed format with delimiters
\nBackward compatible with legacy systems
\nFWB Elements:
\nAWB number: 176-12345678
\nRoute: KHIDXB (Karachi to Dubai)
\nWeight: T10K500 (Total 10 pieces, 500 kg)
\nAirline: EKEK (Emirates)
\nFlight: 602/25NOV
\nFHL Elements:
\nHAWB number: KHI12345678
\nConsignor/Consignee details
\nNature of goods
\nHS code
\nPLACI indicator
\nProcess Flow: E23ACA → ACS → E24AL
\nActors: Airline (E24AL), ACA (E23ACA), EPO
\nAuthentication: OAuth 2.0 Bearer Token
\nPriority: P1 (Critical Integration)
\nStandards: IATA Cargo-IMP, WCO PLACI
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["mawb-hawb-receipts","fwb-fhl"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"3f269d06-6a43-48e7-8fe6-9088f84c08a6","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"e05ced4e-d20b-42c0-93b1-7b55b4d06e88"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E24AL.2
\nUse Case: List all MAWB+HAWB receipts with filtering and pagination
\nDescription: Airline lists all received MAWB+HAWB combinations with filters for status, date range, flight details, and message format.
\nQuery Parameters:
\nairlineCode: Filter by airline code (2-letter IATA)
\nstatus: Filter by receipt status
\nmawbNumber: Filter by MAWB number
\nhawbNumber: Filter by HAWB number
\nflightNumber: Filter by flight number
\nflightDate: Filter by flight date
\nsource: Filter by source (ACA or EPO)
\nmessageFormat: Filter by message format
\ndateFrom/dateTo: Filter by received date range
\npage: Page number (default: 1)
\nlimit: Items per page (default: 20, max: 100)
\nsort: Sort by field (receivedAt, flightDate, mawbNumber)
\nResponse Includes:
\nPaginated list of MAWB+HAWB receipts
\nSummary information for each receipt
\nPLACI and FFM preparation status
\nPagination metadata
\nProcess Flow: E24AL → List Receipts
\nActors: Airline (E24AL)
\nAuthentication: OAuth 2.0 Bearer Token
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["mawb-hawb-receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"description":{"content":"Filter by airline code
\n","type":"text/plain"},"key":"airlineCode","value":"EK"},{"description":{"content":"Filter by receipt status (received, processed, rejected)
\n","type":"text/plain"},"key":"status","value":"received"},{"description":{"content":"Filter by MAWB number
\n","type":"text/plain"},"key":"mawbNumber","value":"string"},{"description":{"content":"Filter by HAWB number
\n","type":"text/plain"},"key":"hawbNumber","value":"string"},{"description":{"content":"Filter by flight number
\n","type":"text/plain"},"key":"flightNumber","value":"string"},{"description":{"content":"Filter by flight date (YYYY-MM-DD)
\n","type":"text/plain"},"key":"flightDate","value":"string"},{"description":{"content":"Filter by source (ACA or EPO)
\n","type":"text/plain"},"key":"source","value":"string"},{"description":{"content":"Filter by message format (JSON, XFWB_XFZB, FWB_FHL)
\n","type":"text/plain"},"key":"messageFormat","value":"string"},{"description":{"content":"Filter by received date (from)
\n","type":"text/plain"},"key":"dateFrom","value":"string"},{"description":{"content":"Filter by received date (to)
\n","type":"text/plain"},"key":"dateTo","value":"string"},{"description":{"content":"Page number
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (max 100)
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort by field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-receivedAt"}],"variable":[]}},"response":[{"id":"909fa4b0-489f-4a8b-8ed1-68cabad86841","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"17985d2e-99f3-4d16-b70a-22f863cf3966"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E25AL.3
\nUse Case: Airlines send PLACI data for advance risk assessment
\nDescription: Airlines submit PLACI data to ACS for forwarding to destination country customs
\nProcess Flow: E24AL → E25AL → E25DCC
\nActors: Airline (AL), Destination Country Customs (DCC)
\nBusiness Context:
\nThis endpoint enables airlines to submit Pre-Loading Advance Cargo Information (PLACI) to destination country customs authorities for risk assessment BEFORE cargo is loaded onto aircraft. PLACI is mandated by the World Customs Organization (WCO) to enable:
\nRisk-based screening before departure
\nPrevention of prohibited/dangerous goods from being loaded
\nFaster clearance upon arrival at destination
\nEnhanced security for international air cargo
\nThe airline submits PLACI data in JSON format containing mandatory WCO PLACI elements including consignor details, consignee details, cargo description, and data filer identification.
\nWCO PLACI Mandatory Fields:
\nConsignor name and address
\nConsignee name and address
\nNumber of packages
\nTotal gross weight with unit qualifier (kg, lb)
\nBrief cargo description
\nData filer identification from HAWB/MAWB
\nAuthentication: OAuth 2.0 Bearer Token (Airline role required)
\nValidation Rules:
\nMAWB format: {airline-prefix}-{8-digit-serial}
Flight number format: {airline-code}-{flight-number}
IATA airport codes: 3-letter codes (KHI, LHR, DXB)
\nISO country codes: 2-letter codes (PK, GB, AE)
\nWeight unit: kg or lb
\nVolume unit: m3 or ft3
\nPackage type: IATA package codes (CTN, PLT, BAG, etc.)
\nAll mandatory WCO PLACI fields must be present
\nResponse: Returns PLACI submission ID and status for tracking.
\nNext Steps:
\nACS forwards PLACI to destination customs (CM.E25AL.3-2)
\nDestination customs reviews and responds (CM.E25DCC.4)
\nAirline receives decision (Load/Additional Info/Screening/DNL)
\nRequirement Reference: CM.E25AL.3
\nUse Case: Airlines send PLACI data for advance risk assessment
\nDescription: Airlines submit PLACI data to ACS in WCO PLACI XML format
\nProcess Flow: E24AL → E25AL → E25DCC
\nActors: Airline (AL), Destination Country Customs (DCC)
\nBusiness Context:
\nThis endpoint accepts PLACI submissions in WCO (World Customs Organization) PLACI XML standard format. The XML format is preferred by many customs authorities worldwide and ensures compliance with international PLACI standards.
\nThe WCO PLACI XML format includes:
\nHeader with message identification and routing
\nShipment details with MAWB/HAWB references
\nFlight information
\nConsignor and consignee details
\nCargo description and measurements
\nData filer identification
\nWCO PLACI XML Standard: Follows WCO Data Model for customs data exchange, specifically the PLACI message structure defined by the World Customs Organization.
\nAuthentication: OAuth 2.0 Bearer Token (Airline role required)
\nXML Validation:
\nMust conform to WCO PLACI XML schema
\nAll mandatory elements must be present
\nDate/time in ISO 8601 format
\nCountry codes: ISO 3166-1 alpha-2
\nAirport codes: IATA 3-letter codes
\nWeight unit: KGM (kilograms) or LBR (pounds)
\nVolume unit: MTQ (cubic meters) or FTQ (cubic feet)
\nResponse: Returns PLACI submission ID and processing status.
\nNext Steps:
\nACS validates XML against WCO PLACI schema
\nACS forwards to destination customs via WeBOC
\nDestination customs reviews and responds
\nAirline receives decision via response endpoints
\nRequirement Reference: CM.E25AL.3
\nUse Case: List all PLACI submissions with filtering and pagination
\nDescription: Query PLACI submissions by various criteria
\nProcess Flow: E25AL (List)
\nActors: Airline (AL)
\nBusiness Context:
\nRetrieve a paginated list of PLACI submissions with flexible filtering options. Useful for:
\nMonitoring all PLACI submissions for a specific flight
\nTracking submissions by destination country
\nFinding submissions awaiting decisions
\nDaily reconciliation of PLACI submissions
\nReporting and compliance audits
\nQuery Parameters:
\nstatus: Filter by submission status (submitted, validated, forwarded, decision_received, etc.)
flightDate: Filter by flight departure date (YYYY-MM-DD)
flightNumber: Filter by flight number (e.g., PK-758)
destinationCountry: Filter by destination country ISO code
destinationAirport: Filter by destination airport IATA code
mawbNumber: Filter by MAWB number
hawbNumber: Filter by HAWB number
submittedAfter: Filter submissions after date/time (ISO 8601)
submittedBefore: Filter submissions before date/time (ISO 8601)
page: Page number (default: 1)
limit: Items per page (default: 20, max: 100)
sort: Sort field (prefix with - for descending, e.g., -submittedAt)
Sorting Options:
\nsubmittedAt: Submission timestamp
flightDate: Flight departure date
status: Submission status
destinationCountry: Destination country
Authentication: OAuth 2.0 Bearer Token (Airline role required)
\nAuthorization: Airlines can only list their own PLACI submissions.
\nPagination: Standard pagination with total count in metadata.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","placi-submissions"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"description":{"content":"Filter by submission status
\n","type":"text/plain"},"key":"status","value":"decision_received"},{"description":{"content":"Filter by flight date (YYYY-MM-DD)
\n","type":"text/plain"},"key":"flightDate","value":"2025-11-25"},{"description":{"content":"Filter by destination country (ISO 2-letter code)
\n","type":"text/plain"},"key":"destinationCountry","value":"GB"},{"description":{"content":"Filter by MAWB number
\n","type":"text/plain"},"key":"mawbNumber","value":"string"},{"description":{"content":"Page number (default: 1)
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (default: 20, max: 100)
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-submittedAt"}],"variable":[]}},"response":[{"id":"0bba4a05-3085-4477-b9c8-7d3792d68e6f","name":"Success - PLACI List","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E25AL.3
\nUse Case: Push PLACI data to destination country customs
\nDescription: ACS forwards PLACI to destination customs via WeBOC
\nProcess Flow: E25AL → E25DCC
\nActors: ACS System, Destination Country Customs (DCC)
\nBusiness Context:
\nThis endpoint forwards a validated PLACI submission to the destination country customs authority for risk assessment. The forwarding is typically automatic after validation, but can also be triggered manually by system administrators.
\nACS acts as a middleware hub, routing PLACI data through WeBOC to the appropriate destination country customs authority based on the destination country code.
\nForwarding Methods:
\nweboc: Route through Pakistan WeBOC to destination customs (default)
direct: Direct connection to destination customs API (if available)
manual: Manual processing required
Priority Levels:
\nurgent: High-priority shipment, expedited processing
normal: Standard processing (default)
low: Low-priority, batch processing acceptable
Authentication: OAuth 2.0 Bearer Token (System Admin or Airline role)
\nValidation:
\nPLACI submission must be in validated status
Cannot forward already-forwarded submissions (idempotent)
\nDestination customs authority must be configured in system
\nWeBOC connection must be active
\nProcess:
\nACS retrieves PLACI submission
\nTransforms to destination customs format (if needed)
\nSends via WeBOC integration
\nUpdates submission status to forwarded
Records forwarding timestamp
\nSends notification email (if provided)
\nResponse: Confirmation of forwarding with tracking information.
\nNext Steps:
\nDestination customs receives PLACI
\nDestination customs performs risk analysis
\nDestination customs sends decision (CM.E25DCC.4)
\nACS receives and distributes decision
\nPLACI submission ID
\n","type":"text/plain"},"type":"any","value":"placi-exp-45a7b9c1","key":"id"}]}},"response":[{"id":"e9748742-4fa2-4760-a17e-6040e6dd7922","name":"Success - PLACI Forwarded","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"b24ea5da-84c2-428e-8601-3ce2abacc120"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E25AL.3
\nUse Case: Check real-time PLACI processing status
\nDescription: Monitor PLACI submission through processing pipeline
\nProcess Flow: E25AL (Status Check)
\nActors: Airline (AL)
\nBusiness Context:
\nProvides a lightweight status check endpoint for real-time monitoring of PLACI submission progress. Useful for:
\nPolling for decision updates
\nDashboard status displays
\nAutomated monitoring systems
\nIntegration with airline operational systems
\nStatus Flow:
\ndraft → submitted → validated → forwarded → under_review → decision_received → completed\n ↓\n failed\n\nStatus Definitions:
\ndraft: Created but not submitted
submitted: Received by ACS, awaiting validation
validated: Passed validation checks
forwarded: Sent to destination customs
under_review: Being reviewed by destination customs
decision_received: Decision received from customs
completed: All processing complete
failed: Validation or processing failure
Response Information:
\nCurrent status
\nStatus timestamps
\nDecision type (if received)
\nNext expected action
\nEstimated decision time
\nCustoms authority contact (if needed)
\nAuthentication: OAuth 2.0 Bearer Token (Airline role required)
\nAuthorization: Airlines can only check status of their own submissions.
\nUse Cases:
\nPre-flight status verification
\nAutomated alerts when decision received
\nOperations dashboard integration
\nMobile app status display
\nPLACI submission ID
\n","type":"text/plain"},"type":"any","value":"placi-exp-45a7b9c1","key":"id"}]}},"response":[{"id":"3563ed2d-2ef2-4120-bd20-64865fb34e9e","name":"Success - Status with Decision","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E25DCC.4, CM.E25AL.3-3
\nUse Case: Response from destination country to the PLACI request
\nDescription: Destination customs communicates risk analysis decision back to ACS
\nProcess Flow: E25DCC → E25AL
\nActors: Destination Country Customs (DCC), ACS System
\nBusiness Context:
\nThis endpoint receives PLACI risk analysis decisions from destination country customs authorities. The decision is one of four types mandated by WCO PLACI standards:
\n1. LOAD - Cleared for loading
\nNo issues identified
\nCargo can proceed as planned
\nNo further action required
\n2. ADDITIONAL_INFORMATION - Request for more details
\nCustoms requires clarification from consignor
\nSpecific information requested
\nDeadline for response provided
\nCargo on hold until info received
\n3. ADDITIONAL_SCREENING - Physical inspection required
\nX-ray screening mandatory
\nExplosive detection required
\nPhysical examination needed
\nResults must be submitted before loading
\n4. DO_NOT_LOAD - Prohibited from loading
\nSecurity risk identified
\nProhibited goods detected
\nRegulatory violation found
\nCargo must be returned to sender
\nCannot proceed with shipment
\nDecision Data:
\nDecision type (one of four)
\nReason code and description
\nCustoms authority identification
\nCustoms reference number
\nValidity period for decision
\nAdditional instructions (if applicable)
\nContact information for follow-up
\nNotification Distribution:
Based on decision type, ACS automatically notifies:
LOAD: Airline only
\nADDITIONAL_INFORMATION: Airline + ACA + Consignor
\nADDITIONAL_SCREENING: Airline + GHA
\nDO_NOT_LOAD: Airline + GHA + ACA + Consignor
\nAuthentication: OAuth 2.0 Bearer Token (WeBOC/System role required)
\nValidation:
\nPLACI submission ID must exist and be in forwarded status
Decision type must be one of four valid types
\nAdditional screening details required if decision is additional_screening
Additional information details required if decision is additional_information
Do-not-load reason required if decision is do_not_load
Response: Confirmation of receipt with distribution tracking.
\nNext Steps:
\nACS creates PLACI response record
\nACS updates original submission status
\nACS pushes decision to airline (CM.E25DCC.4-1)
\nACS pushes to GHA if screening required
\nACS notifies ACA if do-not-load
\nRequirement Reference: CM.E25DCC.4
\nUse Case: List PLACI responses with filtering options
\nDescription: Query PLACI responses by decision type and other criteria
\nProcess Flow: E25DCC (List)
\nActors: Airline (AL), GHA, ACA
\nBusiness Context:
\nRetrieve a paginated list of PLACI risk analysis responses. Useful for:
\nMonitoring all screening requests for a flight
\nIdentifying do-not-load decisions
\nGHA workload planning (screening queue)
\nOperations dashboard displays
\nCompliance reporting
\nQuery Parameters:
\ndecision: Filter by decision type (load, additional_information, additional_screening, do_not_load)
flightDate: Filter by flight date (YYYY-MM-DD)
flightNumber: Filter by flight number
customsAuthority: Filter by customs authority code
mawbNumber: Filter by MAWB number
receivedAfter: Filter responses received after date/time
receivedBefore: Filter responses received before date/time
screeningPending: Filter responses awaiting screening results (true/false)
page: Page number (default: 1)
limit: Items per page (default: 20, max: 100)
sort: Sort field (prefix with - for descending)
Decision Type Filters:
\nload: Cleared for loading
additional_information: Awaiting additional info from consignor
additional_screening: Screening required by GHA
do_not_load: Prohibited from loading
Sorting Options:
\nreceivedAt: Response receipt timestamp
decisionDate: Customs decision date
flightDate: Flight departure date
decision: Decision type
Authentication: OAuth 2.0 Bearer Token (Airline, GHA, or ACA role)
\nAuthorization: Users see only responses relevant to their role and permissions.
\nUse Cases:
\nAirline: Monitor all responses for upcoming flights
\nGHA: View screening workload and priorities
\nACA: Track do-not-load decisions affecting consignors
\nCompliance: Audit trail of customs decisions
\nFilter by decision type
\n","type":"text/plain"},"key":"decision","value":"additional_screening"},{"description":{"content":"Filter by flight date
\n","type":"text/plain"},"key":"flightDate","value":"2025-11-25"},{"description":{"content":"Filter by customs authority
\n","type":"text/plain"},"key":"customsAuthority","value":"string"},{"description":{"content":"Filter by MAWB number
\n","type":"text/plain"},"key":"mawbNumber","value":"string"},{"description":{"content":"Page number
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort field
\n","type":"text/plain"},"key":"sort","value":"-receivedAt"}],"variable":[]}},"response":[{"id":"839d069b-8e54-4036-b772-0e73ed023b32","name":"Success - Response List","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E25DCC.4, CM.E25AL.5
\nUse Case: Push PLACI risk analysis decision to airline
\nDescription: ACS distributes PLACI response to airline
\nProcess Flow: E25DCC → E25AL
\nActors: ACS System, Airline (AL)
\nBusiness Context:
\nACS pushes the PLACI risk analysis decision to the airline that submitted the PLACI. This is a critical notification that determines whether cargo can be loaded on the aircraft.
\nThe airline MUST receive this decision before flight departure to ensure compliance with:
\nWCO PLACI standards
\nDestination country customs requirements
\nIATA security regulations
\nAviation security protocols
\nDistribution Logic:
\nALL Decisions → Airline receives:
\nComplete decision details
\nCustoms authority contact info
\nValidity period
\nNext action required
\nDecision-Specific Distribution:
\nLOAD: Airline only (proceed with loading)
\nADDITIONAL_INFORMATION: Airline + notification to ACA/Consignor
\nADDITIONAL_SCREENING: Airline + GHA notification
\nDO_NOT_LOAD: Airline + GHA + ACA (critical alert)
\nNotification Methods:
\napi: Push via API callback (if airline has webhook)
email: Email notification to operations team
sms: SMS alert for critical decisions (do-not-load)
portal: Portal notification (airline logs in to view)
Priority Levels:
\ncritical: Do-not-load decisions (immediate action required)
high: Additional screening (time-sensitive)
normal: Additional information (standard processing)
low: Load decision (informational)
Authentication: OAuth 2.0 Bearer Token (System role required)
\nProcess:
\nACS retrieves PLACI response
\nIdentifies airline from original submission
\nSends notification via specified method
\nRecords distribution timestamp
\nUpdates distribution status
\nSends email notification (if provided)
\nResponse: Confirmation of distribution with tracking.
\nNext Steps:
\nLOAD: Airline proceeds with loading
\nADDITIONAL_SCREENING: Airline coordinates with GHA
\nADDITIONAL_INFORMATION: Airline contacts ACA/Consignor
\nDO_NOT_LOAD: Airline rejects cargo, notifies ACA
\nPLACI response ID
\n","type":"text/plain"},"type":"any","value":"placi-resp-89e3f1d2","key":"id"}]}},"response":[{"id":"49b231f3-aa09-4569-bdf5-e5b8740df1ae","name":"Success - Pushed to Airline","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"2c39d5f2-98a1-40a3-b626-2604b8952a48"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E25DCC.4
\nUse Case: Push PLACI response to GHA for additional screening
\nDescription: ACS distributes PLACI response to GHA when screening required
\nProcess Flow: E25DCC → E27GHA
\nActors: ACS System, Ground Handling Agent (GHA)
\nBusiness Context:
\nWhen destination customs requires additional screening, ACS pushes the PLACI response to the Ground Handling Agent (GHA) responsible for cargo handling at the departure airport.
\nGHA must perform the requested screening before cargo can be loaded:
\nScreening Types:
\nX-ray: Standard X-ray screening of all packages
\nEDD: Explosive Detection Dog screening
\nETD: Explosive Trace Detection (swab test)
\nPhysical: Physical inspection of packages
\nCombined: Multiple screening methods required
\nGHA Responsibilities:
\nReceive screening instructions from customs
\nPerform requested screening before deadline
\nDocument screening results
\nSubmit results to ACS
\nProvide screening images/reports if required
\nClear or reject cargo based on screening outcome
\nScreening Instructions Include:
\nScreening type and method
\nSpecific focus areas (if any)
\nDeadline for completion
\nResults submission requirements
\nContact information for customs (if questions)
\nSpecial handling instructions
\nNotification Priority:
\nHigh: Default for all screening requests (time-sensitive)
\nCritical: If deadline is within 4 hours
\nAuthentication: OAuth 2.0 Bearer Token (System role required)
\nProcess:
\nACS validates response requires screening
\nIdentifies GHA from flight/airport
\nSends screening instructions to GHA
\nRecords distribution timestamp
\nSets screening deadline alert
\nSends email/SMS notification
\nResponse: Confirmation of distribution to GHA.
\nNext Steps:
\nGHA receives screening instructions
\nGHA performs screening (CM.E27GHA.6)
\nGHA submits screening results
\nIf cleared: Cargo can be loaded
\nIf failed: Cargo rejected (do-not-load equivalent)
\nPLACI response ID
\n","type":"text/plain"},"type":"any","value":"placi-resp-89e3f1d2","key":"id"}]}},"response":[{"id":"6b7a8f83-d298-4aef-a0cc-bf877ea1aebb","name":"Success - Pushed to GHA","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"af9c5769-fb96-4ebf-b41b-1a2e2d2a7eba"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E25AL.5
\nUse Case: Push do-not-load decision to ACA for consignor notification
\nProcess Flow: E25AL → E25ACA
\nActors: ACS System, Air Cargo Agent (ACA)
\nBusiness Context:
\nWhen destination customs issues a DO NOT LOAD decision, ACS must immediately notify the Air Cargo Agent (ACA) who filed the HAWB. The ACA is then responsible for:
\nNotifying Consignor: Inform shipper of rejection and reason
\nArranging Return: Coordinate return of cargo to consignor
\nDocumentation: Update shipment status and records
\nFinancial Settlement: Process refunds or adjustments
\nCompliance: Document regulatory violation for future reference
\nDo-Not-Load Reasons:
\nProhibited Goods: Items banned by destination country
\nDangerous Goods Violation: DG regulations not met
\nDocumentation Issues: Missing or invalid permits/certificates
\nSecurity Threat: Risk identified in screening/analysis
\nSanctions Violation: Shipper/consignee on restricted list
\nRegulatory Non-Compliance: Does not meet destination requirements
\nACA Required Actions:
\nContact consignor immediately
\nExplain rejection reason and regulation
\nArrange cargo return or disposal
\nCancel AWB allocation
\nUpdate shipment status to \"rejected\"
\nDocument compliance issue
\nAdvise consignor on corrective actions (if possible)
\nNotification Priority: CRITICAL
\nSMS alert sent immediately
\nEmail notification sent
\nAPI callback (if configured)
\nPortal alert displayed
\nMultiple notification channels ensure delivery
\nInformation Provided to ACA:
\nRejection reason and code
\nRegulation/law violated
\nRequired action (return, destroy, etc.)
\nCustoms authority contact for appeal
\nDeadline for cargo removal
\nConsignor contact information
\nAuthentication: OAuth 2.0 Bearer Token (System role required)
\nProcess:
\nACS validates decision is do-not-load
\nIdentifies ACA from HAWB data filer
\nSends critical alert via all channels
\nRecords distribution timestamp
\nSets follow-up reminder for ACA action
\nTracks consignor notification status
\nResponse: Confirmation of critical alert delivery.
\nNext Steps:
\nACA acknowledges receipt
\nACA notifies consignor
\nACA arranges cargo return
\nACA updates shipment status
\nACA submits action report to ACS
\nPLACI response ID (do-not-load decision)
\n","type":"text/plain"},"type":"any","value":"placi-resp-89e3f1d3","key":"id"}]}},"response":[{"id":"871f1b10-e796-4958-bb46-ca24a893cd51","name":"Success - Pushed to ACA (Critical)","originalRequest":{"method":"PATCH","header":[{"key":"X-Request-ID","value":"2bc69a4f-a8bb-4e45-9f56-33b032b7d6b3"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.E25DCC.4
\nUse Case: Submit additional information requested by destination customs
\nDescription: Response to customs request for additional information
\nProcess Flow: Consignor → ACA → E25AL → E25DCC
\nActors: Consignor (CGNR), Air Cargo Agent (ACA), Airline (AL)
\nBusiness Context:
\nWhen destination customs issues an ADDITIONAL INFORMATION decision, they require more details about the cargo before making a final load/do-not-load determination. The consignor must provide the requested information within the specified deadline.
\nCommon Information Requests:
\nCommodity Details:
\nDetailed product description
\nManufacturer information
\nCountry of origin
\nHS code verification
\nUnit and total values
\nBrand names and model numbers
\nBusiness Information:
\nIntended use of goods
\nBusiness relationship between shipper/consignee
\nPrevious shipment history
\nCommercial context
\nDocumentation:
\nCommercial invoice
\nCertificate of origin
\nProduct certifications
\nAuthorization letters
\nImport/export licenses
\nSafety/compliance certificates
\nProcess:
\nCustoms issues additional information request
\nAirline notifies ACA
\nACA contacts consignor with specific requirements
\nConsignor prepares detailed response
\nConsignor submits via ACA (or directly if digital trade lane enabled)
\nACS forwards to destination customs
\nCustoms reviews and issues final decision
\nSubmission Methods:
\nVia ACA: Consignor → ACA → ACS (most common)
\nDirect: Consignor → ACS (if digital trade lane enabled)
\nManual: Paper documents via courier (legacy)
\nSupporting Documents:
Documents must be uploaded separately using document management endpoints, then referenced by document ID in this submission.
Deadline Handling:
\nCustoms specifies deadline in original response
\nLate submissions may be rejected
\nExtensions can be requested via customs contact
\nCargo on hold until information received
\nAuthentication: OAuth 2.0 Bearer Token (Consignor or ACA role)
\nValidation:
\nPLACI response ID must exist with additional_information decision
All requested fields must be provided
\nSupporting documents must be uploaded first
\nSubmission must be within deadline
\nResponse: Confirmation of submission with forwarding status.
\nNext Steps:
\nACS validates submission completeness
\nACS forwards to destination customs
\nCustoms reviews additional information
\nCustoms issues final decision (load or do-not-load)
\nACS distributes final decision to stakeholders
\nRequirement Reference: CM.E25DCC.4, CM.E27GHA.6
\nUse Case: Submit additional screening results to destination customs
\nDescription: GHA submits screening results in response to customs request
\nProcess Flow: E27GHA → E28GHA → E25DCC
\nActors: Ground Handling Agent (GHA), Destination Country Customs (DCC)
\nBusiness Context:
\nWhen destination customs requires additional screening, the Ground Handling Agent (GHA) performs the requested screening and submits comprehensive results back to customs via ACS. The screening results determine whether cargo can proceed to loading or must be rejected.
\nScreening Types:
\nX-ray Screening:
\nStandard cargo X-ray
\nHigh-resolution imaging
\nMulti-angle views
\nImage analysis and interpretation
\nEDD (Explosive Detection Dog):
\nCanine explosive detection
\nHandler certification required
\nDog training/certification verification
\nETD (Explosive Trace Detection):
\nSwab testing for explosive residue
\nChemical analysis
\nDetection threshold levels
\nPhysical Inspection:
\nPackage opening and visual inspection
\nContents verification
\nPackaging integrity check
\nScreening Results:
\nCleared: No issues detected, cargo can be loaded
\nFailed: Anomaly detected, cargo rejected (becomes do-not-load)
\nInconclusive: Requires additional screening or manual review
\nRequired Information:
\nScreening Execution:
\nDate/time of screening
\nLocation and facility
\nEquipment used (make/model)
\nOperator credentials and certification
\nResults:
\nOverall result (cleared/failed/inconclusive)
\nNumber of packages screened
\nAnomalies detected (if any)
\nDetailed findings
\nDocumentation:
\nX-ray images (if X-ray screening)
\nScreening report document
\nOperator certification
\nEquipment calibration certificate
\nCertification:
\nStatement of compliance with ICAO/IATA standards
\nDigital signature of authorized screener
\nSupervisor approval
\nImage Requirements:
\nX-ray images must show full package contents
\nMultiple angles if anomaly detected
\nHigh resolution for customs review
\nImages uploaded separately, referenced by ID
\nReport Requirements:
\nDetailed screening methodology
\nEquipment specifications
\nOperator qualifications
\nPackage-by-package results
\nAny special observations
\nAuthentication: OAuth 2.0 Bearer Token (GHA role required)
\nValidation:
\nPLACI response ID must exist with additional_screening decision
Screening must be performed before deadline
\nOperator must have valid certification
\nEquipment must be calibrated/certified
\nAll required images/documents must be uploaded
\nCertification statement required
\nResponse: Confirmation of submission with forwarding status.
\nNext Steps:
\nACS validates screening results completeness
\nACS forwards results to destination customs
\nCustoms reviews screening results
\nCustoms issues final decision:
\nIf cleared: LOAD decision issued
\nIf failed: DO NOT LOAD decision issued
\nIf inconclusive: Additional screening or information requested
\nACS distributes final decision to stakeholders
\nGHA submits secondary security scan information including scan type, results, and metadata. This endpoint supports multiple scan types: X-ray, EDD (Explosive Detection Dog), and ETD (Explosive Trace Detection).
\nRequirement Reference: CM.E27GHA.6
\nUse Case: Secondary scanning, EDD, ETD
\nProcess Flow: E25DCC → E27GHA → E28GHA
\nActors: GHA, WeBOC, Destination Country Customs
\nAuthentication: OAuth 2.0 (GHA role required)
\nBusiness Context: After PLACI risk analysis indicates \"Additional Screening\" decision, GHA performs secondary security scans and submits results digitally. This replaces manual paper-based scan reports.
\nScan Types:
\nX-RAY: Secondary X-ray screening
\nEDD: Explosive Detection Dog inspection
\nETD: Explosive Trace Detection chemical analysis
\nKey Activities:
\nSubmit scan metadata (type, date, operator)
\nRecord scan results (clear/suspicious/prohibited)
\nLink to AWB and shipment
\nAutomatic notification to Customs
\nUpload security scan images (X-ray, photos, etc.) for a submitted security scan. Supports multiple image uploads per scan. Images are securely stored and accessible to authorized parties (Customs, Airlines).
\nRequirement Reference: CM.E27GHA.6
\nUse Case: Secondary scanning, EDD, ETD
\nProcess Flow: E27GHA → E28GHA
\nActors: GHA
\nAuthentication: OAuth 2.0 (GHA role required)
\nBusiness Context: Scan images provide visual evidence for Customs review. X-ray images show cargo contents, while photos document physical inspection.
\nSupported Formats: PNG, JPG, TIFF, DICOM
Max File Size: 10MB per image
Max Images: 20 per scan
Image Types:
\nX-ray scan images
\nPhysical inspection photos
\nEDD/ETD result photos
\nDocumentation photos
\nRetrieve a list of security scans with filtering and pagination.
\nRequirement Reference: CM.E27GHA.6
\nUse Case: Secondary scanning, EDD, ETD
\nActors: GHA, Customs, Airline
\nAuthentication: OAuth 2.0 (GHA/Customs/Airline roles)
\nFilter Options:
\nAWB/HAWB number
\nScan type
\nScan result
\nAirport
\nDate range
\nSort Options:
\nscanDate (default descending)
\nscanResult
\nstatus
\nFilter by AWB number
\n","type":"text/plain"},"key":"awbNumber","value":"176-12345678"},{"key":"hawbNumber","value":"PKEPO00012345"},{"description":{"content":"Filter by scan type: X-RAY, EDD, ETD
\n","type":"text/plain"},"key":"scanType","value":"X-RAY"},{"description":{"content":"Filter by result: CLEAR, SUSPICIOUS, PROHIBITED
\n","type":"text/plain"},"key":"scanResult","value":"CLEAR"},{"key":"airport","value":"KHI"},{"key":"scanDateFrom","value":"2025-11-01"},{"key":"scanDateTo","value":"2025-11-30"},{"key":"page","value":"1"},{"key":"limit","value":"20"},{"description":{"content":"Sort by field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-scanDate"}],"variable":[]}},"response":[{"id":"a467b9f0-b6de-44bf-ae27-53aa1b2e7b5b","name":"Success - Scan List","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerPush security scan information to WeBOC (Pakistan Customs). ACS acts as middleware hub to securely transmit scan data, images, and results to Customs for review.
\nPush security scan information to destination country customs authorities. Supports advance notification to destination for faster import clearance.
\nRequirement Reference: CM.E27GHA.6
\nUse Case: Secondary scanning, EDD, ETD
\nProcess Flow:
\nACS → WeBOC
\nACS → Destination Country Customs
\nActors: ACS (system), WeBOC, Destination Country Customs
\nAuthentication: OAuth 2.0 (System role)
\nBusiness Context:
\nACS middleware pattern ensures all communications are routed through central system for audit, security, and standardization. NO direct GHA-to-Customs connections.
\nSending security scan results to destination country Customs facilitates pre-clearance and reduces delays on arrival. Part of WCO security cooperation.
\nPush Payload Includes:
\nComplete scan metadata
\nScan results and findings
\nImage URLs (secure access)
\nAWB/HAWB linkage
\nOperator certification details
\nPush security scan information to destination country customs authorities. Supports advance notification to destination for faster import clearance.
\nRequirement Reference: CM.E27GHA.6
\nUse Case: Secondary scanning, EDD, ETD
\nProcess Flow: ACS → Destination Country Customs
\nActors: ACS (system), Destination Country Customs
\nAuthentication: OAuth 2.0 (System role)
\nBusiness Context: Sending security scan results to destination country Customs facilitates pre-clearance and reduces delays on arrival. Part of WCO security cooperation.
\nTransmission Protocol: Secure API or WCO Data Model XML
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","export","security-scans",":scanId","push","destination-customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"scan-789abc123","key":"scanId"}]}},"response":[{"id":"6bd7e8f0-6297-4145-845a-551d669cef96","name":"Success - Pushed to Destination","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"b3f8b29d-2b09-41b6-bf17-66d078c2150c"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerGHA submits Electronic Consignment Security Declaration (E-CSD) in JSON format. E-CSD certifies that cargo has been screened per ICAO security standards.
\nRequirement Reference: CM.E28AL.7
\nUse Case: E-CSD received
\nProcess Flow: E28GHA → E28AL
\nActors: GHA, Airline
\nAuthentication: OAuth 2.0 (GHA role required)
\nStandard: ICAO Doc 8973/Chapter 13/Appendix 33, IATA E-CSD
\nBusiness Context: E-CSD is mandatory for all air cargo shipments per ICAO regulations. It certifies that cargo has undergone security screening and is safe for air transport. Airlines cannot accept cargo without valid E-CSD.
\nE-CSD Required Fields (per ICAO Doc 8973):
\nEntity responsible for securing the cargo
\nContent of the commodity
\nAWB number
\nDeparture airport
\nDestination airport
\nScreening method
\nName of person issuing security status
\nDate of issuance
\nTime of issuance
\nScreening Methods:
\nX-RAY: X-ray inspection
\nPHYSICAL: Physical inspection
\nEDD: Explosive Detection Dog
\nETD: Explosive Trace Detection
\nEXEMPTION: Exempted cargo (diplomatic, medical emergency)
\nKC: Known Consignor (pre-authorized shipper)
\nGHA submits E-CSD in IATA E-CSD XML format. This format is used for airline system integration per IATA e-CSD standards.
\nRequirement Reference: CM.E28AL.7
\nUse Case: E-CSD received
\nProcess Flow: E28GHA → E28AL
\nActors: GHA, Airline
\nAuthentication: OAuth 2.0 (GHA role required)
\nStandard: IATA E-CSD XML Schema
\nBusiness Context: Many airline cargo systems natively support IATA E-CSD XML format. This endpoint allows GHA systems to submit E-CSD directly in XML without format conversion.
\nContent-Type: application/xml
XML Schema: IATA Cargo-XML E-CSD Schema v3.00
Retrieve list of E-CSD submissions with filtering and pagination.
\nRequirement Reference: CM.E28AL.7
\nUse Case: E-CSD received
\nActors: GHA, Airline, Customs
\nAuthentication: OAuth 2.0
\nFilter Options:
\nAWB/HAWB number
\nStatus (ISSUED, EXPIRED, REVOKED)
\nAirport
\nAirline
\nDate range
\nPush E-CSD data to Airline cargo system. ACS acts as middleware hub to securely transmit E-CSD to airlines for cargo acceptance verification.
\nRequirement Reference: CM.E28AL.7
\nUse Case: E-CSD received
\nProcess Flow: ACS → Airline
\nActors: ACS (system), Airline
\nAuthentication: OAuth 2.0 (System role)
\nBusiness Context: Airlines MUST receive valid E-CSD before accepting cargo per ICAO regulations. ACS middleware ensures E-CSD is delivered to airline system with audit trail.
\nTransmission Options:
\nJSON format for modern airline APIs
\nIATA E-CSD XML for legacy systems
\nEmail notification with PDF attachment
\nGHA creates a new digital pouch container for consolidating shipment documents. Digital pouch replaces traditional physical paper pouch carried with cargo.
\nRequirement Reference: CM.E32GHA.8
\nUse Case: Digital Pouch is created and shared with the Airline
\nProcess Flow: E31GHA → E32GHA → E33AL
\nActors: GHA, Airline
\nAuthentication: OAuth 2.0 (GHA role required)
\nBusiness Context: Digital pouch digitizes the document package traditionally placed in plastic pouch and attached to shipment. Benefits include:
\nFaster document access for destination handlers
\nNo risk of lost/damaged documents
\nImmediate sharing with multiple parties
\nReduced environmental impact (paperless)
\nAudit trail of document access
\nLifecycle:
\nCreate pouch (DRAFT status)
\nAdd documents
\nFinalize pouch (locks from edits)
\nShare with airline
\nAirline accesses documents at destination
\nAdd a document to the digital pouch. Documents can only be added to pouches in DRAFT status.
\nRequirement Reference: CM.E32GHA.8
\nUse Case: Digital Pouch is created and shared with the Airline
\nProcess Flow: E31GHA → E32GHA
\nActors: GHA
\nAuthentication: OAuth 2.0 (GHA role required)
\nDocument Types:
\nMAWB: Master Air Waybill
\nHAWB: House Air Waybill
\nGD: Goods Declaration
\nPACKING_LIST: Packing list
\nINVOICE: Commercial invoice
\nCERTIFICATE: Export certificate
\nNOC: No Objection Certificate
\nOTHER: Other supporting documents
\nSupported Formats: PDF, PNG, JPG, TIFF
Max File Size: 10MB per document
Max Documents: 50 per pouch
Retrieve list of digital pouches with filtering and pagination.
\nRequirement Reference: CM.E32GHA.8
\nUse Case: Digital Pouch is created and shared with the Airline
\nActors: GHA, Airline
\nAuthentication: OAuth 2.0
\nFilter Options:
\nMAWB number
\nStatus
\nFlight number/date
\nAirline
\nOrigin/destination
\nDRAFT, FINALIZED, SHARED
\n","type":"text/plain"},"key":"status","value":"FINALIZED"},{"key":"flightNumber","value":"EK-600"},{"key":"flightDate","value":"2025-11-24"},{"key":"airlineCode","value":"EK"},{"key":"origin","value":"KHI"},{"key":"destination","value":"DXB"},{"key":"page","value":"1"},{"key":"limit","value":"20"},{"key":"sort","value":"-createdAt"}],"variable":[]}},"response":[{"id":"d8d08790-b0fa-4a8a-afeb-459325069633","name":"Success - Pouch List","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerFinalize digital pouch to lock from further edits. Once finalized, no documents can be added or removed. Finalization is required before sharing with airline.
\nRequirement Reference: CM.E32GHA.8
\nUse Case: Digital Pouch is created and shared with the Airline
\nProcess Flow: E32GHA
\nActors: GHA
\nAuthentication: OAuth 2.0 (GHA role required)
\nBusiness Context: Finalizing ensures document package integrity. Airlines receive complete, unmodified pouch. Prevents accidental document changes after sharing.
\nValidation:
\nMust have at least 1 document
\nMAWB document required
\nAll required documents for customs clearance present
\nShare finalized digital pouch with Airline. ACS acts as middleware hub to securely grant airline access to digital pouch and all contained documents.
\nRequirement Reference: CM.E32GHA.8
\nUse Case: Digital Pouch is created and shared with the Airline
\nProcess Flow: ACS → Airline
\nActors: ACS (system), Airline
\nAuthentication: OAuth 2.0 (System role)
\nBusiness Context: Sharing digital pouch grants airline personnel secure access to all shipment documents. Airline can access pouch from any location (origin, destination, transit). Replaces physical handoff of paper pouch.
\nAccess Control:
\nAirline users with cargo handling role can access
\nAudit log tracks all document views/downloads
\nAccess expires after flight completion + 90 days
\nNotification:
\nEmail to airline cargo team
\nSMS to flight handler (optional)
\nAPI callback to airline system (if configured)
\nRequirement Reference: CM.I1AL.1
\nUse Case: Airline sends PLACI data to Customs for risk analysis
\nDescription: ACS enables Customs to receive PLACI data digitally
\nProcess Flow: I1AL → I1CUS
\nActors: Airline (AL), Customs (CUS)
\nStandard: WCO PLACI Standard
\nAction: PUSH
\nPriority: P1 (F/1)
\nAuthentication: OAuth 2.0 Bearer Token (Airline role required)
\nBusiness Context:
Airlines must submit PLACI data for all import cargo to WeBOC (Web-Based One Customs) before the flight departs from the origin country. This enables Pakistan Customs to perform advance risk assessment and identify shipments requiring additional information, additional screening, or those prohibited from loading (do not load).
WCO PLACI Mandatory Data Elements:
\nConsignor name and address
\nConsignee name and address
\nNumber of packages
\nTotal gross weight (including measure unit qualifier)
\nBrief cargo description
\nData filer identification (provided with HAWB and/or MAWB)
\nMessage Flow:
\nAirline submits PLACI → ACS
\nACS forwards to WeBOC → Customs
\nCustoms performs risk analysis
\nCustoms sends decision back to Airline via ACS
\nFour PLACI Decisions:
\nLoad - Cleared for loading
\nAdditional Information - Requires more details
\nAdditional Screening - Requires physical inspection
\nDo Not Load - Prohibited from loading
\nRequirement Reference: CM.I1AL.1
\nUse Case: Airline sends PLACI data to Customs for risk analysis
\nDescription: ACS enables Customs to receive PLACI data digitally
\nProcess Flow: I1AL → I1CUS
\nActors: Airline (AL), Customs (CUS)
\nMessage Format: WCO PLACI XML Standard
\nStandard: WCO PLACI Standard (XML)
\nAction: PUSH
\nPriority: P1 (F/1)
\nAuthentication: OAuth 2.0 Bearer Token (Airline role required)
\nBusiness Context:
This endpoint accepts PLACI data in the official WCO PLACI XML format. Airlines using existing PLACI systems can submit XML directly without converting to JSON. The ACS will parse the XML, validate against WCO PLACI schema, and forward to WeBOC.
WCO PLACI XML Schema Elements:
\nMessageHeader: Sender, Receiver, DateTime, Reference
\nFlightDetails: Carrier, Flight, Airports, Schedule
\nConsignments: AWB details, Parties, Cargo, Value
\nValidation:
\nXML must be well-formed and valid against WCO PLACI XSD schema
\nAll mandatory elements must be present
\nCountry codes must be ISO 3166-1 alpha-2
\nAirport codes must be IATA 3-letter codes
\nWeight units must be KG or LB
\nHS codes must be valid 6-10 digit codes
\nRequirement Reference: CM.I1AL.1, CM.I1CUS.3
\nUse Case: List import PLACI submissions with filtering
\nDescription: Airline and Customs view PLACI submissions
\nProcess Flow: I1AL, I1CUS
\nActors: Airline (AL), Customs (CUS)
\nAction: GET
\nPriority: P1 (F/1)
\nAuthentication: OAuth 2.0 Bearer Token (Airline or Customs role required)
\nBusiness Context:
Provides a paginated list of PLACI submissions with filtering capabilities. Airlines can filter by their own submissions, flight dates, and assessment status. Customs can view all submissions for risk analysis workflow.
Filter Options:
\nflightDate: ISO 8601 date (YYYY-MM-DD)
\nstatus: submitted, risk_assessed, completed
\nairlineCode: IATA 2-letter airline code
\ndepartureAirport: IATA 3-letter airport code
\narrivalAirport: IATA 3-letter airport code
\nriskDecision: load, additional_information, additional_screening, do_not_load
\nSorting: Default sort by submittedAt DESC
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","placi-submissions"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"description":{"content":"Filter by flight date
\n","type":"text/plain"},"key":"flightDate","value":"2025-11-24"},{"description":{"content":"Filter by status: submitted, risk_assessed, completed
\n","type":"text/plain"},"key":"status","value":"pending"},{"description":{"content":"Filter by airline IATA code
\n","type":"text/plain"},"key":"airlineCode","value":"EK"},{"description":{"content":"Filter by departure airport
\n","type":"text/plain"},"key":"departureAirport","value":"DXB"},{"description":{"content":"Filter by arrival airport
\n","type":"text/plain"},"key":"arrivalAirport","value":"KHI"},{"description":{"content":"Page number
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (max 100)
\n","type":"text/plain"},"key":"limit","value":"20"}],"variable":[]}},"response":[{"id":"b379480e-0413-4b79-89c0-34835658eebb","name":"Success - PLACI List","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.I1AL.1
\nUse Case: Push PLACI data to WeBOC (Customs)
\nDescription: ACS → WeBOC (forward PLACI to Customs)
\nProcess Flow: I1AL → I1CUS (ACS middleware push)
\nActors: ACS (System), WeBOC (Customs)
\nAction: PUSH
\nPriority: P1 (F/1)
\nAuthentication: OAuth 2.0 Bearer Token (System/Admin role required)
\nBusiness Context:
This is an ACS middleware operation that pushes PLACI data from ACS to WeBOC (Web-Based One Customs) for risk analysis. This endpoint is typically called automatically when PLACI is submitted, but can also be triggered manually for retry scenarios.
ACS Middleware Pattern:
\nAirline submits PLACI → ACS
\nACS validates and stores PLACI
\nACS pushes to WeBOC → Customs
\nNO direct Airline → WeBOC connection
\nACS ensures traceability and audit trail
\nPush Payload Includes:
\nComplete PLACI data (all shipments)
\nAirline identification
\nFlight details
\nRequest for risk assessment
\nACS reference for response correlation
\nRetry Logic:
\nIf WeBOC is unavailable, ACS will retry automatically
\nManual retry available via this endpoint
\nStatus tracked: pending_push, pushed, push_failed
\nRequirement Reference: CM.I1P.2
\nUse Case: Postal authority sends CN data before flight departure for PLACI risk assessment
\nDescription: ACS enables Customs to receive postal shipment data digitally
\nProcess Flow: I1P → I1CUS
\nActors: Postal Authority (P), Customs (CUS)
\nStandard: UPU Standards (Universal Postal Union)
\nAction: PUSH
\nPriority: P1 (F/1)
\nAuthentication: OAuth 2.0 Bearer Token (Postal Authority role required)
\nBusiness Context:
Postal authorities from origin countries must submit CN (Consignment Note) data for postal shipments to WeBOC before flight departure. This enables Pakistan Customs to perform PLACI risk assessment on mail items. UPU standards govern postal data interchange.
UPU CN Data Elements:
\nCN Number (unique consignment note identifier)
\nConsignor name and address
\nConsignee name and address (including phone/email)
\nNumber of packages
\nGross weight (with unit qualifier)
\nBrief cargo description
\nDeclared value for customs
\nItem type (letter, parcel, package)
\nMail class (priority, economy, express)
\nMessage Flow:
\nPostal Authority submits CN data → ACS
\nACS forwards to WeBOC → Customs
\nCustoms performs PLACI risk analysis
\nCustoms sends acknowledgment/decision back to Postal Authority via ACS
\nPLACI Decisions for Postal Items:
\nLoad - Cleared for loading
\nAdditional Information - Requires more consignee details
\nAdditional Screening - Requires physical inspection
\nDo Not Load - Prohibited from loading
\nPostal-Specific Rules:
\nLower value thresholds for simplified clearance
\nImmediate release procedures for low-risk items
\nSpecial handling for express postal items
\nRequirement Reference: CM.I1P.2
\nUse Case: Postal authority sends CN data before flight departure for PLACI risk assessment
\nDescription: ACS enables Customs to receive postal shipment data digitally
\nProcess Flow: I1P → I1CUS
\nActors: Postal Authority (P), Customs (CUS)
\nMessage Format: UPU XML Standard (ITMATT)
\nStandard: UPU Standards (Universal Postal Union)
\nAction: PUSH
\nPriority: P1 (F/1)
\nAuthentication: OAuth 2.0 Bearer Token (Postal Authority role required)
\nBusiness Context:
This endpoint accepts postal CN data in the UPU ITMATT XML format. Postal authorities using existing UPU systems can submit XML directly. The ACS will parse the XML, validate against UPU schema, and forward to WeBOC for PLACI risk assessment.
UPU ITMATT XML Schema Elements:
\nMessageHeader: Sender, Receiver, DateTime, Reference
\nFlightDetails: Flight, Airports, Schedule
\nPostalAuthority: Name, Code, Country
\nMailItems: CN details, Sender/Recipient, Cargo, Value
\nValidation:
\nXML must be well-formed and valid against UPU ITMATT XSD schema
\nAll mandatory elements must be present
\nCN numbers must be unique
\nCountry codes must be ISO 3166-1 alpha-2
\nAirport codes must be IATA 3-letter codes
\nWeight units must be KG or LB
\nHS codes must be valid 6-10 digit codes
\nRequirement Reference: CM.I1P.2, CM.I1CUS.3
\nUse Case: List postal PLACI submissions with filtering
\nDescription: Postal Authority and Customs view CN submissions
\nProcess Flow: I1P, I1CUS
\nActors: Postal Authority (P), Customs (CUS)
\nAction: GET
\nPriority: P1 (F/1)
\nAuthentication: OAuth 2.0 Bearer Token (Postal Authority or Customs role required)
\nBusiness Context:
Provides a paginated list of postal PLACI submissions with filtering capabilities. Postal authorities can filter by their own submissions, flight dates, and assessment status. Customs can view all submissions for risk analysis workflow.
Filter Options:
\nflightDate: ISO 8601 date (YYYY-MM-DD)
\nstatus: submitted, risk_assessed, completed
\npostalAuthorityCode: Postal authority identifier
\ndepartureAirport: IATA 3-letter airport code
\narrivalAirport: IATA 3-letter airport code
\nriskDecision: load, additional_information, additional_screening, do_not_load
\nmailClass: priority, economy, express
\nSorting: Default sort by submittedAt DESC
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","postal-placi-submissions"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"description":{"content":"Filter by flight date
\n","type":"text/plain"},"key":"flightDate","value":"2025-11-24"},{"description":{"content":"Filter by status: submitted, risk_assessed, completed
\n","type":"text/plain"},"key":"status","value":"pending"},{"description":{"content":"Filter by postal authority code
\n","type":"text/plain"},"key":"postalAuthorityCode","value":"TR-POST"},{"description":{"content":"Filter by departure airport
\n","type":"text/plain"},"key":"departureAirport","value":"IST"},{"description":{"content":"Filter by arrival airport
\n","type":"text/plain"},"key":"arrivalAirport","value":"KHI"},{"description":{"content":"Page number
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (max 100)
\n","type":"text/plain"},"key":"limit","value":"20"}],"variable":[]}},"response":[{"id":"965f08cb-f619-41c6-89bf-262af11028f3","name":"Success - Postal PLACI List","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.I1P.2
\nUse Case: Push postal CN data to WeBOC (Customs)
\nDescription: ACS → WeBOC (forward postal CN to Customs)
\nProcess Flow: I1P → I1CUS (ACS middleware push)
\nActors: ACS (System), WeBOC (Customs)
\nAction: PUSH
\nPriority: P1 (F/1)
\nAuthentication: OAuth 2.0 Bearer Token (System/Admin role required)
\nBusiness Context:
This is an ACS middleware operation that pushes postal CN data from ACS to WeBOC (Web-Based One Customs) for PLACI risk analysis. This endpoint is typically called automatically when CN data is submitted, but can also be triggered manually for retry scenarios.
ACS Middleware Pattern:
\nPostal Authority submits CN data → ACS
\nACS validates and stores CN data
\nACS pushes to WeBOC → Customs
\nNO direct Postal → WeBOC connection
\nACS ensures traceability and audit trail
\nPush Payload Includes:
\nComplete CN data (all mail items)
\nPostal authority identification
\nFlight details
\nRequest for PLACI risk assessment
\nACS reference for response correlation
\nRetry Logic:
\nIf WeBOC is unavailable, ACS will retry automatically
\nManual retry available via this endpoint
\nStatus tracked: pending_push, pushed, push_failed
\nPostal-Specific Processing:
\nUPU standards compliance
\nMail item classification
\nSimplified clearance thresholds
\nExpress postal handling
\nRequirement Reference: CM.I2CUS.4
\nUse Case: Communicate risk analysis result to Airline/Postal Authority (Integration Points: IN-CM.I2CUS.4-1, IN-CM.I2CUS.4-2)
\nDescription: ACS enables Customs to digitally send risk analysis results per consignment
\nProcess Flow: I1CUS → I2CUS → I2AL/I2P
\nActors: Customs (WeBOC), ACS
\nBusiness Context: After completing PLACI risk analysis, WeBOC (Customs) sends risk assessment results to ACS, which then routes to appropriate stakeholders (Airline or Postal Authority). Four possible decisions:
\nLOAD - Cleared for loading, no issues
\nADDITIONAL_INFORMATION - Requires more details from consignor
\nADDITIONAL_SCREENING - Requires X-ray or physical inspection
\nDO_NOT_LOAD - Prohibited from loading, must be returned
\nAuthentication: OAuth 2.0 JWT Bearer token (Customs role required)
\nValidation Rules:
\nRisk decision must be one of: LOAD, ADDITIONAL_INFORMATION, ADDITIONAL_SCREENING, DO_NOT_LOAD
\nRisk level: LOW, MEDIUM, HIGH, CRITICAL
\nplaciSubmissionId must reference valid submission
\nvalidUntil must be future timestamp
\nIf ADDITIONAL_INFORMATION, must specify required fields
\nIf ADDITIONAL_SCREENING, must specify screening type
\nIf DO_NOT_LOAD, must provide detailed reason
\nNotification Workflow:
\nACS automatically pushes to airline or postal based on notificationTargets
\nEmail/SMS alerts sent to data filer
\nStatus updated in PSW portal
\nStandards: WCO PLACI Standard for risk assessment messaging
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","placi-responses"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"202a6ab3-748b-41e3-ac39-7e03f0cab82e","name":"Success - Load Decision","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"placiSubmissionId\": \"placi-import-sub-789012\",\n \"awbNumber\": \"176-87654321\",\n \"riskDecision\": \"LOAD\",\n \"riskLevel\": \"LOW\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.psw.gov.pk/api/v1/import/placi-responses"},"status":"Created","code":201,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json"},{"key":"Location","value":"/api/v1/import/placi-responses/placi-resp-imp-567890"}],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"placi-resp-imp-567890\",\n \"placiSubmissionId\": \"placi-import-sub-789012\",\n \"awbNumber\": \"176-87654321\",\n \"flightNumber\": \"EK-612\",\n \"flightDate\": \"2025-11-28\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"consignor\": {\n \"name\": \"Dubai Electronics LLC\",\n \"address\": \"Sheikh Zayed Road, Dubai, UAE\"\n },\n \"consignee\": {\n \"name\": \"Pakistan Tech Imports\",\n \"address\": \"Clifton Block 5, Karachi, Pakistan\"\n },\n \"riskDecision\": \"LOAD\",\n \"riskLevel\": \"LOW\",\n \"riskScore\": 15,\n \"decisionReason\": \"No risk indicators identified. Cleared for loading.\",\n \"additionalInfoRequired\": false,\n \"additionalScreeningRequired\": false,\n \"doNotLoad\": false,\n \"analysisTimestamp\": \"2025-11-27T14:30:00Z\",\n \"validUntil\": \"2025-11-28T10:00:00Z\",\n \"status\": \"COMMUNICATED\",\n \"notificationsSent\": [\n {\n \"target\": \"airline\",\n \"targetId\": \"airline-emirates\",\n \"sentAt\": \"2025-11-27T14:30:15Z\",\n \"status\": \"DELIVERED\"\n }\n ],\n \"createdAt\": \"2025-11-27T14:30:00Z\",\n \"updatedAt\": \"2025-11-27T14:30:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:30:00Z\",\n \"requestId\": \"req-789456\"\n }\n}"},{"id":"8227ddd6-5a8c-449f-996b-f2e81c84f183","name":"Success - Additional Information Required","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"placiSubmissionId\": \"placi-import-sub-789013\",\n \"awbNumber\": \"176-87654322\",\n \"riskDecision\": \"ADDITIONAL_INFORMATION\",\n \"riskLevel\": \"MEDIUM\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.psw.gov.pk/api/v1/import/placi-responses"},"status":"Created","code":201,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json"}],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"placi-resp-imp-567891\",\n \"placiSubmissionId\": \"placi-import-sub-789013\",\n \"awbNumber\": \"176-87654322\",\n \"flightNumber\": \"PK-307\",\n \"flightDate\": \"2025-11-28\",\n \"origin\": \"LHR\",\n \"destination\": \"ISB\",\n \"riskDecision\": \"ADDITIONAL_INFORMATION\",\n \"riskLevel\": \"MEDIUM\",\n \"riskScore\": 55,\n \"decisionReason\": \"Incomplete consignor details. Additional information required before clearance.\",\n \"additionalInfoRequired\": true,\n \"requiredInformation\": [\n {\n \"field\": \"consignor.taxId\",\n \"description\": \"Tax identification number of consignor\",\n \"mandatory\": true\n },\n {\n \"field\": \"cargo.detailedDescription\",\n \"description\": \"Detailed description of cargo contents with HS codes\",\n \"mandatory\": true\n },\n {\n \"field\": \"cargo.commercialInvoice\",\n \"description\": \"Upload commercial invoice PDF\",\n \"mandatory\": true\n }\n ],\n \"responseDeadline\": \"2025-11-28T06:00:00Z\",\n \"additionalScreeningRequired\": false,\n \"doNotLoad\": false,\n \"status\": \"AWAITING_INFO\",\n \"createdAt\": \"2025-11-27T14:35:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:35:00Z\",\n \"requestId\": \"req-789457\"\n }\n}"},{"id":"430705d0-a661-47e6-b225-919e993c6591","name":"Success - Additional Screening Required","originalRequest":{"method":"POST","header":[],"body":{"mode":"raw","raw":"{\n \"placiSubmissionId\": \"placi-import-sub-789014\",\n \"awbNumber\": \"176-87654323\",\n \"riskDecision\": \"ADDITIONAL_SCREENING\",\n \"riskLevel\": \"HIGH\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.psw.gov.pk/api/v1/import/placi-responses"},"status":"Created","code":201,"_postman_previewlanguage":"json","header":[{"key":"Content-Type","value":"application/json"}],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"placi-resp-imp-567892\",\n \"placiSubmissionId\": \"placi-import-sub-789014\",\n \"awbNumber\": \"176-87654323\",\n \"flightNumber\": \"TK-719\",\n \"flightDate\": \"2025-11-28\",\n \"origin\": \"IST\",\n \"destination\": \"LHE\",\n \"riskDecision\": \"ADDITIONAL_SCREENING\",\n \"riskLevel\": \"HIGH\",\n \"riskScore\": 78,\n \"decisionReason\": \"High-risk origin country. X-ray screening required before clearance.\",\n \"additionalInfoRequired\": false,\n \"additionalScreeningRequired\": true,\n \"screeningRequirements\": [\n {\n \"type\": \"XRAY\",\n \"description\": \"100% X-ray screening of all packages\",\n \"mandatory\": true\n },\n {\n \"type\": \"ETD\",\n \"description\": \"Explosive Trace Detection sampling\",\n \"mandatory\": true\n }\n ],\n \"screeningLocation\": \"Customs Examination Facility - Lahore Airport\",\n \"screeningDeadline\": \"2025-11-28T08:00:00Z\",\n \"doNotLoad\": false,\n \"status\": \"AWAITING_SCREENING\",\n \"createdAt\": \"2025-11-27T14:40:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-27T14:40:00Z\",\n \"requestId\": \"req-789458\"\n }\n}"},{"id":"b8702a03-0f29-4dc7-8ebf-fbac1096e9b0","name":"Success - Load Decision","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"7e7d1b96-94af-41f8-a2c0-e05abb4d54ca"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.I2CUS.4
\nUse Case: List all PLACI risk analysis responses with filtering
\nProcess Flow: Query PLACI responses
\nActors: Customs, ACS
\nAuthentication: OAuth 2.0 JWT Bearer token
\nQuery Parameters:
\nFilter by decision type: LOAD, ADDITIONAL_INFORMATION, ADDITIONAL_SCREENING, DO_NOT_LOAD
\n","type":"text/plain"},"key":"riskDecision","value":"LOAD"},{"key":"riskLevel","value":"HIGH"},{"key":"flightDate","value":"2025-11-28"},{"key":"awbNumber","value":"176-87654321"},{"key":"status","value":"COMMUNICATED"},{"key":"page","value":"1"},{"key":"limit","value":"20"}],"variable":[]}},"response":[],"_postman_id":"c407fda9-4bf3-4fce-9100-6799b04a4d3c"},{"name":"Push PLACI Result to Airline","id":"7db8ad89-faf5-4c11-acc8-798efb87aed7","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"airlineId\": \"airline-emirates\",\n \"notificationMethod\": \"API_PUSH\",\n \"includeFullDetails\": true,\n \"urgency\": \"HIGH\"\n}","options":{"raw":{"headerFamily":"json","language":"json"}}},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/placi-responses/:responseId/push/airline","description":"Requirement Reference: CM.I2CUS.4, Integration Point IN-CM.I2CUS.4-2
\nUse Case: Communicate risk analysis result to Airline
\nDescription: ACS enables Customs to digitally send risk analysis results per consignment (to Airline)
\nProcess Flow: I2CUS → I2AL
\nActors: Customs, ACS, Airline
\nBusiness Context: ACS pushes PLACI risk analysis results from WeBOC to Airline. Airline must take action based on decision type:
\nLOAD: Proceed with loading
\nADDITIONAL_INFORMATION: Request info from consignor
\nADDITIONAL_SCREENING: Arrange screening
\nDO_NOT_LOAD: Prevent loading, return cargo
\nACS Middleware Pattern: NO direct WeBOC ↔ Airline connection. All communication flows through ACS.
\nAuthentication: OAuth 2.0 JWT Bearer token (ACS system role)
\nNotification Methods:
\nAPI_PUSH: Real-time API push to airline system
\nEMAIL: Email to airline cargo operations
\nSMS: SMS to duty manager (urgent only)
\nPORTAL: Display in airline portal
\nRequirement Reference: CM.I2CUS.4, Integration Point IN-CM.I2CUS.4-1
\nUse Case: Communicate risk analysis result to Postal Authority
\nDescription: ACS enables Customs to digitally send risk analysis results per consignment (to Postal)
\nProcess Flow: I2CUS → I2P
\nActors: Customs, ACS, Postal Authority
\nBusiness Context: ACS pushes PLACI risk analysis results from WeBOC to Postal Authority (Pakistan Post or EPO). Postal authority must take action based on decision.
\nStandards: UPU standards for postal shipment communications
\nACS Middleware Pattern: NO direct WeBOC ↔ Postal connection. All communication flows through ACS.
\nAuthentication: OAuth 2.0 JWT Bearer token (ACS system role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","placi-responses",":responseId","push","postal"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"placi-resp-imp-567891","key":"responseId"}]}},"response":[{"id":"a2bbb279-328e-4660-848f-680be73b0e18","name":"Success - Pushed to Postal","originalRequest":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CM.I2AL.5
\nUse Case: Airline lists all PLACI results for their flights
\nProcess Flow: Query PLACI results for airline
\nActors: Airline, ACS
\nAuthentication: OAuth 2.0 JWT Bearer token (Airline role)
\nQuery Parameters:
\nShow only results requiring airline action
\n","type":"text/plain"},"key":"actionRequired","value":"true"},{"key":"page","value":"1"},{"key":"limit","value":"20"}],"variable":[]}},"response":[],"_postman_id":"18b8beec-b112-45c5-97b6-d225988bc9be"},{"name":"Request Additional Information from Consignor","id":"63c5cbe5-a084-4b27-b82a-9ea2705c18b3","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"placiResponseId\": \"placi-resp-imp-567891\",\n \"awbNumber\": \"176-87654322\",\n \"consignorId\": \"consignor-uae-electronics-456\",\n \"consignorEmail\": \"exports@uaeelectronics.ae\",\n \"consignorPhone\": \"+971-4-1234567\",\n \"requestType\": \"ADDITIONAL_INFORMATION\",\n \"requiredFields\": [\n {\n \"field\": \"consignor.taxId\",\n \"description\": \"Tax identification number of consignor\",\n \"currentValue\": null,\n \"mandatory\": true,\n \"format\": \"UAE TRN format: 123456789012345\"\n },\n {\n \"field\": \"cargo.detailedDescription\",\n \"description\": \"Detailed description of cargo contents with HS codes\",\n \"currentValue\": \"Electronics\",\n \"mandatory\": true,\n \"instructions\": \"Please provide specific product names, models, and corresponding HS codes\"\n },\n {\n \"field\": \"cargo.commercialInvoice\",\n \"description\": \"Upload commercial invoice PDF\",\n \"mandatory\": true,\n \"fileType\": \"PDF\",\n \"maxSize\": \"5MB\"\n }\n ],\n \"responseDeadline\": \"2025-11-28T06:00:00Z\",\n \"urgency\": \"HIGH\",\n \"customsReason\": \"Incomplete consignor details. Additional information required before clearance.\",\n \"consequenceOfNonCompliance\": \"Flight will depart without this shipment. Cargo will be offloaded and returned to origin.\",\n \"airlineContactPerson\": {\n \"name\": \"Ali Ahmed\",\n \"designation\": \"Cargo Operations Manager\",\n \"email\": \"ali.ahmed@emirates.com\",\n \"phone\": \"+92-21-9876543\"\n },\n \"notificationMethods\": [\n \"EMAIL\",\n \"SMS\"\n ],\n \"language\": \"en\"\n}","options":{"raw":{"headerFamily":"json","language":"json"}}},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/placi-additional-info-requests","description":"Requirement Reference: CM.I2AL.5, Integration Point IN-CM.I2AL.5-2
\nUse Case: Airline communicates additional information or do not load status to Consignor
\nDescription: ACS enables Airline to transmit additional info or do not load status digitally to Consignor
\nProcess Flow: I2AL → I3CGNR
\nActors: Airline, Consignor, ACS
\nBusiness Context: When Customs issues ADDITIONAL_INFORMATION decision, Airline must contact consignor to request missing/incomplete information. This endpoint:
\nCreates formal information request
\nNotifies consignor via email/SMS
\nProvides secure portal link for response
\nTracks deadline and sends reminders
\nAlerts airline when consignor responds
\nAuthentication: OAuth 2.0 JWT Bearer token (Airline role required)
\nValidation Rules:
\nplaciResponseId must reference valid PLACI response with ADDITIONAL_INFORMATION decision
\nresponseDeadline must be before flight departure
\nAll mandatory fields must be specified
\nConsignor contact information required
\nWorkflow:
\nAirline creates request via this endpoint
\nACS sends notification to consignor
\nConsignor submits response via companion endpoint
\nAirline reviews and forwards to Customs
\nCustoms re-evaluates and updates decision
\nRequirement Reference: CM.I2AL.5, Integration Point IN-CM.I2AL.5-2
\nUse Case: Consignor provides additional information in response to Airline request
\nDescription: ACS enables Airline to transmit additional info digitally to Customs (via Consignor response)
\nProcess Flow: I3CGNR → I2AL → I2CUS (forwarded to Customs)
\nActors: Consignor, Airline, ACS, Customs
\nBusiness Context: Consignor submits requested information to resolve ADDITIONAL_INFORMATION decision. Once submitted:
\nAirline receives notification
\nAirline reviews response for completeness
\nAirline forwards to Customs for re-evaluation
\nCustoms updates PLACI decision (typically to LOAD)
\nAuthentication: OAuth 2.0 JWT Bearer token (Consignor role required)
\nValidation Rules:
\nAll mandatory fields must be provided
\nDocument uploads must be valid file types
\nResponse must be within deadline
\nField values must match format requirements
\nAutomatic Workflows:
\nAirline notified immediately upon submission
\nCustoms notified after airline review
\nStatus updated in PSW portal
\nTimeline event recorded
\nRequirement Reference: CM.I2AL.5, Integration Point IN-CM.I2AL.5-1
\nUse Case: Airline submits additional screening results to Customs
\nDescription: ACS enables Airline to receive risk analysis and respond digitally (screening results)
\nProcess Flow: I2AL → I2CUS (screening results forwarded to Customs)
\nActors: Airline, ACS, Customs
\nBusiness Context: When Customs issues ADDITIONAL_SCREENING decision, Airline must coordinate X-ray and/or ETD (Explosive Trace Detection) screening at destination airport. After screening, results are submitted to Customs for re-evaluation.
\nScreening Types:
\nXRAY: X-ray imaging of all packages
\nETD: Explosive Trace Detection sampling
\nPHYSICAL: Physical inspection of contents
\nXRAY_ETD: Combined X-ray and ETD screening
\nScreening Results:
\nCLEAR/NEGATIVE: No issues found, recommend approval
\nSUSPICIOUS: Items requiring further investigation
\nPOSITIVE: Prohibited/dangerous items detected
\nAuthentication: OAuth 2.0 JWT Bearer token (Airline role required)
\nValidation Rules:
\nplaciResponseId must reference PLACI response with ADDITIONAL_SCREENING decision
\nAll required screening methods must be completed
\nScreening officers must have valid licenses
\nX-ray images and reports must be uploaded
\nScreening must occur at approved facility
\nAutomatic Workflows:
\nResults submitted by airline
\nACS forwards to WeBOC (Customs)
\nCustoms reviews screening results
\nCustoms updates PLACI decision
\nUpdated decision pushed to airline
\nIf cleared, cargo approved for loading
\nRequirement Reference: CM.I2P.6
\nUse Case: Postal Authority lists all PLACI results for postal items
\nProcess Flow: Query PLACI results for postal authority
\nActors: Postal Authority, ACS
\nAuthentication: OAuth 2.0 JWT Bearer token (Postal Authority role)
\nQuery Parameters:
\nRequirement Reference: CM.I2P.6, Integration Point IN-CM.I2P.6-2
\nUse Case: Postal Authority transmits additional information or do not load status to Consignor
\nDescription: ACS enables Postal Authority to communicate status digitally to Consignor
\nProcess Flow: I2P → I3CGNR
\nActors: Postal Authority, Consignor, ACS, Customs
\nBusiness Context: When Customs issues ADDITIONAL_INFORMATION decision for postal item, Postal Authority contacts sender (consignor) in origin country to request missing information. This is typically handled through UPU channels for international postal communications.
\nStandards: UPU (Universal Postal Union) standards
\nAuthentication: OAuth 2.0 JWT Bearer token (Postal Authority role required)
\nValidation Rules:
\nplaciResponseId must reference valid postal PLACI response
\nresponseDeadline must be reasonable for international postal communication
\nAll mandatory fields must be specified
\nInternational Coordination:
\nRequest may be forwarded to origin country postal authority
\nResponse time depends on international postal cooperation
\nLanguage translation may be required
\nRequirement Reference: CM.I2P.6, Integration Point IN-CM.I2P.6-2
\nUse Case: Consignor provides additional information to Postal Authority in response to request
\nDescription: ACS enables Postal Authority to communicate status digitally to Consignor (response collection)
\nProcess Flow: I3CGNR → I2P → I2CUS (forwarded to Customs)
\nActors: Consignor, Postal Authority, ACS, Customs
\nBusiness Context: Consignor (sender) in origin country provides requested information through origin country postal authority. Once received:
\nPakistan Postal Authority receives response
\nPostal Authority reviews for completeness
\nPostal Authority forwards to Customs for re-evaluation
\nCustoms updates PLACI decision
\nSender and recipient notified of outcome
\nInternational Workflow:
\nInformation typically submitted through origin country postal system
\nOrigin postal authority forwards to Pakistan Post via UPU channels
\nDigital documents uploaded to ACS platform
\nVerification may involve origin country postal authority
\nStandards: UPU standards for international postal communications
\nAuthentication: OAuth 2.0 JWT Bearer token (Consignor or Postal Authority role)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","postal-placi-additional-info-responses"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"6c4498bf-6236-4a9b-bd1e-357c69c84c47","name":"Success - Postal Info Response Received","originalRequest":{"method":"POST","header":[{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerOAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Unique request identifier
\n","key":"X-Request-ID","value":"662293b0-71bc-451e-93a4-6cc61a0d2806"}],"body":{"mode":"raw","raw":"{\n \"flightNumber\": \"EK-612\",\n \"flightDate\": \"2025-11-24\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"aircraftType\": \"B777-300ER\",\n \"aircraftRegistration\": \"A6-EBY\",\n \"departureTime\": \"2025-11-24T03:40:00Z\",\n \"arrivalTime\": \"2025-11-24T07:30:00Z\",\n \"airlinePrefix\": \"176\",\n \"airlineCode\": \"EK\",\n \"manifestType\": \"STANDARD\",\n \"totalPieces\": 450,\n \"totalWeight\": 18500,\n \"weightUnit\": \"kg\",\n \"manifestStatus\": \"FINAL\",\n \"mawbs\": [\n {\n \"mawbNumber\": \"176-12345678\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 100,\n \"weight\": 4500,\n \"weightUnit\": \"kg\",\n \"natureOfGoods\": \"General Cargo\",\n \"specialHandlingCodes\": [\"EAT\"],\n \"hawbs\": [\n {\n \"hawbNumber\": \"DXBACA00012345\",\n \"shipperName\": \"Dubai Electronics Trading LLC\",\n \"shipperAddress\": \"Sheikh Zayed Road, Dubai, UAE\",\n \"consigneeName\": \"Karachi Importers Pvt Ltd\",\n \"consigneeAddress\": \"I.I. Chundrigar Road, Karachi, Pakistan\",\n \"pieces\": 50,\n \"weight\": 2250,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Consumer Electronics\",\n \"hsCode\": \"8517.12\",\n \"valueForCarriage\": 45000,\n \"valueForCustoms\": 45000,\n \"currency\": \"USD\"\n },\n {\n \"hawbNumber\": \"DXBACA00012346\",\n \"shipperName\": \"Gulf Trading Company\",\n \"shipperAddress\": \"Deira, Dubai, UAE\",\n \"consigneeName\": \"Pakistan Retail Group\",\n \"consigneeAddress\": \"Tariq Road, Karachi, Pakistan\",\n \"pieces\": 50,\n \"weight\": 2250,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Textile Products\",\n \"hsCode\": \"6204.62\",\n \"valueForCarriage\": 22500,\n \"valueForCustoms\": 22500,\n \"currency\": \"USD\"\n }\n ]\n },\n {\n \"mawbNumber\": \"176-12345679\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 75,\n \"weight\": 3000,\n \"weightUnit\": \"kg\",\n \"natureOfGoods\": \"Express Parcels\",\n \"specialHandlingCodes\": [\"XPS\"],\n \"expressCargo\": true,\n \"hawbs\": [\n {\n \"hawbNumber\": \"PKEPO00012345\",\n \"shipperName\": \"Global Express Shippers\",\n \"shipperAddress\": \"Business Bay, Dubai, UAE\",\n \"consigneeName\": \"Ali Ahmed\",\n \"consigneeAddress\": \"DHA Phase 5, Karachi, Pakistan\",\n \"pieces\": 25,\n \"weight\": 1000,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Documents and Small Parcels\",\n \"hsCode\": \"4901.99\",\n \"valueForCarriage\": 5000,\n \"valueForCustoms\": 5000,\n \"currency\": \"USD\"\n }\n ]\n }\n ],\n \"cargoBreakdown\": [\n {\n \"destination\": \"KHI\",\n \"pieces\": 450,\n \"weight\": 18500,\n \"weightUnit\": \"kg\"\n }\n ],\n \"statistics\": {\n \"totalFlights\": 1,\n \"totalMawbs\": 2,\n \"totalHawbs\": 3,\n \"totalGeneralCargo\": 4500,\n \"totalExpressCargo\": 3000,\n \"totalPieces\": 450,\n \"totalWeight\": 18500,\n \"weightUnit\": \"kg\"\n },\n \"remarks\": \"Flight departed on schedule. All cargo loaded and secured.\"\n}"},"url":"https://api.psw.gov.pk/api/v1/import/flight-manifests","description":"Airline submits import flight manifest with MAWB and HAWB data in JSON format at flight departure from origin.
\nRequirement Reference: CM.I4AL.7
\nUse Case: Airline sends Flight Manifest, MAWB and HAWB data at flight departure from Destination
\nProcess Flow: I2AL → I4AL
\nActors: Airline
\nAuthentication: OAuth 2.0 - Airline role required
\nBusiness Rules:
\nManifest must be submitted at or after flight departure from origin
\nFlight must exist in the system
\nAll AWBs referenced must exist
\nCargo breakdown must match total pieces/weight
\nDestination must be Pakistan airport (KHI, LHE, ISB, etc.)
\nDistribution: After submission, manifest can be pushed to GHA, ACA, Consignee, Postal, PSW, and PAA
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"protocol":"https","path":["api","v1","import","flight-manifests"],"host":["api","psw","gov","pk"],"query":[],"variable":[]}},"response":[{"id":"9c2f5105-ce70-4cc9-9016-d2ede8c427a3","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"OAuth 2.0 JWT token","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Unique request identifier","key":"X-Request-ID","value":"842c2b15-2610-41dc-9479-83f917d02025"}],"body":{"mode":"raw","raw":"{\n \"flightNumber\": \"EK-612\",\n \"flightDate\": \"2025-11-24\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"aircraftType\": \"B777-300ER\",\n \"aircraftRegistration\": \"A6-EBY\",\n \"departureTime\": \"2025-11-24T03:40:00Z\",\n \"arrivalTime\": \"2025-11-24T07:30:00Z\",\n \"airlinePrefix\": \"176\",\n \"airlineCode\": \"EK\",\n \"manifestType\": \"STANDARD\",\n \"totalPieces\": 450,\n \"totalWeight\": 18500,\n \"weightUnit\": \"kg\",\n \"manifestStatus\": \"FINAL\",\n \"mawbs\": [\n {\n \"mawbNumber\": \"176-12345678\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 100,\n \"weight\": 4500,\n \"weightUnit\": \"kg\",\n \"natureOfGoods\": \"General Cargo\",\n \"specialHandlingCodes\": [\"EAT\"],\n \"hawbs\": [\n {\n \"hawbNumber\": \"DXBACA00012345\",\n \"shipperName\": \"Dubai Electronics Trading LLC\",\n \"shipperAddress\": \"Sheikh Zayed Road, Dubai, UAE\",\n \"consigneeName\": \"Karachi Importers Pvt Ltd\",\n \"consigneeAddress\": \"I.I. Chundrigar Road, Karachi, Pakistan\",\n \"pieces\": 50,\n \"weight\": 2250,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Consumer Electronics\",\n \"hsCode\": \"8517.12\",\n \"valueForCarriage\": 45000,\n \"valueForCustoms\": 45000,\n \"currency\": \"USD\"\n },\n {\n \"hawbNumber\": \"DXBACA00012346\",\n \"shipperName\": \"Gulf Trading Company\",\n \"shipperAddress\": \"Deira, Dubai, UAE\",\n \"consigneeName\": \"Pakistan Retail Group\",\n \"consigneeAddress\": \"Tariq Road, Karachi, Pakistan\",\n \"pieces\": 50,\n \"weight\": 2250,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Textile Products\",\n \"hsCode\": \"6204.62\",\n \"valueForCarriage\": 22500,\n \"valueForCustoms\": 22500,\n \"currency\": \"USD\"\n }\n ]\n },\n {\n \"mawbNumber\": \"176-12345679\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 75,\n \"weight\": 3000,\n \"weightUnit\": \"kg\",\n \"natureOfGoods\": \"Express Parcels\",\n \"specialHandlingCodes\": [\"XPS\"],\n \"expressCargo\": true,\n \"hawbs\": [\n {\n \"hawbNumber\": \"PKEPO00012345\",\n \"shipperName\": \"Global Express Shippers\",\n \"shipperAddress\": \"Business Bay, Dubai, UAE\",\n \"consigneeName\": \"Ali Ahmed\",\n \"consigneeAddress\": \"DHA Phase 5, Karachi, Pakistan\",\n \"pieces\": 25,\n \"weight\": 1000,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Documents and Small Parcels\",\n \"hsCode\": \"4901.99\",\n \"valueForCarriage\": 5000,\n \"valueForCustoms\": 5000,\n \"currency\": \"USD\"\n }\n ]\n }\n ],\n \"cargoBreakdown\": [\n {\n \"destination\": \"KHI\",\n \"pieces\": 450,\n \"weight\": 18500,\n \"weightUnit\": \"kg\"\n }\n ],\n \"statistics\": {\n \"totalFlights\": 1,\n \"totalMawbs\": 2,\n \"totalHawbs\": 3,\n \"totalGeneralCargo\": 4500,\n \"totalExpressCargo\": 3000,\n \"totalPieces\": 450,\n \"totalWeight\": 18500,\n \"weightUnit\": \"kg\"\n },\n \"remarks\": \"Flight departed on schedule. All cargo loaded and secured.\"\n}"},"url":"https://api.psw.gov.pk/api/v1/import/flight-manifests","description":"Airline submits import flight manifest with MAWB and HAWB data in JSON format at flight departure from origin.\n\n**Requirement Reference**: CM.I4AL.7\n\n**Use Case**: Airline sends Flight Manifest, MAWB and HAWB data at flight departure from Destination\n\n**Process Flow**: I2AL → I4AL\n\n**Actors**: Airline\n\n**Authentication**: OAuth 2.0 - Airline role required\n\n**Business Rules**:\n\n- Manifest must be submitted at or after flight departure from origin\n \n- Flight must exist in the system\n \n- All AWBs referenced must exist\n \n- Cargo breakdown must match total pieces/weight\n \n- Destination must be Pakistan airport (KHI, LHE, ISB, etc.)\n \n\n**Distribution**: After submission, manifest can be pushed to GHA, ACA, Consignee, Postal, PSW, and PAA"},"status":"Created","code":201,"_postman_previewlanguage":"Text","header":[{"key":"Content-Type","value":"application/json"},{"key":"Location","value":"/api/v1/import/flight-manifests/fm-a1b2c3d4"}],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"fm-a1b2c3d4\",\n \"manifestNumber\": \"EK612-20251124-001\",\n \"flightNumber\": \"EK-612\",\n \"flightDate\": \"2025-11-24\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"status\": \"RECEIVED\",\n \"totalPieces\": 450,\n \"totalWeight\": 18500,\n \"weightUnit\": \"kg\",\n \"totalMawbs\": 2,\n \"totalHawbs\": 3,\n \"distributionStatus\": {\n \"gha\": \"PENDING\",\n \"aca\": \"PENDING\",\n \"consignee\": \"PENDING\",\n \"postal\": \"PENDING\",\n \"psw\": \"PENDING\",\n \"paa\": \"PENDING\"\n },\n \"submittedBy\": \"user-airline-ek-001\",\n \"submittedAt\": \"2025-11-24T03:45:00Z\",\n \"createdAt\": \"2025-11-24T03:45:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-24T03:45:00Z\",\n \"requestId\": \"req-123456\"\n }\n}"},{"id":"99b18927-7571-408e-8ab1-8c58175bda1a","name":"Validation Error","originalRequest":{"method":"POST","header":[{"description":"OAuth 2.0 JWT token","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Unique request identifier","key":"X-Request-ID","value":"ec24d3ad-48fb-4e44-9bdc-63880c889d27"}],"body":{"mode":"raw","raw":"{\n \"flightNumber\": \"EK-612\",\n \"flightDate\": \"2025-11-24\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"aircraftType\": \"B777-300ER\",\n \"aircraftRegistration\": \"A6-EBY\",\n \"departureTime\": \"2025-11-24T03:40:00Z\",\n \"arrivalTime\": \"2025-11-24T07:30:00Z\",\n \"airlinePrefix\": \"176\",\n \"airlineCode\": \"EK\",\n \"manifestType\": \"STANDARD\",\n \"totalPieces\": 450,\n \"totalWeight\": 18500,\n \"weightUnit\": \"kg\",\n \"manifestStatus\": \"FINAL\",\n \"mawbs\": [\n {\n \"mawbNumber\": \"176-12345678\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 100,\n \"weight\": 4500,\n \"weightUnit\": \"kg\",\n \"natureOfGoods\": \"General Cargo\",\n \"specialHandlingCodes\": [\"EAT\"],\n \"hawbs\": [\n {\n \"hawbNumber\": \"DXBACA00012345\",\n \"shipperName\": \"Dubai Electronics Trading LLC\",\n \"shipperAddress\": \"Sheikh Zayed Road, Dubai, UAE\",\n \"consigneeName\": \"Karachi Importers Pvt Ltd\",\n \"consigneeAddress\": \"I.I. Chundrigar Road, Karachi, Pakistan\",\n \"pieces\": 50,\n \"weight\": 2250,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Consumer Electronics\",\n \"hsCode\": \"8517.12\",\n \"valueForCarriage\": 45000,\n \"valueForCustoms\": 45000,\n \"currency\": \"USD\"\n },\n {\n \"hawbNumber\": \"DXBACA00012346\",\n \"shipperName\": \"Gulf Trading Company\",\n \"shipperAddress\": \"Deira, Dubai, UAE\",\n \"consigneeName\": \"Pakistan Retail Group\",\n \"consigneeAddress\": \"Tariq Road, Karachi, Pakistan\",\n \"pieces\": 50,\n \"weight\": 2250,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Textile Products\",\n \"hsCode\": \"6204.62\",\n \"valueForCarriage\": 22500,\n \"valueForCustoms\": 22500,\n \"currency\": \"USD\"\n }\n ]\n },\n {\n \"mawbNumber\": \"176-12345679\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 75,\n \"weight\": 3000,\n \"weightUnit\": \"kg\",\n \"natureOfGoods\": \"Express Parcels\",\n \"specialHandlingCodes\": [\"XPS\"],\n \"expressCargo\": true,\n \"hawbs\": [\n {\n \"hawbNumber\": \"PKEPO00012345\",\n \"shipperName\": \"Global Express Shippers\",\n \"shipperAddress\": \"Business Bay, Dubai, UAE\",\n \"consigneeName\": \"Ali Ahmed\",\n \"consigneeAddress\": \"DHA Phase 5, Karachi, Pakistan\",\n \"pieces\": 25,\n \"weight\": 1000,\n \"weightUnit\": \"kg\",\n \"commodity\": \"Documents and Small Parcels\",\n \"hsCode\": \"4901.99\",\n \"valueForCarriage\": 5000,\n \"valueForCustoms\": 5000,\n \"currency\": \"USD\"\n }\n ]\n }\n ],\n \"cargoBreakdown\": [\n {\n \"destination\": \"KHI\",\n \"pieces\": 450,\n \"weight\": 18500,\n \"weightUnit\": \"kg\"\n }\n ],\n \"statistics\": {\n \"totalFlights\": 1,\n \"totalMawbs\": 2,\n \"totalHawbs\": 3,\n \"totalGeneralCargo\": 4500,\n \"totalExpressCargo\": 3000,\n \"totalPieces\": 450,\n \"totalWeight\": 18500,\n \"weightUnit\": \"kg\"\n },\n \"remarks\": \"Flight departed on schedule. All cargo loaded and secured.\"\n}"},"url":"https://api.psw.gov.pk/api/v1/import/flight-manifests","description":"Airline submits import flight manifest with MAWB and HAWB data in JSON format at flight departure from origin.\n\n**Requirement Reference**: CM.I4AL.7\n\n**Use Case**: Airline sends Flight Manifest, MAWB and HAWB data at flight departure from Destination\n\n**Process Flow**: I2AL → I4AL\n\n**Actors**: Airline\n\n**Authentication**: OAuth 2.0 - Airline role required\n\n**Business Rules**:\n\n- Manifest must be submitted at or after flight departure from origin\n \n- Flight must exist in the system\n \n- All AWBs referenced must exist\n \n- Cargo breakdown must match total pieces/weight\n \n- Destination must be Pakistan airport (KHI, LHE, ISB, etc.)\n \n\n**Distribution**: After submission, manifest can be pushed to GHA, ACA, Consignee, Postal, PSW, and PAA"},"status":"Unprocessable Entity","code":422,"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":"{\n \"success\": false,\n \"error\": {\n \"code\": \"VALIDATION_ERROR\",\n \"message\": \"Flight manifest validation failed\",\n \"details\": [\n {\n \"field\": \"cargoBreakdown[0].weight\",\n \"issue\": \"Cargo breakdown weight (18000 kg) does not match total MAWB weight (18500 kg)\"\n },\n {\n \"field\": \"mawbs[0].hawbs[0].weight\",\n \"issue\": \"HAWB weights do not sum to MAWB weight\"\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-24T03:45:00Z\",\n \"requestId\": \"req-123456\"\n }\n}"}],"_postman_id":"81ad5a8a-1cef-4a9a-b3fb-ad2fa5ebde58"},{"name":"Submit Flight Manifest (XFFM XML)","id":"63f85d60-0802-4f1d-9144-e9ede9be6f3d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Unique request identifier
\n","key":"X-Request-ID","value":"9c64e308-062a-4d2e-8a02-022b53d03056"},{"key":"Content-Type","value":"application/xml"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/xffm","description":"Airline submits import flight manifest in IATA Cargo-XML XFFM format. This is the industry-standard XML format for flight manifests.
\nRequirement Reference: CM.I4AL.7
\nUse Case: Airline sends Flight Manifest in XFFM format
\nProcess Flow: I2AL → I4AL
\nActors: Airline
\nAuthentication: OAuth 2.0 - Airline role required
\nMessage Format: IATA Cargo-XML XFFM (Flight Manifest Message)
\nIATA Standard: XFFM message includes flight details, MAWB/HAWB data, and cargo breakdown.
\nBusiness Rules:
\nMust conform to IATA Cargo-XML XFFM schema
\nFlight departure must be from international origin to Pakistan
\nAll referenced AWBs must have valid formats
\nManifest data extracted and stored in ACS database
\nUnique request identifier
\n","key":"X-Request-ID","value":"7caccd36-b6f5-4c70-9638-baa50b319004"},{"key":"Content-Type","value":"text/plain"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/ffm","description":"Airline submits import flight manifest in IATA Cargo-IMP FFM format. This is the legacy text-based format still widely used in air cargo industry.
\nRequirement Reference: CM.I4AL.7
\nUse Case: Airline sends Flight Manifest in FFM format
\nProcess Flow: I2AL → I4AL
\nActors: Airline
\nAuthentication: OAuth 2.0 - Airline role required
\nMessage Format: IATA Cargo-IMP FFM (Flight Manifest Message)
\nIATA Standard: FFM message uses fixed-width text format with specific line prefixes (FFM, AWB, ORG, DST, etc.).
\nBusiness Rules:
\nMust conform to IATA Cargo-IMP FFM format specification
\nMessage parsed line-by-line according to IMP standard
\nAll AWB numbers extracted and validated
\nLegacy format support for older airline systems
\nOAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests?flightNumber=EK-612&flightDate=2025-11-24&origin=DXB&destination=KHI&status=RECEIVED&airlineCode=EK&dateFrom=2025-11-01&dateTo=2025-11-30&page=1&limit=20&sort=-submittedAt","description":"List flight manifests with filtering, pagination, and sorting.
\nRequirement Reference: CM.I4AL.7
\nUse Case: List flight manifests
\nActors: Airline, GHA, ACA, Consignee, Postal, PSW, PAA
\nAuthentication: OAuth 2.0 - Role-based access
\nFilter Options:
\nflightNumber: Filter by flight number (e.g., EK-612)
\nflightDate: Filter by flight date (YYYY-MM-DD)
\norigin: Filter by origin airport code
\ndestination: Filter by destination airport code
\nstatus: Filter by manifest status
\nairlineCode: Filter by airline code
\ndateFrom/dateTo: Filter by date range
\nSorting Options:
\nsubmittedAt: Sort by submission time
\nflightDate: Sort by flight date
\nflightNumber: Sort by flight number
\nFilter by flight number
\n","type":"text/plain"},"key":"flightNumber","value":"EK-612"},{"description":{"content":"Filter by flight date (YYYY-MM-DD)
\n","type":"text/plain"},"key":"flightDate","value":"2025-11-24"},{"description":{"content":"Filter by origin airport
\n","type":"text/plain"},"key":"origin","value":"DXB"},{"description":{"content":"Filter by destination airport
\n","type":"text/plain"},"key":"destination","value":"KHI"},{"description":{"content":"Filter by status (RECEIVED, DISTRIBUTED, PARTIAL)
\n","type":"text/plain"},"key":"status","value":"RECEIVED"},{"description":{"content":"Filter by airline code
\n","type":"text/plain"},"key":"airlineCode","value":"EK"},{"description":{"content":"Filter by submission date range (from)
\n","type":"text/plain"},"key":"dateFrom","value":"2025-11-01"},{"description":{"content":"Filter by submission date range (to)
\n","type":"text/plain"},"key":"dateTo","value":"2025-11-30"},{"description":{"content":"Page number (default: 1)
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (default: 20, max: 100)
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort by field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-submittedAt"}],"variable":[]}},"response":[{"id":"c9271e0e-7574-497d-8f13-3fb41810220a","name":"Success Response","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerUnique request identifier
\n","key":"X-Request-ID","value":"b46f0144-86ea-4cde-b182-af251d666ffe"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/gha","description":"Push flight manifest data to Ground Handling Agent (GHA) for import cargo handling preparation.
\nRequirement Reference: CM.I4AL.7
\nUse Case: ACS enables Airline to digitally send Flight Manifest to GHA
\nProcess Flow: I4AL → I4GHA
\nActors: Airline (sender), GHA (receiver)
\nAuthentication: OAuth 2.0 - Airline role required
\nACS Middleware Pattern: ACS acts as hub - Airline → ACS → GHA
\nBusiness Rules:
\nManifest must be in RECEIVED or DISTRIBUTED status
\nGHA must be assigned to handle the flight
\nPush creates notification for GHA
\nGHA receives all MAWB/HAWB data for cargo handling
\nUpdates distribution status to track push completion
\nGHA Use Case: GHA uses manifest to prepare for cargo arrival, allocate warehouse space, and plan unloading operations.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"Flight manifest ID
\n","type":"text/plain"},"type":"any","value":"fm-a1b2c3d4","key":"id"}]}},"response":[{"id":"46380f6d-68a5-4364-ab9a-d99edd16c31b","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Unique request identifier","key":"X-Request-ID","value":"289b1005-46fd-4e73-93a0-452594514c0f"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerOAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/aca","description":"Push flight manifest data to Air Cargo Agents (ACAs) who have cargo on the flight.
\nRequirement Reference: CM.I4AL.7
\nUse Case: ACS enables Airline to digitally send Flight Manifest to ACA
\nProcess Flow: I4AL → I5ACA
\nActors: Airline (sender), ACA (receiver)
\nAuthentication: OAuth 2.0 - Airline role required
\nACS Middleware Pattern: ACS acts as hub - Airline → ACS → ACA
\nBusiness Rules:
\nACS identifies all ACAs with cargo on the manifest
\nOnly MAWBs/HAWBs belonging to each ACA are included in their notification
\nMulti-ACA push: If multiple ACAs have cargo, each receives filtered data
\nUpdates distribution status per ACA
\nACA Use Case: ACAs use manifest to prepare for customs clearance, notify consignees, and arrange delivery.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","aca"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"Flight manifest ID
\n","type":"text/plain"},"type":"any","value":"fm-a1b2c3d4","key":"id"}]}},"response":[{"id":"f61112ca-22b5-4960-9160-a08dbdfc0ec9","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerOAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/consignor","description":"Push flight manifest data to Consignors who have cargo arriving on the flight.
\nRequirement Reference: CM.I4AL.7
\nUse Case: ACS enables Airline to digitally send Flight Manifest to Consignor
\nProcess Flow: I4AL → I5CGNR
\nActors: Airline (sender), Consignor (receiver)
\nAuthentication: OAuth 2.0 - Airline role required
\nACS Middleware Pattern: ACS acts as hub - Airline → ACS → Consignor
\nBusiness Rules:
\nACS identifies all consignees based on HAWB consignor names
\nEach consignor receives only their cargo information
\nNotification includes flight arrival details and cargo description
\nConsignor can track cargo arrival in real-time
\nConsignor Use Case: Consignors use manifest to prepare for cargo pickup, arrange customs clearance, and plan warehouse space.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","consignor"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"Flight manifest ID
\n","type":"text/plain"},"type":"any","value":"fm-a1b2c3d4","key":"id"}]}},"response":[{"id":"e3161afc-f2fd-443b-b4a5-66fa39eb1bb4","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerOAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/postal","description":"Push flight manifest data to Postal Authority (Pakistan Post) for mail and express cargo.
\nRequirement Reference: CM.I4AL.7
\nUse Case: ACS enables Airline to digitally send Flight Manifest to Postal Authority
\nProcess Flow: I4AL → I4P
\nActors: Airline (sender), Postal Authority (receiver)
\nAuthentication: OAuth 2.0 - Airline role required
\nACS Middleware Pattern: ACS acts as hub - Airline → ACS → Postal
\nBusiness Rules:
\nOnly postal/express cargo (SHC: XPS, MAL) is included
\nPostal authority receives manifest for mail items and express parcels
\nEnables postal customs clearance and delivery processing
\nEPO cargo also routed to postal authority
\nPostal Use Case: Postal authority uses manifest for mail sorting, customs clearance, and domestic delivery routing.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","postal"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"description":{"content":"Flight manifest ID
\n","type":"text/plain"},"type":"any","value":"fm-a1b2c3d4","key":"id"}]}},"response":[{"id":"6f754788-f465-4cc8-8643-d6a7e109a3a0","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerOAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/psw","description":"Push flight manifest data to Pakistan Single Window (PSW) for statistical and analytical purposes.
\nRequirement Reference: CM.I5PSW.8
\nUse Case: PSW receives Flight Manifest (FFM) message for statistical purposes
\nProcess Flow: I4AL → I5PSW
\nActors: Airline (sender), PSW (receiver)
\nAuthentication: OAuth 2.0 - Airline role required
\nACS Middleware Pattern: ACS acts as hub - Airline → ACS → PSW
\nBusiness Rules:
\nPSW receives aggregated statistics, not detailed cargo data
\nUsed for trade statistics, volume analysis, and planning
\nNo personally identifiable information (PII) included
\nStatistics include: flights, pieces, weight, origins, cargo types
\nPSW Use Case: PSW uses manifest statistics for:
\nImport trade volume tracking
\nRoute analysis and planning
\nCargo type distribution
\nAirport performance metrics
\nEconomic indicators
\nFlight manifest ID
\n","type":"text/plain"},"type":"any","value":"fm-a1b2c3d4","key":"id"}]}},"response":[{"id":"c2884b98-3b7b-41ca-8916-c582b285babe","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerOAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/paa","description":"Push flight manifest data to Pakistan Airport Authority (PAA) for airport operations statistics and planning.
\nRequirement Reference: CM.I5PAA.9
\nUse Case: PAA receives Flight Manifest (FFM) message for statistical purposes
\nProcess Flow: I4AL → I5PAA
\nActors: Airline (sender), PAA (receiver)
\nAuthentication: OAuth 2.0 - Airline role required
\nACS Middleware Pattern: ACS acts as hub - Airline → ACS → PAA
\nBusiness Rules:
\nPAA receives flight and cargo statistics for airport planning
\nUsed for infrastructure planning, capacity management
\nStatistics by airport, airline, route, and cargo type
\nNo cargo details or consignee information
\nPAA Use Case: PAA uses manifest statistics for:
\nAirport cargo volume tracking
\nWarehouse capacity planning
\nGround handling resource allocation
\nFlight schedule analysis
\nAirport performance reporting
\nInfrastructure investment planning
\nFlight manifest ID
\n","type":"text/plain"},"type":"any","value":"fm-a1b2c3d4","key":"id"}]}},"response":[{"id":"e094e9be-2d23-47f2-8b8f-67bccba1cd9b","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerOAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Accept","value":"application/json"}],"url":"https://api.psw.gov.pk/api/v1/import/statistics/psw?dateFrom=2025-11-01&dateTo=2025-11-30&origin=DXB&destination=KHI&airlineCode=EK&aggregateBy=DAY&page=1&limit=50","description":"PSW retrieves aggregated flight manifest statistics for trade monitoring, volume analysis, and planning.
\nRequirement Reference: CM.I5PSW.8
\nUse Case: PSW receives Flight Manifest (FFM) message for statistical purposes
\nProcess Flow: I4AL → I5PSW (receiving flight manifest data)
\nActors: PSW
\nAuthentication: OAuth 2.0 - PSW role required
\nStatistics Included:
\nTotal flights by date/route/airline
\nTotal cargo volume (pieces and weight)
\nBreakdown by cargo type (general, express, postal)
\nOrigin-destination pairs
\nMAWB/HAWB counts
\nTime-series trends
\nUse Cases:
\nImport trade volume monitoring
\nRoute performance analysis
\nCargo type distribution
\nEconomic indicators
\nPolicy planning and decision-making
\nStart date for statistics (YYYY-MM-DD)
\n","type":"text/plain"},"key":"dateFrom","value":"2025-11-01"},{"description":{"content":"End date for statistics (YYYY-MM-DD)
\n","type":"text/plain"},"key":"dateTo","value":"2025-11-30"},{"description":{"content":"Filter by origin airport (optional)
\n","type":"text/plain"},"key":"origin","value":"DXB"},{"description":{"content":"Filter by destination airport (optional)
\n","type":"text/plain"},"key":"destination","value":"KHI"},{"description":{"content":"Filter by airline code (optional)
\n","type":"text/plain"},"key":"airlineCode","value":"EK"},{"description":{"content":"Aggregation level: DAY, WEEK, MONTH, YEAR (optional)
\n","type":"text/plain"},"key":"aggregateBy","value":"DAY"},{"disabled":true,"description":{"content":"Filter by cargo type: GENERAL, EXPRESS, POSTAL (optional)
\n","type":"text/plain"},"key":"cargoType","value":"GENERAL"},{"description":{"content":"Page number (default: 1)
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (default: 50, max: 100)
\n","type":"text/plain"},"key":"limit","value":"50"}],"variable":[]}},"response":[],"_postman_id":"cff90c07-6bc4-4be8-bfe3-0b4e696df1a3"},{"name":"Get PAA Flight Statistics","id":"ef82d23e-075b-4e7a-92ec-8a6bb9f88ba6","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"description":"OAuth 2.0 JWT token
\n","key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Accept","value":"application/json"}],"url":"https://api.psw.gov.pk/api/v1/import/statistics/paa?airportCode=KHI&dateFrom=2025-11-01&dateTo=2025-11-30&origin=DXB&airlineCode=EK&aggregateBy=DAY&includeAircraftTypes=true&page=1&limit=50","description":"PAA retrieves aggregated flight manifest statistics for airport operations planning, capacity management, and infrastructure planning.
\nRequirement Reference: CM.I5PAA.9
\nUse Case: PAA receives Flight Manifest (FFM) message for statistical purposes
\nProcess Flow: I4AL → I5PAA (receiving flight manifest data)
\nActors: PAA
\nAuthentication: OAuth 2.0 - PAA role required
\nStatistics Included:
\nTotal flights by airport/date/airline
\nTotal cargo volume handled
\nAircraft type distribution
\nCargo breakdown by type
\nPeak hours and load factors
\nRoute performance
\nWarehouse utilization metrics
\nUse Cases:
\nAirport cargo volume tracking
\nWarehouse capacity planning
\nGround handling resource allocation
\nFlight schedule analysis
\nPeak period identification
\nInfrastructure investment planning
\nPerformance benchmarking
\nFilter by airport code (KHI, LHE, ISB, etc.)
\n","type":"text/plain"},"key":"airportCode","value":"KHI"},{"description":{"content":"Start date for statistics (YYYY-MM-DD)
\n","type":"text/plain"},"key":"dateFrom","value":"2025-11-01"},{"description":{"content":"End date for statistics (YYYY-MM-DD)
\n","type":"text/plain"},"key":"dateTo","value":"2025-11-30"},{"description":{"content":"Filter by origin airport (optional)
\n","type":"text/plain"},"key":"origin","value":"DXB"},{"description":{"content":"Filter by airline code (optional)
\n","type":"text/plain"},"key":"airlineCode","value":"EK"},{"description":{"content":"Aggregation level: DAY, WEEK, MONTH, YEAR (optional)
\n","type":"text/plain"},"key":"aggregateBy","value":"DAY"},{"description":{"content":"Include aircraft type breakdown (optional)
\n","type":"text/plain"},"key":"includeAircraftTypes","value":"true"},{"disabled":true,"description":{"content":"Filter by cargo type (optional)
\n","type":"text/plain"},"key":"cargoType","value":"GENERAL"},{"description":{"content":"Page number (default: 1)
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (default: 50, max: 100)
\n","type":"text/plain"},"key":"limit","value":"50"}],"variable":[]}},"response":[],"_postman_id":"ef82d23e-075b-4e7a-92ec-8a6bb9f88ba6"}],"id":"ceb18436-57b5-483f-b1f7-02c80d348e29","description":"Endpoints for PSW and PAA to retrieve flight manifest statistics for reporting and planning purposes.
\nRequirements: CM.I5PSW.8, CM.I5PAA.9\nIntegration Points: IN-CM.I5PSW.8-1, IN-CM.I5PAA.9-1\nUse Cases: PSW and PAA receive Flight Manifest data for statistical purposes\nProcess Flow: I4AL → I5PSW, I4AL → I5PAA\nActors: PSW, PAA
\n","_postman_id":"ceb18436-57b5-483f-b1f7-02c80d348e29","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"c6fc0a08-4074-47c7-b5ed-4c605834a26e","_postman_id":"c6fc0a08-4074-47c7-b5ed-4c605834a26e","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"9662108c-85ee-40d3-950d-9bec27c59648","_postman_id":"9662108c-85ee-40d3-950d-9bec27c59648","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"EPO Express Compliance","item":[{"name":"Export - E-CSD Management","item":[{"name":"Submit E-CSD to EPO (JSON)","id":"619450fa-297f-4db5-b72a-13a941467c51","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"key":"X-Request-ID","value":"acf6d592-87ee-48aa-8f48-fd9b7489744b"}],"body":{"mode":"raw","raw":"{\n \"mawbNumber\": \"176-12345678\",\n \"hawbNumber\": \"PKEPO00012345\",\n \"ghaCode\": \"GHAPK001\",\n \"ghaName\": \"Pakistan Ground Handling Services\",\n \"declarationDate\": \"2025-11-24T08:30:00+05:00\",\n \"flightNumber\": \"PK-784\",\n \"flightDate\": \"2025-11-24\",\n \"origin\": \"KHI\",\n \"destination\": \"DXB\",\n \"consignor\": {\n \"name\": \"Express Consignments Ltd\",\n \"address\": \"123 Business Avenue, Karachi\",\n \"country\": \"PK\"\n },\n \"consignee\": {\n \"name\": \"Dubai Trading Co\",\n \"address\": \"456 Trade Street, Dubai\",\n \"country\": \"AE\"\n },\n \"cargo\": {\n \"description\": \"Express Documents and Small Parcels\",\n \"pieces\": 25,\n \"weight\": 45.5,\n \"weightUnit\": \"kg\"\n },\n \"securityScreening\": {\n \"screeningDate\": \"2025-11-24T07:00:00+05:00\",\n \"screeningMethod\": \"X-Ray\",\n \"screenedBy\": \"Ahmad Khan\",\n \"screeningAuthority\": \"ASF Pakistan\",\n \"screeningLocation\": \"Karachi Airport Cargo Terminal\",\n \"screeningResult\": \"Clear\",\n \"screeningLevel\": \"Enhanced\",\n \"dangerousGoodsScreening\": false,\n \"explosiveDetection\": true,\n \"xRayImageReference\": \"XR-KHI-20251124-001\"\n },\n \"securityDeclaration\": {\n \"id\": \"19509971-5f55-47ea-8f24-4899d84e4c80\",\n \"declarantName\": \"Zain Ahmed\",\n \"declarantTitle\": \"Security Manager\",\n \"declarantSignature\": \"data:image/png;base64,iVBORw0KGgo...\",\n \"declaration\": \"I hereby certify that this consignment has been screened in accordance with ICAO Doc 8973 Chapter 13 requirements and is secure for air transport.\",\n \"icaoCompliance\": \"ICAO Doc 8973 Chapter 13\",\n \"regulatoryCompliance\": [\"ASF Regulations\", \"CAA Pakistan\"],\n \"certificateNumber\": \"ECSD-KHI-20251124-001\"\n },\n \"securityStatus\": \"Secure for Carriage\",\n \"specialHandling\": [\"Express\", \"Time Sensitive\"],\n \"additionalRemarks\": \"Pre-cleared for express handling\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.psw.gov.pk/api/v1/epo/export/e-csd-receipts","description":"Requirement Reference: CS.E28EPO.1
\nUse Case: EPO receives E-CSD (Consignment Security Declaration) digitally
\nDescription: ACS enables EPO to receive E-CSD data digitally
\nProcess Flow: E28GHA → E28EPO
\nActors: Ground Handling Agent (GHA), Express Post Office (EPO)
\nAuthentication: OAuth 2.0 JWT token (GHA role required)
\nBusiness Rules:
\nE-CSD certifies that cargo has undergone security screening per ICAO Doc 8973 Chapter 13
\nE-CSD is required for all air cargo shipments
\nScreening must be conducted by authorized personnel at approved facilities
\nSecurity declaration must include screening method, date, location, and result
\nClear screening result required before cargo can be loaded
\nCertificate number must be unique and traceable
\nIATA E-CSD Standard:
\nElectronic format replacing paper security declarations
\nIncludes screening details and certifications
\nDigital signature for authentication
\nCompliance with ICAO Doc 8973 (Aviation Security Manual)
\nEPO Context:
\nExpress shipments require expedited security processing
\nE-CSD enables faster clearance at destination
\nPre-screened status allows immediate release procedures
\nRequirement Reference: CS.E28EPO.1
\nUse Case: EPO receives E-CSD in IATA E-CSD XML format
\nProcess Flow: E28GHA → E28EPO
\nMessage Format: IATA E-CSD XML Standard
\nStandard Reference: IATA e-CSD standards, ICAO Doc 8973 Chapter 13 / Appendix 33
\nAuthentication: OAuth 2.0 JWT token (GHA role required)
\nBusiness Rules:
\nXML must conform to IATA E-CSD schema specification
\nAll mandatory elements per IATA standard must be present
\nSecurity screening details must meet ICAO Doc 8973 requirements
\nCertificate number must be globally unique
\nDigital signature validation (if included) must pass
\nXML Validation:
\nSchema validation against IATA E-CSD XSD
\nScreening date must be before or on flight date
\nScreening result must be 'Clear' for acceptance
\nSecurity authority must be recognized/approved
\nIndustry Standard:
\nIATA E-CSD enables paperless security certification
\nGlobally recognized format for cross-border shipments
\nSupports automated risk assessment at destination
\nReduces delays from missing/invalid paper declarations
\nRequirement Reference: CS.E28EPO.1
\nUse Case: EPO lists all received E-CSD receipts with filtering
\nAuthentication: OAuth 2.0 JWT token (EPO role required)
\nQuery Parameters:
\nstatus - Receipt status (Received, Processed, etc.)
flightDate - Filter by flight date
flightNumber - Filter by flight number
awbNumber - Filter by AWB number
securityStatus - Filter by security status
page - Page number (default: 1)
limit - Items per page (default: 20, max: 100)
sort - Sort field (use - prefix for descending)
Business Rules:
\nEPO sees only E-CSDs for their shipments
\nDefault sort: most recently received first
\nPagination required for large result sets
\nFilter by receipt status
\n","type":"text/plain"},"key":"status","value":"Received"},{"description":{"content":"Filter by flight date (YYYY-MM-DD)
\n","type":"text/plain"},"key":"flightDate","value":"2025-11-24"},{"description":{"content":"Filter by flight number
\n","type":"text/plain"},"key":"flightNumber","value":"PK-784"},{"description":{"content":"Filter by AWB number
\n","type":"text/plain"},"key":"awbNumber","value":"176-12345678"},{"description":{"content":"Filter by security status
\n","type":"text/plain"},"key":"securityStatus","value":"Secure for Carriage"},{"description":{"content":"Page number
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (max 100)
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort by field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-receivedAt"}],"variable":[]}},"response":[{"id":"306b9296-a58d-41f2-9363-de20da22dad9","name":"Success - E-CSD List","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CS.I1EPO.1
\nUse Case: EPO sends PLACI data digitally 4 hours before flight departure
\nDescription: ACS enables Customs to receive PLACI data digitally
\nProcess Flow: I1EPO → I1CUS
\nActors: Express Post Office (EPO), Customs (WeBOC)
\nAuthentication: OAuth 2.0 JWT token (EPO role required)
\nCritical Business Rule: EPO must submit PLACI data 4 hours before flight departure
\nWCO PLACI Mandatory Fields:
\nConsignor name
\nConsignor address
\nConsignee name
\nConsignee address
\nNumber of packages
\nTotal gross weight (including unit)
\nBrief cargo description
\nData filer identification (provided with HAWB/MAWB)
\nEPO-Specific Requirements:
\nService level and delivery commitments
\nPre-clearance flag for WCO Immediate Release eligibility
\nValue declaration for customs assessment
\nExpress operator certification details
\nBusiness Rules:
\nSubmission must be at least 4 hours before flight departure
\nLate submissions will be rejected with specific error code
\nPre-clearance can be requested for eligible low-risk shipments
\nSimplified GD procedures apply for express shipments
\nEPO can submit on behalf of consignee for pre-clearance
\nWCO Immediate Release Guidelines:
\nExpress shipments can qualify for pre-flight customs clearance
\nEnables immediate release upon arrival
\nRequires advance PLACI submission (4-hour rule)
\nSupports expedited delivery commitments
\nReduces dwell time at destination airport
\nRequirement Reference: CS.I1EPO.1
\nUse Case: EPO sends PLACI data in WCO PLACI XML standard format
\nProcess Flow: I1EPO → I1CUS
\nMessage Format: WCO PLACI XML Standard
\nStandard Reference: WCO PLACI Standard
\nAuthentication: OAuth 2.0 JWT token (EPO role required)
\nCritical Business Rule: 4-hour advance submission requirement
\nXML Validation:
\nSchema validation against WCO PLACI XSD
\nAll mandatory WCO PLACI elements must be present
\nSubmission time must be at least 4 hours before departure
\nData filer ID must match EPO registration
\nIndustry Standard:
\nWCO PLACI is globally recognized format
\nEnables automated risk assessment
\nSupports cross-border data exchange
\nFacilitates advance screening before cargo loading
\nExpress Operator Benefits:
\nPre-clearance capability
\nSimplified customs procedures
\nImmediate release upon arrival
\nReduced dwell time
\nEnhanced customer service
\nRequirement Reference: CS.I1EPO.1
\nUse Case: EPO lists all PLACI submissions with filtering
\nAuthentication: OAuth 2.0 JWT token (EPO role required)
\nQuery Parameters:
\nstatus - Submission status
flightDate - Filter by flight date
flightNumber - Filter by flight number
hawbNumber - Filter by HAWB number
riskAssessmentStatus - Filter by risk assessment status
deadlineCompliance - Filter by deadline compliance (Met/Missed)
page - Page number (default: 1)
limit - Items per page (default: 20, max: 100)
sort - Sort field
Business Rules:
\nEPO sees only their own PLACI submissions
\nDefault sort: most recently submitted first
\nDeadline compliance status prominently displayed
\nFilter by submission status
\n","type":"text/plain"},"key":"status","value":"Submitted to Customs"},{"description":{"content":"Filter by flight date (YYYY-MM-DD)
\n","type":"text/plain"},"key":"flightDate","value":"2025-11-24"},{"description":{"content":"Filter by flight number
\n","type":"text/plain"},"key":"flightNumber","value":"EK-602"},{"description":{"content":"Filter by HAWB number
\n","type":"text/plain"},"key":"hawbNumber","value":"PKEPO00012345"},{"description":{"content":"Filter by risk assessment status
\n","type":"text/plain"},"key":"riskAssessmentStatus","value":"Pending"},{"description":{"content":"Filter by deadline compliance (Met/Missed)
\n","type":"text/plain"},"key":"deadlineCompliance","value":"Met"},{"description":{"content":"Page number
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (max 100)
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort by field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-submissionTime"}],"variable":[]}},"response":[{"id":"95160fb5-d320-4c76-9b8c-c35577482b1d","name":"Success - PLACI Submissions List","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CS.I1EPO.1
\nUse Case: ACS pushes EPO PLACI submission to WeBOC for risk analysis
\nDescription: ACS enables Customs to receive PLACI data digitally
\nProcess Flow: I1EPO → I1CUS (via ACS middleware)
\nActors: ACS System, WeBOC (Customs)
\nAuthentication: OAuth 2.0 JWT token (System role required)
\nACS Middleware Pattern:
\nACS acts as central hub for all communications
\nNo direct EPO → WeBOC connection
\nACS ensures message transformation and validation
\nRetry mechanism for failed deliveries
\nAudit trail of all push operations
\nBusiness Rules:
\nAutomatic push immediately after PLACI submission
\nCan be manually triggered if auto-push fails
\nValidates 4-hour deadline before pushing
\nRecords delivery timestamp and confirmation
\nNotifies EPO of successful delivery to Customs
\nDelivery Confirmation:
\nWeBOC acknowledgment required
\nDelivery status tracked in real-time
\nFailed deliveries trigger automatic retry
\nEPO notified of delivery status
\nRequirement Reference: CS.I2CUS.3, CS.I2EPO.4
\nUse Case: Customs communicates PLACI risk analysis results to EPO
\nDescription: ACS enables Customs to digitally send risk analysis results and receive additional info/screening
\nProcess Flow: I1CUS → I2CUS → I2EPO
\nActors: WeBOC (Customs), Express Post Office (EPO)
\nAuthentication: OAuth 2.0 JWT token (Customs/System role required)
\nFour PLACI Decision Types:
\nLoad - Cleared for loading, no additional requirements
\nAdditional Information - Requires more details from consignor
\nAdditional Screening - Requires X-ray or physical inspection
\nDo Not Load - Prohibited from loading, must be returned
\nBusiness Rules:
\nRisk analysis typically completed within 1 hour of submission
\nDecision communicated immediately to EPO
\nPre-clearance can be granted for low-risk shipments
\nSimplified GD procedures apply for express shipments
\nWCO Immediate Release guidelines enable pre-flight clearance
\nPre-Clearance Benefits:
\nCustoms clearance before flight arrival
\nImmediate release upon landing
\nReduced dwell time at airport
\nFaster delivery to consignee
\nEnhanced express service capability
\nEPO Responsibilities:
\nSubmit simplified GD on behalf of consignee (if pre-clearance granted)
\nArrange immediate delivery upon release
\nMaintain compliance with customs requirements
\nReport any discrepancies immediately
\nRequirement Reference: CS.I2EPO.4
\nUse Case: EPO lists all PLACI risk analysis responses with filtering
\nAuthentication: OAuth 2.0 JWT token (EPO role required)
\nQuery Parameters:
\ndecision - PLACI decision (Load, Additional Information, Additional Screening, Do Not Load)
preClearanceApproved - Filter by pre-clearance approval
riskLevel - Filter by risk level (Low, Medium, High)
flightDate - Filter by flight date
hawbNumber - Filter by HAWB number
page - Page number (default: 1)
limit - Items per page (default: 20, max: 100)
sort - Sort field
Business Rules:
\nEPO sees only responses for their submissions
\nDefault sort: most recent responses first
\nDecision type and pre-clearance status prominently displayed
\nFilter by PLACI decision
\n","type":"text/plain"},"key":"decision","value":"Load"},{"description":{"content":"Filter by pre-clearance approval status
\n","type":"text/plain"},"key":"preClearanceApproved","value":"true"},{"description":{"content":"Filter by risk level
\n","type":"text/plain"},"key":"riskLevel","value":"Low"},{"description":{"content":"Filter by flight date
\n","type":"text/plain"},"key":"flightDate","value":"2025-11-24"},{"description":{"content":"Filter by HAWB number
\n","type":"text/plain"},"key":"hawbNumber","value":"PKEPO00012345"},{"description":{"content":"Page number
\n","type":"text/plain"},"key":"page","value":"1"},{"description":{"content":"Items per page (max 100)
\n","type":"text/plain"},"key":"limit","value":"20"},{"description":{"content":"Sort by field (prefix with - for descending)
\n","type":"text/plain"},"key":"sort","value":"-respondedAt"}],"variable":[]}},"response":[{"id":"263e9bd6-ff90-46a6-94b4-f28aa077c54d","name":"Success - Responses List","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CS.I2EPO.4
\nUse Case: EPO requests additional information from Consignor in response to PLACI \"Additional Information\" decision
\nDescription: ACS enables EPO to receive PLACI replies and send additional info
\nProcess Flow: I2EPO → I3CGNR (Additional Information request)
\nActors: Express Post Office (EPO), Consignor
\nAuthentication: OAuth 2.0 JWT token (EPO role required)
\nBusiness Rules:
\nTriggered when PLACI decision is \"Additional Information\"
\nEPO acts as intermediary between Customs and Consignor
\nClear deadline communicated to Consignor
\nMultiple information types can be requested
\nUrgency level reflects time-sensitivity
\nAutomated notifications sent to Consignor
\nWorkflow:
\nCustoms requests additional information via PLACI response
\nEPO creates information request to Consignor
\nConsignor receives notification with deadline
\nConsignor provides information to EPO
\nEPO forwards information to Customs
\nCustoms re-evaluates and issues new decision
\nTime Sensitivity:
\nMust meet flight departure deadline
\nTypical turnaround: 2-6 hours
\nMissed deadline results in Do Not Load
\nExpress handling may be possible for urgent cases
\nRequirement Reference: CS.I2EPO.4
\nUse Case: Consignor provides additional information to EPO in response to PLACI information request
\nProcess Flow: I3CGNR → I2EPO → I2CUS (Information response forwarding)
\nActors: Consignor, Express Post Office (EPO), Customs
\nAuthentication: OAuth 2.0 JWT token (Consignor or EPO role required)
\nBusiness Rules:
\nMust be submitted before deadline
\nAll mandatory information items must be included
\nDocuments must be uploaded and accessible
\nEPO validates completeness before forwarding to Customs
\nCustoms performs re-evaluation upon receipt
\nWorkflow:
\nConsignor uploads documents to PSW portal
\nConsignor/EPO submits information response
\nACS validates document availability
\nEPO reviews for completeness
\nEPO forwards to Customs (WeBOC)
\nCustoms re-evaluates PLACI submission
\nNew risk decision issued
\nDocument Requirements:
\nMust be in PDF or approved image format
\nFile size limits apply (10MB per document)
\nDocument hash for integrity verification
\nOfficial certificates must have verification numbers
\nRequirement Reference: CS.I2EPO.4
\nUse Case: EPO submits additional screening results in response to PLACI \"Additional Screening\" decision
\nDescription: ACS enables EPO to send screening results digitally
\nProcess Flow: I2EPO → I2CUS (Screening results submission)
\nActors: Express Post Office (EPO), Customs
\nAuthentication: OAuth 2.0 JWT token (EPO role required)
\nBusiness Rules:
\nTriggered when PLACI decision is \"Additional Screening\"
\nEPO must conduct enhanced security screening
\nX-ray images required for verification
\nScreening report must be comprehensive
\nResults forwarded to Customs for re-evaluation
\nClear result enables loading authorization
\nScreening Requirements:
\nMust use approved screening equipment
\nConducted by certified screening personnel
\nComply with ICAO Doc 8973 standards
\nMultiple images from different angles
\nDetailed screening report
\nOfficer certification and signature
\nWorkflow:
\nCustoms requests additional screening via PLACI response
\nEPO conducts enhanced X-ray screening
\nEPO captures images and generates report
\nEPO submits results to Customs via ACS
\nCustoms reviews screening results
\nCustoms issues new decision (typically Load or Do Not Load)
\nResult Options:
\nClear: No anomalies, cleared for loading
\nSuspicious: Requires physical inspection
\nProhibited Items Found: Do Not Load decision
\nExpress Context:
\nEPO has certified screening facilities
\nCan perform enhanced screening without external support
\nFaster turnaround than standard cargo screening
\nMaintains chain of custody throughout process
\nUnique request identifier for traceability
\n","key":"X-Request-ID","value":"f0762cb5-747e-42c0-8955-7e8be5bbdb4e"},{"description":"Identifier of the sending/requesting system (e.g., CGNR-{NTN})
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.831Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/digital-trade-lane/consignments","description":"Requirement Reference: CL.I1CGNR.1
\nUse Case: Consignor submits export documents via Digital Trade Lane
\nDescription: ACS enables Consignor to submit consignment documents to ACS via digital trade lane in digital format, enabling direct communication with Airlines and Customs.
\nProcess Flow:
\nConsignor System (Origin Country) → ACS (Air Cargo System) → Airline System
\nConsignor System (Origin Country) → ACS (Air Cargo System) → Customs (WeBOC)
\nPriority: P1
\nKey Activities:
\nSubmit MAWB and HAWB data
\nSubmit Goods Declaration (or Export declaration from origin)
\nSubmit Packing list
\nSubmit Commercial Invoice
\nSubmit Export Certificates and NOCs if applicable
\nBusiness Rules:
\nConsignor must be registered in ACS digital trade lane program
\nAll mandatory documents must be provided
\nDocument data validated against IATA and customs standards
\nTriggers distribution to Airline and Customs upon successful submission
\nSupports both direct and consolidated shipments
\nInput Documents
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","digital-trade-lane","consignments"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"f0ceb20d-4ea8-466c-9adf-4e7f6210c8a8","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Unique request identifier for traceability","key":"X-Request-ID","value":"f0f14034-8d14-4e3e-a2db-edc67fca2a87"},{"description":"Identifier of the sending/requesting system (e.g., CGNR-{NTN})","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.831Z"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I4AL.2
\nUse Case: Airline sends Flight manifest & MAWB + HAWB data at flight departure from Destination
\nIntegration Point: IN-CL.I4AL.2-1 - ACS enables airlines to digitally transmit flight manifest, MAWB, and HAWB data to GHA, Customs, PAA, PSW, ACA, and Consignee.
\nKey Activities: Will enable airlines to send this data to GHA digitally. Will enable Airlines to share MAWB + HAWB data digitally with Consignee and ACA.
\nProcess Flow: I2AL → I4AL → I4GHA/I4CUS/I5PSW/I5PAA/I5ACA/I5CNE
\nActors: Airline (submitter), GHA, Customs, PSW, PAA, ACA, Consignee (receivers)
\nAuthentication: OAuth 2.0 JWT (Airline role required)
\nMessage Format: JSON (REST API standard)
\nResponse: Returns manifest ID and triggers asynchronous distribution to all stakeholders.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"3c762ecb-e74a-489a-a7ff-6eab8c8181c8","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"flightNumber\": \"PK-307\",\n \"departureAirport\": \"DXB\",\n \"arrivalAirport\": \"KHI\",\n \"departureDate\": \"2025-11-28\",\n \"departureTime\": \"14:30:00Z\",\n \"arrivalDate\": \"2025-11-28\",\n \"arrivalTime\": \"19:00:00Z\",\n \"aircraftType\": \"Boeing 777-300ER\",\n \"aircraftRegistration\": \"AP-BHV\",\n \"airlinePrefix\": \"214\",\n \"airlineCode\": \"PK\",\n \"manifestItems\": [\n {\n \"awbNumber\": \"214-12345678\",\n \"origin\": \"DXB\",\n \"destination\": \"KHI\",\n \"pieces\": 10,\n \"weight\": 500.5,\n \"weightUnit\": \"KG\",\n \"volumeWeight\": 450.0,\n \"commodityDescription\": \"Electronics\",\n \"specialHandlingCodes\": [\"GEN\"],\n \"consignorName\": \"ABC Electronics LLC\",\n \"consigneeName\": \"XYZ Imports Pvt Ltd\",\n \"consigneeAddress\": \"123 Main St, Karachi\"\n }\n ],\n \"totalPieces\": 10,\n \"totalWeight\": 500.5,\n \"totalWeightUnit\": \"KG\"\n}"},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests","description":"**Requirement Reference**: CL.I4AL.2\n\n**Use Case**: Airline sends Flight manifest & MAWB + HAWB data at flight departure from Destination\n\n**Integration Point**: IN-CL.I4AL.2-1 - ACS enables airlines to digitally transmit flight manifest, MAWB, and HAWB data to GHA, Customs, PAA, PSW, ACA, and Consignee.\n\n**Key Activities**: Will enable airlines to send this data to GHA digitally. Will enable Airlines to share MAWB + HAWB data digitally with Consignee and ACA.\n\n**Process Flow**: I2AL → I4AL → I4GHA/I4CUS/I5PSW/I5PAA/I5ACA/I5CNE\n\n**Actors**: Airline (submitter), GHA, Customs, PSW, PAA, ACA, Consignee (receivers)\n\n**Authentication**: OAuth 2.0 JWT (Airline role required)\n\n**Message Format**: JSON (REST API standard)\n\n**Response**: Returns manifest ID and triggers asynchronous distribution to all stakeholders."},"status":"Created","code":201,"_postman_previewlanguage":"Text","header":[{"key":"Content-Type","value":"application/json"},{"key":"Location","value":"/api/v1/import/flight-manifests/ffm-20251128-PK307"}],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"ffm-20251128-PK307\",\n \"flightNumber\": \"PK-307\",\n \"departureAirport\": \"DXB\",\n \"arrivalAirport\": \"KHI\",\n \"departureDateTime\": \"2025-11-28T14:30:00Z\",\n \"arrivalDateTime\": \"2025-11-28T19:00:00Z\",\n \"totalPieces\": 10,\n \"totalWeight\": 500.5,\n \"status\": \"RECEIVED\",\n \"distributionStatus\": \"PENDING\",\n \"submittedBy\": \"PK-Airlines\",\n \"submittedAt\": \"2025-11-28T10:00:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T10:00:00Z\",\n \"requestId\": \"req-ffm-001\"\n }\n}"}],"_postman_id":"21ec5fba-1bfa-4f2f-aaf0-4694cffecdb3"},{"name":"Submit Flight Manifest (IATA Cargo-XML)","id":"35a6c657-a9e0-47d5-b2e5-2db13a5a5374","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/xml"}],"body":{"mode":"raw","raw":"\nRequirement Reference: CL.I4AL.2
\nUse Case: Airline sends Flight manifest & MAWB + HAWB data at flight departure from Destination
\nIntegration Point: IN-CL.I4AL.2-1 - ACS enables airlines to digitally transmit flight manifest in IATA Cargo-XML format.
\nKey Activities: Transmitting Flight manifest data in industry-standard XML format.
\nProcess Flow: I2AL → I4AL → I4GHA/I4CUS/I5PSW/I5PAA/I5ACA/I5CNE
\nActors: Airline (submitter)
\nAuthentication: OAuth 2.0 JWT (Airline role required)
\nMessage Format: IATA Cargo-XML (XFFM)
\nStandards: IATA Cargo-XML specification for Flight Manifest
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests","xffm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"8071cbb6-7660-4195-be3c-eca8f3b35e9d","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/xml"}],"body":{"mode":"raw","raw":"\nRequirement Reference: CL.I4AL.2
\nUse Case: Airline sends Flight manifest & MAWB + HAWB data at flight departure from Destination
\nIntegration Point: IN-CL.I4AL.2-1 - ACS enables airlines to digitally transmit flight manifest in IATA Cargo-IMP format.
\nKey Activities: Transmitting Flight manifest data in legacy IMP format.
\nProcess Flow: I2AL → I4AL → I4GHA/I4CUS/I5PSW/I5PAA/I5ACA/I5CNE
\nActors: Airline (submitter)
\nAuthentication: OAuth 2.0 JWT (Airline role required)
\nMessage Format: IATA Cargo-IMP (FFM)
\nStandards: IATA Cargo-IMP specification for Flight Manifest
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests","ffm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"50d91720-d8bf-4e27-9708-a1335b223b46","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"text/plain"}],"body":{"mode":"raw","raw":"FFM\n214-12345678KHIDXB/T500.5K10/SDXBGEN\n1/Electronics\nPK307/28NOV.DXBKHI/D2025112814301900"},"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/ffm","description":"**Requirement Reference**: CL.I4AL.2\n\n**Use Case**: Airline sends Flight manifest & MAWB + HAWB data at flight departure from Destination\n\n**Integration Point**: IN-CL.I4AL.2-1 - ACS enables airlines to digitally transmit flight manifest in IATA Cargo-IMP format.\n\n**Key Activities**: Transmitting Flight manifest data in legacy IMP format.\n\n**Process Flow**: I2AL → I4AL → I4GHA/I4CUS/I5PSW/I5PAA/I5ACA/I5CNE\n\n**Actors**: Airline (submitter)\n\n**Authentication**: OAuth 2.0 JWT (Airline role required)\n\n**Message Format**: IATA Cargo-IMP (FFM)\n\n**Standards**: IATA Cargo-IMP specification for Flight Manifest"},"status":"Created","code":201,"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"id\": \"ffm-20251128-PK307\",\n \"flightNumber\": \"PK-307\",\n \"format\": \"FFM\",\n \"status\": \"RECEIVED\",\n \"distributionStatus\": \"PENDING\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T10:00:00Z\",\n \"requestId\": \"req-ffm-001\"\n }\n}"}],"_postman_id":"14ed2b65-e11a-4f90-ae75-70de3e94eb17"},{"name":"Submit Master Air Waybill (JSON)","id":"0a13f627-e289-4bf8-b0e7-a8d916e84b17","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/master-air-waybills","description":"Requirement Reference: CL.I4AL.2
\nUse Case: Airline sends Flight manifest & MAWB + HAWB data at flight departure from Destination
\nIntegration Point: IN-CL.I4AL.2-1 - ACS enables airlines to digitally transmit Master Air Waybill data.
\nKey Activities: Transmitting Master Airway Bill data digitally.
\nProcess Flow: I2AL → I4AL → I4GHA/I4CUS/I5ACA/I5CNE
\nActors: Airline (submitter), GHA, Customs, ACA, Consignee (receivers)
\nAuthentication: OAuth 2.0 JWT (Airline role required)
\nMessage Format: JSON (REST API standard)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","master-air-waybills"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"0afb3cb2-5731-4667-a0b1-8b48c78fbdf7","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I4AL.2
\nUse Case: Airline sends Flight manifest & MAWB + HAWB data at flight departure from Destination
\nIntegration Point: IN-CL.I4AL.2-1 - ACS enables airlines to digitally transmit Master Air Waybill in IATA Cargo-XML format.
\nMessage Format: IATA Cargo-XML (XFWB)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","master-air-waybills","xfwb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"60de71ee-b4ca-4e3d-a646-7e8209568ada"},{"name":"Submit Master Air Waybill (IATA Cargo-IMP)","id":"410bf464-a311-4d82-910e-e7e3f6c92a3e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/master-air-waybills/fwb","description":"Requirement Reference: CL.I4AL.2
\nUse Case: Airline sends Flight manifest & MAWB + HAWB data at flight departure from Destination
\nIntegration Point: IN-CL.I4AL.2-1 - ACS enables airlines to digitally transmit Master Air Waybill in IATA Cargo-IMP format.
\nMessage Format: IATA Cargo-IMP (FWB)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","master-air-waybills","fwb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"410bf464-a311-4d82-910e-e7e3f6c92a3e"}],"id":"0f191b0c-8d4c-4274-a7db-194acc163400","_postman_id":"0f191b0c-8d4c-4274-a7db-194acc163400","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Flight Data Distribution","item":[{"name":"Push Flight Manifest to GHA","id":"4f71c273-c77f-4992-8465-f6536340ed2d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/gha","description":"Requirement Reference: CL.I4AL.2, CL.I4GHA.3
\nUse Case: ACS transmits flight manifest to GHA system in digital format
\nIntegration Point: IN-CL.I4AL.2-1 - ACS pushes FFM/MAWB/HAWB to GHA for cargo handling preparation.
\nKey Activities: GHA receives flight manifest, MAWB and HAWB data digitally from airlines via ACS.
\nProcess Flow: I4AL → ACS → I4GHA
\nActors: ACS (system), GHA (receiver)
\nAuthentication: OAuth 2.0 JWT (System role)
\nExecution: Asynchronous push with retry logic. GHA receives data for cargo handling preparation.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","key":"id"}]}},"response":[{"id":"72969225-d56a-4a67-b960-ad4df020f6e7","name":"Success Response","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":{"raw":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/gha","host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"path":["api","v1","import","flight-manifests",":id","push","gha"],"variable":[{"key":"id"}]},"description":"**Requirement Reference**: CL.I4AL.2, CL.I4GHA.3\n\n**Use Case**: ACS transmits flight manifest to GHA system in digital format\n\n**Integration Point**: IN-CL.I4AL.2-1 - ACS pushes FFM/MAWB/HAWB to GHA for cargo handling preparation.\n\n**Key Activities**: GHA receives flight manifest, MAWB and HAWB data digitally from airlines via ACS.\n\n**Process Flow**: I4AL → ACS → I4GHA\n\n**Actors**: ACS (system), GHA (receiver)\n\n**Authentication**: OAuth 2.0 JWT (System role)\n\n**Execution**: Asynchronous push with retry logic. GHA receives data for cargo handling preparation."},"status":"OK","code":200,"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"pushId\": \"push-gha-001\",\n \"manifestId\": \"ffm-20251128-PK307\",\n \"target\": \"GHA\",\n \"status\": \"DELIVERED\",\n \"deliveredAt\": \"2025-11-28T10:01:00Z\"\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T10:01:00Z\",\n \"requestId\": \"req-push-001\"\n }\n}"}],"_postman_id":"4f71c273-c77f-4992-8465-f6536340ed2d"},{"name":"Push Flight Manifest to Customs","id":"3c3e01f8-0e25-4fc2-a182-10853f4a8ee3","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/customs","description":"Requirement Reference: CL.I4AL.2, CL.I4CUS.4
\nUse Case: ACS transmits flight manifest to Customs/WeBOC in digital format
\nIntegration Point: IN-CL.I4AL.2-2 - ACS pushes FFM/MAWB/HAWB to Customs for risk assessment and ACI process.
\nKey Activities: Customs receives flight manifest data, MAWB data and HAWB in digital format. Enables Customs to create draft GD in PSW.
\nProcess Flow: I4AL → ACS → I4CUS
\nActors: ACS (system), Customs (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"3c3e01f8-0e25-4fc2-a182-10853f4a8ee3"},{"name":"Push Flight Manifest to PAA","id":"909fe617-427b-408f-8515-17371e6a6935","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/paa","description":"Requirement Reference: CL.I4AL.2, CL.I5PAA.6
\nUse Case: ACS transmits flight manifest to PAA for statistical purposes
\nIntegration Point: IN-CL.I5PAA.6-1 - ACS pushes FFM to Pakistan Airport Authority for airport planning statistics.
\nKey Activities: PAA receives Flight manifest data in digital format for statistical purposes.
\nProcess Flow: I4AL → ACS → I5PAA
\nActors: ACS (system), PAA (receiver)
\nPurpose: Statistical data collection only - no action required from PAA
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","paa"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","key":"id"}]}},"response":[],"_postman_id":"909fe617-427b-408f-8515-17371e6a6935"},{"name":"Push Flight Manifest to PSW","id":"af6c7b6e-8244-4903-98ae-bc79d83d2b34","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/psw","description":"Requirement Reference: CL.I4AL.2, CL.I5PSW.7
\nUse Case: ACS transmits flight manifest to PSW for statistical purposes
\nIntegration Point: IN-CL.I5PSW.7-1 - ACS pushes FFM to Pakistan Single Window for trade statistics.
\nKey Activities: PSW receives flight Manifest data for statistical purposes.
\nProcess Flow: I4AL → ACS → I5PSW
\nActors: ACS (system), PSW (receiver)
\nPurpose: Trade statistics and business intelligence
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","psw"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","key":"id"}]}},"response":[],"_postman_id":"af6c7b6e-8244-4903-98ae-bc79d83d2b34"},{"name":"Push Flight Manifest to ACA","id":"9b478472-52aa-48b4-a377-45ccdf9d3ad9","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/aca","description":"Requirement Reference: CL.I4AL.2
\nUse Case: ACS transmits flight manifest and MAWB/HAWB data to ACA
\nIntegration Point: IN-CL.I4AL.2-5 - ACS pushes MAWB/HAWB data to Air Cargo Agent for consolidated shipment management.
\nKey Activities: ACA receives MAWB and HAWB data digitally for consolidated shipments.
\nProcess Flow: I4AL → ACS → I5ACA
\nActors: ACS (system), ACA (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","aca"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","key":"id"}]}},"response":[],"_postman_id":"9b478472-52aa-48b4-a377-45ccdf9d3ad9"},{"name":"Push Flight Manifest to Consignee","id":"ad90fe83-8260-4be6-b963-22cdf2615ec4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/:id/push/consignee","description":"Requirement Reference: CL.I4AL.2
\nUse Case: ACS transmits flight manifest and MAWB data to Consignee
\nIntegration Point: IN-CL.I4AL.2-6 - ACS pushes MAWB data to Consignee for direct shipment arrival notification.
\nKey Activities: Consignee receives MAWB data digitally for direct shipments.
\nProcess Flow: I4AL → ACS → I5CNE
\nActors: ACS (system), Consignee (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests",":id","push","consignee"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"ad90fe83-8260-4be6-b963-22cdf2615ec4"}],"id":"94681daf-ea80-4dc7-b550-40ae70da39e9","_postman_id":"94681daf-ea80-4dc7-b550-40ae70da39e9","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"GHA Reception","item":[{"name":"GHA Receives Flight Manifest","id":"24b70228-eaf1-43cd-952d-63b14cd93a09","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/receipts/gha","description":"Requirement Reference: CL.I4GHA.3
\nUse Case: GHA receives FFM/FWB + FHL and files in PSW
\nIntegration Point: IN-CL.I4GHA.3-1 - GHA receives flight manifest, MAWB and HAWB data digitally from airlines via ACS.
\nKey Activities: Receiving flight manifest, MAWB and HAWB data. Filing in PSW system.
\nProcess Flow: I4AL → I4GHA
\nActors: GHA (receiver)
\nAuthentication: OAuth 2.0 JWT (GHA role required)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests","receipts","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"b374ed2a-c3cc-43b7-b61f-3d7dd973444a","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I4GHA.3
\nUse Case: GHA receives FFM/FWB + FHL and files in PSW
\nIntegration Point: IN-CL.I4GHA.3-1 - GHA receives MAWB data digitally from airlines via ACS.
\nKey Activities: Receiving MAWB data for cargo handling preparation.
\nProcess Flow: I4AL → I4GHA
\nActors: GHA (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","master-air-waybills","receipts","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"c29fc2a9-3e70-49ef-8927-acd6e8b10d87"},{"name":"GHA Receives House Air Waybill","id":"78250dd2-0167-45dd-8f15-c22024e0e2f4","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/house-air-waybills/receipts/gha","description":"Requirement Reference: CL.I4GHA.3
\nUse Case: GHA receives FFM/FWB + FHL and files in PSW
\nIntegration Point: IN-CL.I4GHA.3-1 - GHA receives HAWB data digitally for consolidated shipments.
\nKey Activities: Receiving House Air Waybill data for consolidated cargo handling.
\nProcess Flow: I4AL → I4GHA
\nActors: GHA (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","house-air-waybills","receipts","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"78250dd2-0167-45dd-8f15-c22024e0e2f4"}],"id":"23124002-e616-4961-acb7-5dbea9186ccd","_postman_id":"23124002-e616-4961-acb7-5dbea9186ccd","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Customs Reception","item":[{"name":"Customs Receives Flight Manifest","id":"2e1af481-067d-4f1a-853d-5695165ed462","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/receipts/customs","description":"Requirement Reference: CL.I4CUS.4
\nUse Case: Customs receives FFM, FWB & FHL
\nIntegration Point: IN-CL.I4CUS.4-1 - Customs receives flight manifest data digitally via ACS for risk assessment.
\nKey Activities: Receiving flight manifest, MAWB and HAWB data. Creating draft GD in PSW.
\nProcess Flow: I4GHA → I4CUS
\nActors: Customs/WeBOC (receiver)
\nAuthentication: OAuth 2.0 JWT (Customs role required)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests","receipts","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"01f1ef64-b133-405f-9936-6bd20611b12a","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I4CUS.4
\nUse Case: Customs receives FFM, FWB & FHL
\nIntegration Point: IN-CL.I4CUS.4-1 - Customs receives MAWB data digitally for customs clearance processing.
\nProcess Flow: I4GHA → I4CUS → I6CUS
\nActors: Customs/WeBOC (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","master-air-waybills","receipts","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"765e3894-325f-4300-b9c2-a2801a072b30"},{"name":"Customs Receives House Air Waybill","id":"5258aab4-1d93-4e00-a66f-6a838d3917e5","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/house-air-waybills/receipts/customs","description":"Requirement Reference: CL.I4CUS.4
\nUse Case: Customs receives FFM, FWB & FHL
\nIntegration Point: IN-CL.I4CUS.4-1 - Customs receives HAWB data digitally for consolidated shipment processing.
\nProcess Flow: I4GHA → I4CUS → I6CUS
\nActors: Customs/WeBOC (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","house-air-waybills","receipts","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"5258aab4-1d93-4e00-a66f-6a838d3917e5"}],"id":"0e622804-0d2d-44c3-ae5d-b136ef993679","_postman_id":"0e622804-0d2d-44c3-ae5d-b136ef993679","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Postal Reception","item":[{"name":"Pakistan Post Receives Flight Manifest","id":"f5393ab5-7bad-44f7-a026-61f9fc76c710","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/flight-manifests/receipts/postal","description":"Requirement Reference: CL.I4P.5
\nUse Case: Pakistan Post receives FFM & Mail information
\nIntegration Point: IN-CL.I4P.5-1 - Pakistan Post receives flight manifest and mail information digitally from airlines via ACS.
\nKey Activities: Receiving mail data and transmitting mail data to PSW.
\nProcess Flow: I4GHA → I4P → I4PSW/I7P
\nActors: Pakistan Post (receiver)
\nAuthentication: OAuth 2.0 JWT (Postal role required)
\nPurpose: Mail item tracking and processing
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","flight-manifests","receipts","postal"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"6c84d1c7-e2c4-49c5-8b7f-3d20a024af26","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I5PAA.6
\nUse Case: PAA receives FFM message for statistical purposes
\nIntegration Point: IN-CL.I5PAA.6-1 - ACS enables PAA to receive Flight manifest data in digital format for statistical purposes.
\nKey Activities: Receiving flight manifest data for airport planning and statistics.
\nProcess Flow: I4AL → I5PAA
\nActors: PAA (viewer)
\nAuthentication: OAuth 2.0 JWT (PAA role required)
\nPurpose: Airport planning, capacity management, statistical analysis
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","statistics","paa"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"startDate","value":"2025-11-01"},{"key":"endDate","value":"2025-11-30"},{"key":"airport","value":"KHI"}],"variable":[]}},"response":[{"id":"a54647a4-0dcb-4602-a677-485b3e45824c","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":{"raw":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/statistics/paa?startDate=2025-11-01&endDate=2025-11-30&airport=KHI","host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"path":["api","v1","import","statistics","paa"],"query":[{"key":"startDate","value":"2025-11-01"},{"key":"endDate","value":"2025-11-30"},{"key":"airport","value":"KHI"}]},"description":"**Requirement Reference**: CL.I5PAA.6\n\n**Use Case**: PAA receives FFM message for statistical purposes\n\n**Integration Point**: IN-CL.I5PAA.6-1 - ACS enables PAA to receive Flight manifest data in digital format for statistical purposes.\n\n**Key Activities**: Receiving flight manifest data for airport planning and statistics.\n\n**Process Flow**: I4AL → I5PAA\n\n**Actors**: PAA (viewer)\n\n**Authentication**: OAuth 2.0 JWT (PAA role required)\n\n**Purpose**: Airport planning, capacity management, statistical analysis"},"status":"OK","code":200,"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"period\": {\n \"startDate\": \"2025-11-01\",\n \"endDate\": \"2025-11-30\"\n },\n \"airport\": \"KHI\",\n \"totalFlights\": 450,\n \"totalCargoWeight\": 2500000.5,\n \"weightUnit\": \"KG\",\n \"totalPieces\": 15000,\n \"airlines\": [\n {\n \"airlineCode\": \"PK\",\n \"flights\": 120,\n \"cargoWeight\": 650000.0\n },\n {\n \"airlineCode\": \"EK\",\n \"flights\": 90,\n \"cargoWeight\": 800000.0\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T10:00:00Z\",\n \"requestId\": \"req-paa-001\"\n }\n}"}],"_postman_id":"7f22f318-61fc-4efc-8e2d-88364c756f64"},{"name":"PSW View Flight Statistics","id":"b238708c-d9af-4dbf-a4c4-ee89732b40fe","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/statistics/psw?startDate=2025-11-01&endDate=2025-11-30","description":"Requirement Reference: CL.I5PSW.7
\nUse Case: PSW receives FFM message for statistical purposes
\nIntegration Point: IN-CL.I5PSW.7-1 - ACS enables PSW to receive flight Manifest data for statistical purposes.
\nKey Activities: Receiving flight manifest data for trade statistics and business intelligence.
\nProcess Flow: I4AL → I5PSW
\nActors: PSW (viewer)
\nAuthentication: OAuth 2.0 JWT (PSW role required)
\nPurpose: Trade statistics, business intelligence, reporting
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","statistics","psw"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"startDate","value":"2025-11-01"},{"key":"endDate","value":"2025-11-30"}],"variable":[]}},"response":[{"id":"42e4802f-ca6a-4506-b78c-fe6096c0b773","name":"Success Response","originalRequest":{"method":"GET","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":{"raw":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/statistics/psw?startDate=2025-11-01&endDate=2025-11-30","host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"path":["api","v1","import","statistics","psw"],"query":[{"key":"startDate","value":"2025-11-01"},{"key":"endDate","value":"2025-11-30"}]},"description":"**Requirement Reference**: CL.I5PSW.7\n\n**Use Case**: PSW receives FFM message for statistical purposes\n\n**Integration Point**: IN-CL.I5PSW.7-1 - ACS enables PSW to receive flight Manifest data for statistical purposes.\n\n**Key Activities**: Receiving flight manifest data for trade statistics and business intelligence.\n\n**Process Flow**: I4AL → I5PSW\n\n**Actors**: PSW (viewer)\n\n**Authentication**: OAuth 2.0 JWT (PSW role required)\n\n**Purpose**: Trade statistics, business intelligence, reporting"},"status":"OK","code":200,"_postman_previewlanguage":"Text","header":[],"cookie":[],"responseTime":null,"body":"{\n \"success\": true,\n \"data\": {\n \"period\": {\n \"startDate\": \"2025-11-01\",\n \"endDate\": \"2025-11-30\"\n },\n \"totalImports\": 15000,\n \"totalValue\": 75000000.00,\n \"currency\": \"USD\",\n \"topCommodities\": [\n {\n \"commodity\": \"Electronics\",\n \"value\": 25000000.00,\n \"percentage\": 33.3\n },\n {\n \"commodity\": \"Textiles\",\n \"value\": 15000000.00,\n \"percentage\": 20.0\n }\n ],\n \"topOrigins\": [\n {\n \"country\": \"UAE\",\n \"value\": 30000000.00,\n \"percentage\": 40.0\n },\n {\n \"country\": \"China\",\n \"value\": 20000000.00,\n \"percentage\": 26.7\n }\n ]\n },\n \"meta\": {\n \"timestamp\": \"2025-11-28T10:00:00Z\",\n \"requestId\": \"req-psw-001\"\n }\n}"}],"_postman_id":"b238708c-d9af-4dbf-a4c4-ee89732b40fe"}],"id":"25478f09-7f9a-44fd-9e38-a2b2ad94ce2b","description":"Endpoints for PAA and PSW to view flight statistics
\n","_postman_id":"25478f09-7f9a-44fd-9e38-a2b2ad94ce2b","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"ec16924f-795f-49d9-8a40-040679db0456","_postman_id":"ec16924f-795f-49d9-8a40-040679db0456","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Document Upload & Distribution","item":[{"name":"Direct Shipment - Consignee Upload","item":[{"name":"Upload Consignment Documents","id":"1ffe56e1-d2a1-4a43-b513-c08b03068248","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consignment-documents","description":"Requirement Reference: CL.I5CNE.8
\nUse Case: Direct shipment, Consignee uploads imports documents (ACI process)
\nIntegration Point: IN-CL.I5CNE.8-1 - ACS enables Consignee to send documents of import shipment in digital format to Customs, customs broker, or Air Cargo Agent.
\nKey Activities: Sending consignment documents for ACI process. Documents include: MAWB data, Goods Declaration (or Export declaration), Packing list, Invoice, Export Certificates and NOC's if applicable.
\nProcess Flow: I4AL → I5CNE → I6CB/I6GHA/I6CUS
\nActors: Consignee (uploader), CB, GHA, Customs (receivers)
\nAuthentication: OAuth 2.0 JWT (Consignee role required)
\nShipment Type: DIRECT (no consolidation, no HAWB)
\nBusiness Rule: This endpoint creates the document package metadata. Actual file uploads done via separate endpoint.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"d8ba05ec-042f-41e4-9ffd-3f779aa412c2","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I5CNE.8
\nUse Case: Direct shipment, Consignee uploads document files
\nIntegration Point: IN-CL.I5CNE.8-1 - ACS enables upload of actual document files (PDF, images).
\nKey Activities: Uploading document files for ACI process.
\nProcess Flow: I5CNE → ACS (file storage)
\nActors: Consignee (uploader)
\nFile Requirements:
\nRequirement Reference: CL.I5CNE.8
\nUse Case: View uploaded document package details
\nProcess Flow: I5CNE
\nActors: Consignee, CB, GHA, Customs (viewers)
\nReturns: Document package metadata and list of uploaded files
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents",":id"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[{"id":"4a9e31fe-7bed-44c9-a4ca-e20047b0065a","name":"Success Response","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I5CNE.8
\nUse Case: Update document package metadata before finalization
\nBusiness Rule: Can only update documents in DRAFT status
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents",":id"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"0f7dad43-4b29-418c-aad5-5145cecb05b0"},{"name":"Finalize Document Package","id":"9b870d78-39ff-4172-bbcd-7a3ebfe6b905","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consignment-documents/:id/finalize","description":"Requirement Reference: CL.I5CNE.8
\nUse Case: Finalize document package for distribution
\nKey Activities: Lock document package from further edits and trigger distribution to stakeholders.
\nBusiness Rules:
\nRequirement Reference: CL.I5CNE.8
\nUse Case: List all consignment documents with pagination
\nFilters: status, awbNumber, startDate, endDate, shipmentType
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"page","value":"1"},{"key":"limit","value":"20"},{"key":"status","value":"FINALIZED"}],"variable":[]}},"response":[],"_postman_id":"26cac197-327f-44aa-9124-0e79418d4791"}],"id":"f30e9427-3158-46e0-9cbe-14f2bd4b86d1","_postman_id":"f30e9427-3158-46e0-9cbe-14f2bd4b86d1","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Direct Shipment - Distribution","item":[{"name":"Push Documents to Customs Broker","id":"17ed578b-bd7d-4a0a-afb2-58c37a36847c","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consignment-documents/:id/push/customs-broker","description":"Requirement Reference: CL.I5CNE.8
\nUse Case: ACS transmits consignment documents to Customs Broker
\nIntegration Point: IN-CL.I5CNE.8-1 - ACS pushes documents from Consignee to Customs Broker for customs clearance processing.
\nProcess Flow: I5CNE → ACS → I6CB
\nActors: ACS (system), Customs Broker (receiver)
\nExecution: Asynchronous push with retry logic
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents",":id","push","customs-broker"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"17ed578b-bd7d-4a0a-afb2-58c37a36847c"},{"name":"Push Documents to GHA","id":"bc721fd0-6d15-421d-be74-ce9d2c128825","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consignment-documents/:id/push/gha","description":"Requirement Reference: CL.I5CNE.8
\nUse Case: ACS transmits consignment documents to GHA
\nIntegration Point: IN-CL.I5CNE.8-2 - ACS pushes documents from Consignee to GHA for cargo release preparation.
\nProcess Flow: I5CNE → ACS → I6GHA
\nActors: ACS (system), GHA (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents",":id","push","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"bc721fd0-6d15-421d-be74-ce9d2c128825"},{"name":"Push Documents to Customs","id":"da9671f0-c5e2-4c57-aed7-0e03a79ec11d","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consignment-documents/:id/push/customs","description":"Requirement Reference: CL.I5CNE.8
\nUse Case: ACS transmits consignment documents to Customs/WeBOC
\nIntegration Point: IN-CL.I5CNE.8-3 - ACS pushes documents from Consignee to Customs for ACI process.
\nProcess Flow: I5CNE → ACS → I6CUS
\nActors: ACS (system), Customs (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents",":id","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"da9671f0-c5e2-4c57-aed7-0e03a79ec11d"}],"id":"5efb5c87-db09-4758-a1a8-246a758faf20","_postman_id":"5efb5c87-db09-4758-a1a8-246a758faf20","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Consolidated Shipment - ACA Upload","item":[{"name":"Upload Consolidated Documents","id":"6f0d6b0b-6639-4fb8-8fe5-6106b7e9617e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents","description":"Requirement Reference: CL.I5ACA.9
\nUse Case: Consolidation, ACA uploads imports documents (ACI Process)
\nIntegration Point: IN-CL.I5ACA.9-1 - ACS enables ACA to send document of import shipment in digital format to Customs, customs broker or Consignee.
\nKey Activities: Sending consignment documents for ACI process. Documents include: MAWB data, HAWB data, Goods Declaration (or Export declaration), Packing list, Invoice, Export Certificates and NOC's if applicable.
\nProcess Flow: I4AL → I5ACA → I6GHA/I6CB/I6CNE/I6CUS
\nActors: ACA (uploader), GHA, CB, Consignee, Customs (receivers)
\nAuthentication: OAuth 2.0 JWT (ACA role required)
\nShipment Type: CONSOLIDATED (multiple HAWBs under one MAWB)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"d2902618-3229-4c01-bc04-fb65decb49ba","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I5ACA.9
\nUse Case: Consolidation, ACA uploads document files
\nIntegration Point: IN-CL.I5ACA.9-1 - ACS enables upload of consolidated shipment document files.
\nActors: ACA (uploader)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents","files"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[],"_postman_id":"e447d3f8-1b3d-41cd-9e15-59cfbd219b34"},{"name":"View Consolidated Documents","id":"a5af0fb5-1fc2-4c7b-802d-0f0f665adf52","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"GET","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents/:id","description":"Requirement Reference: CL.I5ACA.9
\nUse Case: View consolidated document package details
\nActors: ACA, GHA, CB, Consignee, Customs (viewers)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents",":id"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"a5af0fb5-1fc2-4c7b-802d-0f0f665adf52"},{"name":"Update Consolidated Document Metadata","id":"bea181b6-b831-46b5-a849-ce5257a60860","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"PATCH","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents/:id","description":"Requirement Reference: CL.I5ACA.9
\nUse Case: Update consolidated document package (e.g., add/remove HAWBs)
\nBusiness Rule: Can only update documents in DRAFT status
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents",":id"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"bea181b6-b831-46b5-a849-ce5257a60860"},{"name":"Finalize Consolidated Package","id":"8c12bbe4-087a-43e2-a835-38453efaba41","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents/:id/finalize","description":"Requirement Reference: CL.I5ACA.9
\nUse Case: Finalize consolidated document package for distribution
\nBusiness Rules:
\nRequirement Reference: CL.I5ACA.9
\nUse Case: List all consolidated documents with pagination
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"page","value":"1"},{"key":"limit","value":"20"}],"variable":[]}},"response":[],"_postman_id":"4809cee7-fcf4-497b-a16c-05c9b0ef5ca4"}],"id":"966f9528-1657-497c-862d-5014a800c664","_postman_id":"966f9528-1657-497c-862d-5014a800c664","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Consolidated Shipment - Distribution","item":[{"name":"Push Consolidated Docs to GHA","id":"e089d04f-c771-4ac2-b8a6-81d334114179","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents/:id/push/gha","description":"Requirement Reference: CL.I5ACA.9
\nUse Case: ACS transmits consolidated documents to GHA
\nIntegration Point: IN-CL.I5ACA.9-1 - ACS pushes documents from ACA to GHA for cargo handling.
\nProcess Flow: I5ACA → ACS → I6GHA
\nActors: ACS (system), GHA (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents",":id","push","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"e089d04f-c771-4ac2-b8a6-81d334114179"},{"name":"Push Consolidated Docs to Customs Broker","id":"82420875-7ec4-4fcc-82fc-e590225f89e5","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents/:id/push/customs-broker","description":"Requirement Reference: CL.I5ACA.9
\nUse Case: ACS transmits consolidated documents to Customs Broker
\nIntegration Point: IN-CL.I5ACA.9-2 - ACS pushes documents from ACA to CB for customs processing.
\nProcess Flow: I5ACA → ACS → I6CB
\nActors: ACS (system), Customs Broker (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents",":id","push","customs-broker"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"82420875-7ec4-4fcc-82fc-e590225f89e5"},{"name":"Push Consolidated Docs to Consignee","id":"fccb578a-a4d7-4507-9b46-696c1965f02b","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents/:id/push/consignee","description":"Requirement Reference: CL.I5ACA.9
\nUse Case: ACS transmits consolidated documents to Consignee
\nIntegration Point: IN-CL.I5ACA.9-3 - ACS pushes HAWB-specific documents from ACA to individual Consignees.
\nProcess Flow: I5ACA → ACS → I6CNE
\nActors: ACS (system), Consignee (receiver)
\nNote: Each consignee receives only their HAWB documents, not entire MAWB
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents",":id","push","consignee"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"fccb578a-a4d7-4507-9b46-696c1965f02b"},{"name":"Push Consolidated Docs to Customs","id":"7540a1ca-28db-4563-9ddb-e2e277854993","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents/:id/push/customs","description":"Requirement Reference: CL.I5ACA.9
\nUse Case: ACS transmits consolidated documents to Customs
\nIntegration Point: IN-CL.I5ACA.9-4 - ACS pushes documents from ACA to Customs for ACI process.
\nProcess Flow: I5ACA → ACS → I6CUS
\nActors: ACS (system), Customs (receiver)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents",":id","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"7540a1ca-28db-4563-9ddb-e2e277854993"}],"id":"410d10d7-bbae-4286-9a7e-2f039f003e87","_postman_id":"410d10d7-bbae-4286-9a7e-2f039f003e87","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Document Reception - Consignee","item":[{"name":"Consignee Receives Documents","id":"733f161a-8b4a-4bd9-95b6-398695b60520","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consolidated-documents/receipts/consignee","description":"Requirement Reference: CL.I6CNE.10
\nUse Case: Consolidation, receives documents
\nIntegration Point: IN-CL.I6CNE.10-1 - ACS enables Consignee to digitally receive the documents of the consignment from ACA.
\nKey Activities: Receiving the consignment documents (MAWB data, HAWB data, GD, Packing list, Invoice, Certificates).
\nProcess Flow: I5ACA → I6CNE
\nActors: Consignee (receiver)
\nAuthentication: OAuth 2.0 JWT (Consignee role required)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents","receipts","consignee"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"e15d3417-7103-4bae-bbcd-eafd63aa5f9d","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I6CNE.10
\nUse Case: List all documents received by Consignee
\nActors: Consignee (viewer)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consolidated-documents","receipts","consignee"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"page","value":"1"},{"key":"limit","value":"20"}],"variable":[]}},"response":[],"_postman_id":"2fa96486-0927-4869-924e-72a6803e7cd8"}],"id":"6fe5c14f-9436-4601-8540-a9cb457bca95","_postman_id":"6fe5c14f-9436-4601-8540-a9cb457bca95","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Document Reception - Customs Broker","item":[{"name":"Customs Broker Receives Documents","id":"854f5d67-3f3b-4cb8-ab9c-8e0a43880155","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consignment-documents/receipts/customs-broker","description":"Requirement Reference: CL.I6CB.11
\nUse Case: Customs Broker receives Documents
\nIntegration Point: IN-CL.I6CB.11-1 - ACS enables CB to receive import consignment documents in digital format.
\nKey Activities: Receiving the consignment documents (MAWB data, HAWB data, GD, Packing list, Invoice, Certificates).
\nProcess Flow: I5ACA/I5CNE → I6CB
\nActors: Customs Broker (receiver)
\nAuthentication: OAuth 2.0 JWT (Customs Broker role required)
\nSource: Can receive from ACA (consolidated) or Consignee (direct)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents","receipts","customs-broker"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"3af4d5ab-81f6-485b-b2cb-350784197db1","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I6CB.11
\nUse Case: List all documents received by Customs Broker
\nActors: Customs Broker (viewer)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents","receipts","customs-broker"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"page","value":"1"},{"key":"limit","value":"20"}],"variable":[]}},"response":[],"_postman_id":"dba891f2-22a8-439b-a282-b080c799b5ce"}],"id":"7c2bc9be-f43d-46d9-a1da-54dba7830044","_postman_id":"7c2bc9be-f43d-46d9-a1da-54dba7830044","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Document Reception - GHA","item":[{"name":"GHA Receives Documents","id":"62977287-92f5-45b5-b230-81e3d82ee9b2","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consignment-documents/receipts/gha","description":"Requirement Reference: CL.I6GHA.12
\nUse Case: GHA receives Documents
\nIntegration Point: IN-CL.I6GHA.12-1 - ACS enables GHA to receive consignment documents from ACA (consolidated) or Consignee (Direct) digitally.
\nKey Activities: Receiving the consignment documents (MAWB data, HAWB data, GD, Packing list, Invoice, Certificates).
\nProcess Flow: I5CNE/I5ACA → I6GHA
\nActors: GHA (receiver)
\nAuthentication: OAuth 2.0 JWT (GHA role required)
\nSource: Can receive from ACA (consolidated) or Consignee (direct)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents","receipts","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"f9bd5669-7252-4548-b4ab-b14bb0a9d52a","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I6GHA.12
\nUse Case: List all documents received by GHA
\nActors: GHA (viewer)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents","receipts","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"page","value":"1"},{"key":"limit","value":"20"}],"variable":[]}},"response":[],"_postman_id":"4d18bcf8-b702-42ed-87d5-b5ab4b581eec"}],"id":"6c52274c-e5b4-4563-a171-27cfbb91a27d","_postman_id":"6c52274c-e5b4-4563-a171-27cfbb91a27d","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"Document Reception - Customs","item":[{"name":"Customs Receives Documents","id":"39788efe-5855-4cc1-bb25-92d3aeb2d95f","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/consignment-documents/receipts/customs","description":"Requirement Reference: CL.I6CUS.13
\nUse Case: Customs receives Documents
\nIntegration Point: IN-CL.I6CUS.13-1 - ACS enables Customs to receive documents from ACA (consol shipments) and Consignee (direct shipments).
\nKey Activities: Receiving the consignment documents & Starting ACI process.
\nProcess Flow: I5ACA/I5CNE → I6CUS → I7CUS
\nActors: Customs/WeBOC (receiver)
\nAuthentication: OAuth 2.0 JWT (Customs role required)
\nSource: Can receive from ACA (consolidated) or Consignee (direct)
\nNext Step: Triggers ACI process and draft GD creation (CL.I7CUS.14)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","consignment-documents","receipts","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"80b32f8f-98c2-4228-8d51-035494e16866","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I7CUS.14
\nUse Case: ACI process starts / GD Process starts
\nIntegration Point: IN-CL.I7CUS.14-1 - Customs initiates Advance Cargo Information (ACI) process after receiving all required documents.
\nKey Activities: Completion of ACI process & Creation of draft GD in PSW.
\nProcess Flow: I6CUS → I7CUS
\nActors: Customs/WeBOC (initiator)
\nAuthentication: OAuth 2.0 JWT (Customs role required)
\nACI Process Purpose:
\nBusiness Rules:
\nRequirement Reference: CL.I7CUS.14
\nUse Case: View ACI process status and details
\nProcess Flow: I7CUS
\nActors: Customs, CB, ACA, Consignee (viewers)
\nAuthentication: OAuth 2.0 JWT (Customs/CB/ACA/Consignee role)
\nReturns: Complete ACI process details including validation results, risk assessment, and draft GD status
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","aci-processes",":id"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[{"id":"9134b678-289a-4995-b63d-a3d80e658ff8","name":"Success Response","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I7CUS.14
\nUse Case: List all ACI processes with pagination and filters
\nActors: Customs (viewer)
\nFilters: status, awbNumber, flightNumber, startDate, endDate, riskLevel
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","aci-processes"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"page","value":"1"},{"key":"limit","value":"20"},{"key":"status","value":"COMPLETED"},{"key":"startDate","value":"2025-11-01"},{"key":"endDate","value":"2025-11-30"}],"variable":[]}},"response":[{"id":"94e8e692-75a8-4eb2-8c5d-ff19696cc688","name":"Success Response","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I7CUS.14
\nUse Case: ACI process starts / GD Process starts
\nIntegration Point: IN-CL.I7CUS.14-2 - Customs creates draft Goods Declaration in PSW after ACI process completion.
\nKey Activities: Creation of draft GD in PSW. ACS enables Customs to receive flight manifest data, MAWB data and HAWB in digital format. ACS enables Customs to create draft GD in PSW and notify CB, ACA and Consignee.
\nProcess Flow: I7CUS → I11CUS (next module)
\nActors: Customs/WeBOC (creator)
\nAuthentication: OAuth 2.0 JWT (Customs role required)
\nDraft GD Purpose:
\nBusiness Rules:
\nRequirement Reference: CL.I7CUS.14
\nUse Case: View draft Goods Declaration details
\nProcess Flow: I7CUS
\nActors: Customs, CB, ACA, Consignee (viewers)
\nAuthentication: OAuth 2.0 JWT (Customs/CB/ACA/Consignee role)
\nReturns: Complete draft GD details including all items, duty calculations, and risk assessment
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","draft-goods-declarations",":id"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[{"id":"b8e3ebcf-b1d3-4b0d-8f94-0953c55c9c5e","name":"Success Response","originalRequest":{"method":"GET","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I7CUS.14
\nUse Case: ACS notifies Customs Broker about draft GD creation
\nIntegration Point: IN-CL.I7CUS.14-3 - ACS pushes draft GD notification to Customs Broker so they can complete final GD submission.
\nKey Activities: Notifying CB about draft GD availability. CB can view draft GD and create final GD submission.
\nProcess Flow: I7CUS → ACS → CB
\nActors: ACS (system), Customs Broker (receiver)
\nAuthentication: OAuth 2.0 JWT (System role)
\nExecution: Asynchronous push with retry logic. CB receives notification via email/SMS and system alert.
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","draft-goods-declarations",":id","push","customs-broker"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[{"id":"cec70251-0bb0-4d03-8a75-baf806c6c6e1","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: CL.I7CUS.14
\nUse Case: ACS notifies Air Cargo Agent about draft GD creation
\nIntegration Point: IN-CL.I7CUS.14-4 - ACS pushes draft GD notification to ACA for consolidated shipments.
\nKey Activities: Notifying ACA about draft GD availability. ACA can view draft GD and coordinate final GD submission with CB or Consignee.
\nProcess Flow: I7CUS → ACS → ACA
\nActors: ACS (system), ACA (receiver)
\nNote: Only applicable for consolidated shipments
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","draft-goods-declarations",":id","push","aca"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"a9d267ff-d4c2-48b7-a1c9-60502ee46a9f"},{"name":"Notify Consignee","id":"a2c7c022-eecc-46b7-82d7-58ae9897604e","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer {{jwt_token}}"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/import/draft-goods-declarations/:id/push/consignee","description":"Requirement Reference: CL.I7CUS.14
\nUse Case: ACS notifies Consignee about draft GD creation
\nIntegration Point: IN-CL.I7CUS.14-5 - ACS pushes draft GD notification to Consignee so they are aware of customs clearance status.
\nKey Activities: Notifying Consignee about draft GD availability. Consignee can view estimated duties/taxes and coordinate with CB for final GD submission.
\nProcess Flow: I7CUS → ACS → Consignee
\nActors: ACS (system), Consignee (receiver)
\nPurpose: Keep Consignee informed about clearance progress and estimated costs
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","import","draft-goods-declarations",":id","push","consignee"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"string","key":"id"}]}},"response":[],"_postman_id":"a2c7c022-eecc-46b7-82d7-58ae9897604e"}],"id":"0ac13efd-b0b3-4ebd-b41b-5cd1fd9974a3","_postman_id":"0ac13efd-b0b3-4ebd-b41b-5cd1fd9974a3","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"5b6a1eaa-5c94-4b8b-bd6c-a34a3fefc2d6","_postman_id":"5b6a1eaa-5c94-4b8b-bd6c-a34a3fefc2d6","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}}],"id":"f52466f2-c440-4746-9339-51f3281b3068","_postman_id":"f52466f2-c440-4746-9339-51f3281b3068","description":"","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}}},{"name":"e-Trace module","item":[{"name":"Inbound - Receive Status Updates","item":[{"name":"Cargo Status Update (JSON)","id":"1c853464-0682-4abe-bdee-39ddeaed49a0","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"description":"Unique request identifier for traceability
\n","key":"X-Request-ID","value":"421dae3e-5add-43d1-97dc-ffa99803201c"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.837Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/status-updates/receipts","description":"Requirement Reference: TRC.1
\nUse Case: End-to-end monitoring of cargo location, status & handling milestones
\nDescription: ACS receives cargo status updates from all stakeholders (Airline, EPO, GHA, Customs, Forwarder, ACA, etc.) for real-time tracking and monitoring. Updates include IATA Cargo IQ milestone events.
\nProcess Flows:
\nAirline system → ACS
\nGHA → ACS
\nCustoms → ACS
\nEPO → ACS
\nForwarder → ACS
\nAction: PUSH
\nPriority: P1 (Critical Integration)
\nIATA Cargo IQ Milestones:
\nFOH: Freight on Hand (cargo acceptance completed)
\nRCS: Ready for Carriage (prepared for loading)
\nPRE: Pre-departed (prepared for loading onto aircraft)
\nDEP: Departed (flight departed with cargo)
\nARR: Arrived (flight arrived at destination)
\nRCF: Received from Flight (cargo unloaded)
\nNFD: Notification for Delivery (consignee notified)
\nDLV: Delivered (cargo delivered to consignee)
\nBKD: Booked (shipment booked on flight)
\nOFL: Offloaded (cargo removed from flight)
\nDIS: Discrepancy (damage, shortage, overage)
\nValidation Rules:
\nAWB number format: {prefix}-{8-digit-serial}
\nAWB type: MAWB or HAWB
\nStatus code: Valid IATA FSU code
\nTimestamp: ISO 8601 format with timezone
\nAirport code: Valid 3-letter IATA code
\nActor type: AIRLINE, EPO, GHA, CUSTOMS, FORWARDER, ACA, CONSIGNOR, CONSIGNEE
\nUnique request identifier for traceability
\n","key":"X-Request-ID","value":"3bbd7151-81f7-44c1-a41b-29e9399d10ac"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.837Z"},{"key":"Content-Type","value":"application/xml"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/status-updates/xfsu","description":"Requirement Reference: TRC.1
\nMessage Format: IATA Cargo-XML (XFSU - Freight Status Update)
\nUse Case: End-to-end monitoring of cargo location, status & handling milestones
\nDescription: ACS receives cargo status updates from all stakeholders (Airline, EPO, GHA, Customs, Forwarder, ACA, etc.) for real-time tracking and monitoring. Updates include IATA Cargo IQ milestone events.
\nProcess Flows:
\nAirline system → ACS
\nGHA → ACS
\nCustoms → ACS
\nEPO → ACS
\nForwarder → ACS
\nAction: PUSH
\nPriority: P1 (Critical Integration)
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","trace","status-updates","xfsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"51750757-fd62-4dfd-81cb-b3ee5a27eb0e","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Unique request identifier for traceability","key":"X-Request-ID","value":"db2140d2-e66b-40a2-9ffc-f3325f464def"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.837Z"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerUnique request identifier for traceability
\n","key":"X-Request-ID","value":"070a498a-09f6-49cc-8e2f-4b42e4963a6c"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.838Z"},{"key":"Content-Type","value":"text/plain"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/status-updates/fsu","description":"Requirement Reference: TRC.1
\nMessage Format: IATA Cargo-IMP (FSU - Freight Status Update)
\nUse Case: End-to-end monitoring of cargo location, status & handling milestones
\nDescription: ACS receives cargo status updates from all stakeholders (Airline, EPO, GHA, Customs, Forwarder, ACA, etc.) for real-time tracking and monitoring. Updates include IATA Cargo IQ milestone events.
\nProcess Flows:
\nAirline system → ACS
\nGHA → ACS
\nCustoms → ACS
\nEPO → ACS
\nForwarder → ACS
\nAction: PUSH
\nPriority: P1 (Critical Integration)
\nFSU Format:
\nFSU\n{AWB-Number}\n{Status-Code}/{Date} {Time}/{Location}\n{Flight-Number}\n{Pieces}/{Weight}\n{Remarks}\n\nUnique request identifier for traceability
\n","key":"X-Request-ID","value":"5df6039d-84af-47ff-a9fc-fefe0d46990e"},{"description":"ACS system identifier
\n","key":"X-Request-System","value":"ACS"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.838Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/status-updates/:id/push","description":"Requirement Reference: TRC.1
\nUse Case: End-to-end monitoring of cargo location, status & handling milestones
\nDescription: Consolidated endpoint for ACS to push cargo status updates to any stakeholder system. Supports all stakeholder types: Airline, EPO, GHA, Customs, Forwarder/ACA, Consignor, Consignee.
\nProcess Flows:
\nACS → Airline system
\nACS → EPO System
\nACS → GHA system
\nACS → Customs/WeBOC
\nACS → Forwarder system
\nACS → Consignor system
\nACS → Consignee system
\nAction: POST
\nPriority: P2
\nNote: This endpoint replaces individual push endpoints (/push/airline, /push/epo, /push/gha, etc.) with a unified endpoint where the receiver is specified in the payload.
Unique request identifier for traceability
\n","key":"X-Request-ID","value":"b38c3b70-0111-4deb-88ed-31bcbd11ce65"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.838Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/sensor-data/receipts","description":"Requirement Reference: TRC.2
\nUse Case: Time & temperature (data loggers) information
\nDescription: ACS receives sensor data from IoT data loggers attached to shipments. Supports multiple sensor types for monitoring temperature-sensitive cargo (pharmaceuticals, perishables, chemicals).
\nProcess Flow: Data Loggers → ACS
\nPriority: P1 (Critical Integration)
\nSensor Types:
\nTEMPERATURE: Temperature monitoring (Celsius/Fahrenheit)
\nHUMIDITY: Relative humidity percentage
\nSHOCK: G-force measurements for impact detection
\nLIGHT: Lux measurements for tamper detection
\nPRESSURE: Atmospheric pressure in hPa
\nTILT: Angle measurements for proper handling
\nTransmission Modes:
\nREAL_TIME: Immediate transmission via cellular/WiFi
\nBATCH: Periodic batch uploads (e.g., every 15 minutes)
\nOFFLINE_SYNC: Stored readings uploaded after flight/journey
\nUnique request identifier for traceability
\n","key":"X-Request-ID","value":"405e33de-76a4-4076-9908-fbfe2494d6fd"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.838Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/sensor-data/bulk","description":"Requirement Reference: TRC.2
\nUse Case: Time & temperature (data loggers) information
\nDescription: Bulk upload of sensor data readings for batch transmission from data loggers. Used when loggers operate in offline mode and sync accumulated data periodically or after flight arrival.
\nProcess Flow: Data Loggers → ACS
\nPriority: P1
\nUse Cases:
\nOffline data loggers that store readings during flight (no cellular signal)
\nBatch transmission to reduce cellular data costs
\nHistorical data upload for analysis
\nLimits:
\nMaximum 1000 readings per bulk upload
\nMaximum 24-hour time span per upload
\nReadings must be in chronological order
\nUnique request identifier for traceability
\n","key":"X-Request-ID","value":"89aec4a4-152e-4c0a-b3c5-be00ecaab863"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.838Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/sensor-alerts/thresholds","description":"Requirement Reference: TRC.2
\nUse Case: Time & temperature (data loggers) information
\nDescription: Set alert thresholds for sensor monitoring. Defines min/max acceptable values and alert recipients for each sensor type. Critical for temperature-sensitive cargo.
\nPriority: P1
\nAlert Delay: Grace period before triggering alert (prevents false alarms from brief excursions)
\nSeverity Levels:
\nLOW: Informational, no immediate action required
\nMEDIUM: Requires attention, monitor closely
\nHIGH: Critical, immediate action required
\nCRITICAL: Severe, cargo integrity at risk
\nAuthorization: Only consignor, airline, or authorized ACA can set thresholds
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","trace","sensor-alerts","thresholds"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"9d9474c5-bcba-478a-bd5b-1247801b87fa","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Unique request identifier for traceability","key":"X-Request-ID","value":"46eb5fd3-d14d-4b3a-9eab-b31e5609f5d0"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.838Z"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerUnique request identifier for traceability
\n","key":"X-Request-ID","value":"dd381eed-0310-4ad8-b83e-fbccf369cb2a"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.838Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/vehicle-tracking/receipts","description":"Requirement Reference: TRC.3
\nUse Case: Vehicle movement for cargo terminal area
\nDescription: ACS receives GPS location updates from vehicles transporting cargo. Supports real-time tracking via mobile apps or dedicated GPS tracker devices. Used for monitoring vehicle movement within and around airport cargo terminal areas.
\nProcess Flow: Mobile App / Vehicle Tracker → ACS → Stakeholders
\nPriority: P1 (Critical Integration)
\nVehicle Types:
\nTRUCK: Standard cargo truck
\nVAN: Small delivery van
\nFLATBED: Flatbed truck for oversized cargo
\nREFRIGERATED: Temperature-controlled truck
\nCONTAINER: Container truck
\nJourney Types:
\nDELIVERY: Delivering cargo to airport terminal (export)
\nPICKUP: Picking up cargo from airport terminal (import)
\nTRANSFER: Transferring between terminals/warehouses
\nDevice Types:
\nMOBILE_APP: Driver's mobile phone app
\nVEHICLE_TRACKER: Dedicated GPS tracker device
\nTELEMATICS: Vehicle telematics system
\nCoordinate Format: WGS84 decimal degrees
\nValidation Rules:
\nVehicle registration format: {CITY}-{LETTERS}-{NUMBERS}
\nCNIC format: 5-digit district + 7-digit serial + 1-digit check
\nLatitude: -90 to +90
\nLongitude: -180 to +180
\nSpeed: 0 to 150 km/h (reasonable limit for cargo trucks)
\nHeading: 0 to 360 degrees (0=North, 90=East, 180=South, 270=West)
\nUnique request identifier for traceability
\n","key":"X-Request-ID","value":"056e4eda-d55e-427e-8509-68c45f056e96"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.838Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/vehicle-tracking/bulk","description":"Requirement Reference: TRC.3
\nUse Case: Vehicle movement for cargo terminal area
\nDescription: Bulk upload of vehicle location updates. Used when GPS tracker operates in offline mode and syncs accumulated location points periodically, or when mobile app batches updates to reduce cellular data usage.
\nPriority: P1
\nUse Cases:
\nOffline GPS tracker syncing location history
\nMobile app batching to save data/battery
\nHistorical route upload for analysis
\nLimits:
\nMaximum 500 location points per bulk upload
\nMaximum 24-hour time span per upload
\nLocations must be in chronological order
\nUnique request identifier for traceability
\n","key":"X-Request-ID","value":"59df2033-07d0-4a88-9fd8-4428ff93abfc"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)
\n","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request
\n","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.839Z"},{"key":"Content-Type","value":"application/json"}],"url":"https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io/api/v1/trace/geofencing/zones","description":"Requirement Reference: TRC.3
\nUse Case: Vehicle movement for cargo terminal area
\nDescription: Define geofenced zones for airport cargo terminal areas. Geofences trigger alerts when vehicles enter, exit, or dwell in specific zones (loading zones, unloading areas, security checkpoints, etc.).
\nPriority: P1
\nZone Types:
\nLOADING_ZONE: Cargo loading area
\nUNLOADING_ZONE: Cargo unloading area
\nSECURITY_CHECKPOINT: Security screening zone
\nPARKING_AREA: Vehicle parking zone
\nTERMINAL_AREA: General terminal area
\nRESTRICTED_ZONE: Restricted access area
\nGeometry Types:
\nPOLYGON: Multi-point boundary (most common)
\nCIRCLE: Center point + radius
\nEvent Types:
\nENTRY: Vehicle enters zone
\nEXIT: Vehicle exits zone
\nDWELL: Vehicle remains in zone beyond threshold time
\nAuthorization: Only GHA or terminal operators can define zones
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","trace","geofencing","zones"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"481180bf-e555-494f-a650-047cc24a64a8","name":"Success Response","originalRequest":{"method":"POST","header":[{"description":"Unique request identifier for traceability","key":"X-Request-ID","value":"ed464ca6-6633-48a4-96d2-c5609d029b97"},{"description":"Identifier of the sending/requesting system (e.g., GHA-KHI-001, AL-EK)","key":"X-Request-System","value":"{{sender_system_id}}"},{"description":"ISO 8601 timestamp of the request","key":"X-Request-Timestamp","value":"2026-04-05T13:22:13.839Z"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline → ACS (receives FFM) → Distribution to GHA, Customs, PSW, PAA
\nActors: Airline, ACS (System), GHA, Customs, PSW, PAA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created with FFM receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","flight-manifests","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"dbd0f111-a473-43f2-8871-47eb50bc03e2","name":"Success - FFM Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"3feb5be2-37ff-4114-ba89-687865a4b2b3"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline sends XFFM → ACS receives and parses XML → Distribution to GHA, Customs, PSW, PAA
\nActors: Airline, ACS (System), GHA, Customs, PSW, PAA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nMessage Format: IATA Cargo-XML XFFM (Flight Manifest Message)
\nSuccess Response: 201 Created with FFM receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","flight-manifests","xffm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"fbbf87ea-4e21-4fbf-9720-e93d26e2cb42","name":"Success - XFFM Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"303e25c2-d073-4a17-944e-be78b5b32cc0"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline sends FFM (IMP) → ACS receives and parses text → Distribution to GHA, Customs, PSW, PAA
\nActors: Airline, ACS (System), GHA, Customs, PSW, PAA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nMessage Format: IATA Cargo-IMP FFM (Flight Manifest Message)
\nFFM IMP Format:
\nSuccess Response: 201 Created with FFM receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","flight-manifests","ffm"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"8a76a79e-3fb4-4f41-8aa7-f8d913059f9d","name":"Success - FFM IMP Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"984cc0ba-3158-4b5a-909f-9d9dfc816836"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline → ACS (receives FWB) → Distribution to GHA, Customs
\nActors: Airline, ACS (System), GHA, Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created with FWB receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","master-awbs","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"62befb31-436c-4f9b-b25e-8627aa56f91b","name":"Success - FWB Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"59392484-7b89-413f-9e6a-f6113142cc51"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline sends XFWB → ACS receives and parses XML → Distribution to GHA, Customs
\nActors: Airline, ACS (System), GHA, Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nMessage Format: IATA Cargo-XML XFWB (Master AWB Message)
\nSuccess Response: 201 Created with FWB receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","master-awbs","xfwb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"cd8e1798-8b53-43a9-a0e3-7643f5cac025","name":"Success - XFWB Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"a7b8862b-0319-4408-af3d-b8410ecfcc2c"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline sends FWB (IMP) → ACS receives and parses text → Distribution to GHA, Customs
\nActors: Airline, ACS (System), GHA, Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nMessage Format: IATA Cargo-IMP FWB (Master AWB Message)
\nFWB IMP Format:
\nSuccess Response: 201 Created with FWB receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","master-awbs","fwb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"cdd1f59a-adca-418c-80b9-000bcae7c6f2","name":"Success - FWB IMP Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"dfed3f6a-2813-4f73-b387-52502f5209ff"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline → ACS (receives FHL) → Distribution to GHA, Customs
\nActors: Airline, ACS (System), GHA, Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created with FHL receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","house-awbs","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"80bd1ca7-d4ed-4981-985a-20d1457c995f","name":"Success - FHL Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"c32bed95-ddae-4ad8-861d-e012280096f6"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline sends XFZB → ACS receives and parses XML → Distribution to GHA, Customs
\nActors: Airline, ACS (System), GHA, Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nMessage Format: IATA Cargo-XML XFZB (House AWB Message)
\nSuccess Response: 201 Created with FHL receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","house-awbs","xfzb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"ee5801f6-6b32-418c-b7f5-038e1bfe105d","name":"Success - XFZB Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"ba213c24-1384-4d25-881d-9f21d9d442c5"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1
\nUse Case (from Integration Points): Airline sends FFM (Flight Manifest), FWB (Master AWB), and FHL (House AWB) for transit shipments to ACS
\nIntegration Point (from Integration Points): ACS enables Airlines to transmit flight manifest, MAWB, and HAWB data digitally to GHA, Customs, PSW, and PAA
\nProcess Flow: Airline sends FHL (IMP) → ACS receives and parses text → Distribution to GHA, Customs
\nActors: Airline, ACS (System), GHA, Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: AIRLINE_OPERATIONS
\nBusiness Rules:
\nMessage Format: IATA Cargo-IMP FHL (House AWB Message)
\nFHL IMP Format:
\nSuccess Response: 201 Created with FHL receipt ID
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","house-awbs","fhl"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"733612a7-e52a-4cbb-bee4-78ba55e5e4cc","name":"Success - FHL IMP Received","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"156718dc-b376-4dff-8ee1-d41062cc788f"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4GHA.2
\nUse Case (from Integration Points): ACS distributes flight manifest, MAWB, and HAWB data from Airline to GHA
\nIntegration Point (from Integration Points): ACS enables GHA to receive flight manifest, MAWB, and HAWB data digitally from airlines and file in PSW
\nProcess Flow: ACS → Push FFM to GHA
\nActors: ACS (System), GHA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: ACS_SYSTEM
\nBusiness Rules:
\nSuccess Response: 200 OK with push confirmation
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","flight-manifests",":manifestId","push","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-20251202-001","key":"manifestId"}]}},"response":[{"id":"4480297b-9f84-425f-aae8-0c1174ad6425","name":"Success - FFM Pushed to GHA","originalRequest":{"method":"POST","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4GHA.2
\nUse Case (from Integration Points): ACS distributes flight manifest, MAWB, and HAWB data from Airline to GHA
\nIntegration Point (from Integration Points): ACS enables GHA to receive flight manifest, MAWB, and HAWB data digitally from airlines and file in PSW
\nProcess Flow: ACS → Push FWB to GHA
\nActors: ACS (System), GHA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: ACS_SYSTEM
\nBusiness Rules:
\nSuccess Response: 200 OK with push confirmation
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","master-awbs",":awbId","push","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"fwb-20251202-001","key":"awbId"}]}},"response":[{"id":"dbd71434-6ee8-4984-81fa-360ff08745d6","name":"Success - FWB Pushed to GHA","originalRequest":{"method":"POST","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4GHA.2
\nUse Case (from Integration Points): ACS distributes flight manifest, MAWB, and HAWB data from Airline to GHA
\nIntegration Point (from Integration Points): ACS enables GHA to receive flight manifest, MAWB, and HAWB data digitally from airlines and file in PSW
\nProcess Flow: ACS → Push FHL to GHA
\nActors: ACS (System), GHA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: ACS_SYSTEM
\nBusiness Rules:
\nSuccess Response: 200 OK with push confirmation
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","house-awbs",":hawbId","push","gha"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"fhl-20251202-001","key":"hawbId"}]}},"response":[{"id":"2dc9ae4b-3ff2-4422-8aeb-9f384c4d5e81","name":"Success - FHL Pushed to GHA","originalRequest":{"method":"POST","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4GHA.2, TR.I4CUS.3
\nUse Case (from Integration Points): GHA distributes flight manifest, MAWB, and HAWB data to Customs
\nIntegration Point (from Integration Points): ACS enables Customs to receive flight manifest data, MAWB data, and HAWB in digital format for transit cargo
\nProcess Flow: ACS → Push FFM to Customs (WeBOC)
\nActors: ACS (System), Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: ACS_SYSTEM
\nBusiness Rules:
\nSuccess Response: 200 OK with push confirmation
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","flight-manifests",":manifestId","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-20251202-001","key":"manifestId"}]}},"response":[{"id":"f82a130d-7d75-44bf-b62e-bae9bd91006f","name":"Success - FFM Pushed to Customs","originalRequest":{"method":"POST","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4GHA.2, TR.I4CUS.3
\nUse Case (from Integration Points): Customs receives flight manifest, MAWB, and HAWB data for transit shipments
\nIntegration Point (from Integration Points): ACS enables Customs to receive flight manifest data, MAWB data, and HAWB in digital format for transit cargo
\nProcess Flow: ACS → Push FWB to Customs (WeBOC)
\nActors: ACS (System), Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: ACS_SYSTEM
\nBusiness Rules:
\nSuccess Response: 200 OK with push confirmation
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","master-awbs",":awbId","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"fwb-20251202-001","key":"awbId"}]}},"response":[{"id":"9f31ae24-ffff-4e7e-9178-0dd1db6094ea","name":"Success - FWB Pushed to Customs","originalRequest":{"method":"POST","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4GHA.2, TR.I4CUS.3
\nUse Case (from Integration Points): Customs receives flight manifest, MAWB, and HAWB data for transit shipments
\nIntegration Point (from Integration Points): ACS enables Customs to receive flight manifest data, MAWB data, and HAWB in digital format for transit cargo
\nProcess Flow: ACS → Push FHL to Customs (WeBOC)
\nActors: ACS (System), Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: ACS_SYSTEM
\nBusiness Rules:
\nSuccess Response: 200 OK with push confirmation
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","house-awbs",":hawbId","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"fhl-20251202-001","key":"hawbId"}]}},"response":[{"id":"d5848c24-32ba-47f9-ab5b-4f727d61e7aa","name":"Success - FHL Pushed to Customs","originalRequest":{"method":"POST","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1, TR.I4GHA.2
\nUse Case: Query flight manifest details for transit flight
\nProcess Flow: User/System → Query FFM details from ACS
\nActors: GHA, Customs, PSW, PAA, ACS
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: GHA_OPERATIONS, CUSTOMS_OFFICER, PSW_ADMIN, PAA_ADMIN
\nBusiness Rules:
\nQuery Parameters:
\nSuccess Response: 200 OK with manifest details
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","flight-manifests",":flightNumber"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"date","value":"2025-12-03"}],"variable":[{"type":"any","value":"TK-716","key":"flightNumber"}]}},"response":[{"id":"0b6006cf-c997-4c12-89e2-00e1e0d13333","name":"Success - Manifest Retrieved","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I4AL.1, TR.I4GHA.2
\nUse Case: Query complete shipment details by AWB number
\nProcess Flow: User/System → Query shipment details from ACS
\nActors: GHA, Customs, PSW, PAA, ACS
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: GHA_OPERATIONS, CUSTOMS_OFFICER, PSW_ADMIN, PAA_ADMIN
\nBusiness Rules:
\nSuccess Response: 200 OK with shipment details
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","shipments",":awb"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"235-12345678","key":"awb"}]}},"response":[{"id":"4c61fab0-35af-49a4-a09c-82bb86460222","name":"Success - Shipment Retrieved","originalRequest":{"method":"GET","header":[{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5PAA.4
\nUse Case (from Integration Points): PAA receives flight manifest data for statistical purposes
\nIntegration Point (from Integration Points): ACS enables PAA to receive Flight manifest data in digital format for statistical purposes for transit flights
\nProcess Flow: ACS → PAA (push FFM for statistics)
\nActors: ACS (System), PAA (Pakistan Airport Authority)
\nPriority: P2 (Important but not critical)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nPush Strategy:
\nSuccess Response: 200 OK with push confirmation
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","flight-manifests",":id","push","paa"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-20251202-001","key":"id"}]}},"response":[{"id":"2420c7d2-f8ab-4fa4-ad4d-7cf75d5312f8","name":"Success - Pushed to PAA","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"de079532-bb6f-481c-b58e-b490b89c13ff"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5PAA.4
\nUse Case (from Integration Points): PAA receives flight manifest data for statistical purposes
\nIntegration Point (from Integration Points): ACS enables PAA to receive Flight manifest data in digital format for statistical purposes for transit flights
\nProcess Flow: PAA → ACS (query flight statistics)
\nActors: PAA (Pakistan Airport Authority), ACS (System)
\nPriority: P2
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: PAA_OPERATIONS
\nBusiness Rules:
\nQuery Parameters:
\nSuccess Response: 200 OK with flight statistics
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","statistics","paa","flights"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"startDate","value":"2025-12-01"},{"key":"endDate","value":"2025-12-31"},{"key":"airportCode","value":"KHI"},{"key":"transitType","value":"THROUGH"},{"key":"page","value":"1"},{"key":"limit","value":"50"}],"variable":[]}},"response":[{"id":"b4bfb4c3-3c66-48ff-9e11-1727ef1fa384","name":"Success - Flight Statistics","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"79104e8a-0a18-4550-ae09-21c89669473f"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5PAA.4
\nUse Case (from Integration Points): PAA receives flight manifest data for statistical purposes
\nIntegration Point (from Integration Points): ACS enables PAA to receive Flight manifest data in digital format for statistical purposes for transit flights
\nProcess Flow: PAA → ACS (query cargo statistics)
\nActors: PAA, ACS (System)
\nPriority: P2
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: PAA_OPERATIONS
\nBusiness Rules:
\nQuery Parameters:
\nSuccess Response: 200 OK with cargo statistics
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","statistics","paa","cargo"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"startDate","value":"2025-12-01"},{"key":"endDate","value":"2025-12-31"},{"key":"airportCode","value":"KHI"},{"key":"commodityType","value":"Electronics"},{"key":"originRegion","value":"EMEA"},{"key":"destinationRegion","value":"APAC"}],"variable":[]}},"response":[{"id":"6d54c159-0298-4be0-8c43-fadb46cc5424","name":"Success - Cargo Statistics","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"9e95393d-3a47-4539-a5b7-9143b018da17"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5PSW.5
\nUse Case (from Integration Points): PSW receives flight manifest data for statistical purposes
\nIntegration Point (from Integration Points): ACS enables PSW to receive flight Manifest data for statistical purposes for transit flights
\nProcess Flow: ACS → PSW (push FFM for statistics)
\nActors: ACS (System), PSW (Pakistan Single Window)
\nPriority: P2
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nPSW Usage:
\nSuccess Response: 200 OK with push confirmation
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","inbound","flight-manifests",":id","push","psw"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-20251202-001","key":"id"}]}},"response":[{"id":"c2a9b301-12ba-460a-9d5a-c5cbf0fb7d65","name":"Success - Pushed to PSW","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"afbb3139-dfb4-4d81-a39a-4ecf114c7c28"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5PSW.5
\nUse Case (from Integration Points): PSW receives flight manifest data for statistical purposes
\nIntegration Point (from Integration Points): ACS enables PSW to receive flight Manifest data for statistical purposes for transit flights
\nProcess Flow: PSW → ACS (query flight statistics)
\nActors: PSW, ACS (System)
\nPriority: P2
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: PSW_OPERATIONS
\nBusiness Rules:
\nQuery Parameters:
\nSuccess Response: 200 OK with flight statistics
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","statistics","psw","flights"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"startDate","value":"2025-12-01"},{"key":"endDate","value":"2025-12-31"},{"key":"transitCorridor","value":"IST-KHI-SYD"},{"key":"airlineCode","value":"TK"}],"variable":[]}},"response":[{"id":"f1463e5f-1e0d-4f18-8e80-99475ddf9f78","name":"Success - PSW Flight Statistics","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"8c3f4e6a-fe93-4f32-bced-aea87158aa54"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5PSW.5
\nUse Case (from Integration Points): PSW receives flight manifest data for statistical purposes
\nIntegration Point (from Integration Points): ACS enables PSW to receive flight Manifest data for statistical purposes for transit flights
\nProcess Flow: PSW → ACS (query cargo statistics)
\nActors: PSW, ACS (System)
\nPriority: P2
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: PSW_OPERATIONS
\nBusiness Rules:
\nSuccess Response: 200 OK with cargo statistics
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","statistics","psw","cargo"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"startDate","value":"2025-12-01"},{"key":"endDate","value":"2025-12-31"},{"key":"commodityHSCode","value":"8471"},{"key":"originCountry","value":"TR"},{"key":"destinationCountry","value":"AU"}],"variable":[]}},"response":[{"id":"a27bcb66-7bc1-41c3-9d9a-b85293fc2d1d","name":"Success - PSW Cargo Statistics","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"882917ae-29c1-4f4b-b380-0393b1d22c91"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5PSW.5
\nUse Case (from Integration Points): PSW receives flight manifest data for statistical purposes
\nIntegration Point (from Integration Points): ACS enables PSW to receive flight Manifest data for statistical purposes for transit flights
\nProcess Flow: PSW → ACS (query route statistics)
\nActors: PSW, ACS (System)
\nPriority: P2
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: PSW_OPERATIONS
\nBusiness Rules:
\nSuccess Response: 200 OK with route statistics
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","statistics","psw","routes"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"startDate","value":"2025-12-01"},{"key":"endDate","value":"2025-12-31"},{"key":"transitAirport","value":"KHI"}],"variable":[]}},"response":[{"id":"b327ce7e-e3e3-484d-ad74-bfa9c79e3baa","name":"Success - Route Statistics","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"91592775-97a8-442d-808d-5ddede1d752e"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5PSW.5
\nUse Case (from Integration Points): PSW receives flight manifest data for statistical purposes
\nIntegration Point (from Integration Points): ACS enables PSW to receive flight Manifest data for statistical purposes for transit flights
\nProcess Flow: PSW → ACS (query airline statistics)
\nActors: PSW, ACS (System)
\nPriority: P2
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: PSW_OPERATIONS
\nBusiness Rules:
\nSuccess Response: 200 OK with airline statistics
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","statistics","psw","airlines"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[{"key":"startDate","value":"2025-12-01"},{"key":"endDate","value":"2025-12-31"},{"key":"transitAirport","value":"KHI"}],"variable":[]}},"response":[{"id":"1af5cecc-a72a-4824-9fe2-6eb968e24470","name":"Success - Airline Statistics","originalRequest":{"method":"GET","header":[{"key":"X-Request-ID","value":"9e5bee83-4aec-4b38-9adb-9ead3a208c20"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5GHA.6
\nUse Case (from Integration Points): GHA transmits aircraft arrival information for technical stop
\nIntegration Point (from Integration Points): ACS enables Customs, PAA, and PSW to receive aircraft arrival at the airport information digitally for technical stops
\nProcess Flow: GHA → ACS (receives FSU ARR) → Distribution to Customs, PAA, PSW
\nActors: GHA, ACS (System), Customs, PAA, PSW
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: GHA_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","arrivals","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"ada0f5e8-d947-4a39-8c91-c90c22e683c7","name":"Success - Submit Aircraft Arrival - JSON (FSU ARR)","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"beb18eda-09d0-456b-a1f6-9db62e4e35a4"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5GHA.6
\nUse Case (from Integration Points): GHA transmits aircraft arrival information for technical stop
\nIntegration Point (from Integration Points): ACS enables Customs, PAA, and PSW to receive aircraft arrival at the airport information digitally for technical stops
\nProcess Flow: GHA → ACS (receives FSU ARR) → Distribution to Customs, PAA, PSW
\nActors: GHA, ACS (System), Customs, PAA, PSW
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: GHA_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","arrivals","xfsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"dbfc23d1-00ea-4edc-a688-7149d71fae55","name":"Success - Submit Aircraft Arrival - XFSU","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"4cdea5c9-cbfe-47c8-9f6d-e7fe0763192b"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5GHA.6
\nUse Case (from Integration Points): GHA transmits aircraft arrival information for technical stop
\nIntegration Point (from Integration Points): ACS enables Customs, PAA, and PSW to receive aircraft arrival at the airport information digitally for technical stops
\nProcess Flow: GHA → ACS (receives FSU ARR) → Distribution to Customs, PAA, PSW
\nActors: GHA, ACS (System), Customs, PAA, PSW
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: GHA_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","arrivals","fsu"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"2e46da17-429a-4850-a5ae-8dd99e4e4005","name":"Success - Submit Aircraft Arrival - FSU","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"b3b32d28-7bd8-4e96-ae89-159770f6e372"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5GHA.6
\nUse Case (from Integration Points): GHA transmits aircraft arrival information for technical stop
\nIntegration Point (from Integration Points): ACS enables Customs, PAA, and PSW to receive aircraft arrival at the airport information digitally for technical stops
\nProcess Flow: ACS → Customs (push FSU ARR)
\nActors: ACS (System), Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","arrivals",":id","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"arr-tech-20251203-001","key":"id"}]}},"response":[{"id":"d4006185-d911-4727-91e3-229fa90bd714","name":"Success - Push Arrival to Customs","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"bb355e01-6ca7-405f-b29e-60487b07223e"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5GHA.6
\nUse Case (from Integration Points): GHA transmits aircraft arrival information for technical stop
\nIntegration Point (from Integration Points): ACS enables Customs, PAA, and PSW to receive aircraft arrival at the airport information digitally for technical stops
\nProcess Flow: ACS → PAA (push FSU ARR)
\nActors: ACS (System), PAA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","arrivals",":id","push","paa"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"arr-tech-20251203-001","key":"id"}]}},"response":[{"id":"ea00f97b-565d-4329-b429-d3fc9b931c16","name":"Success - Push Arrival to PAA","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"a9f07d3f-b748-4797-9a73-eed7785e1b7b"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I5GHA.6
\nUse Case (from Integration Points): GHA transmits aircraft arrival information for technical stop
\nIntegration Point (from Integration Points): ACS enables Customs, PAA, and PSW to receive aircraft arrival at the airport information digitally for technical stops
\nProcess Flow: ACS → PSW (push FSU ARR)
\nActors: ACS (System), PSW
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","arrivals",":id","push","psw"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"arr-tech-20251203-001","key":"id"}]}},"response":[{"id":"b010efaf-4970-4059-9857-14aae431ed60","name":"Success - Push Arrival to PSW","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"f5cd574a-fc27-4240-86ce-0b2cd3b44410"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E36GHA.7
\nUse Case (from Integration Points): ACS distributes technical stop flight manifest to stakeholders
\nIntegration Point (from Integration Points): ACS distributes GHA-created flight manifest to Airline, Customs, PAA, PSW, and ANF
\nProcess Flow: GHA → ACS (creates FFM) → Distribution to Airline, Customs, PAA, PSW, ANF
\nActors: GHA, ACS (System), Airline, Customs, PAA, PSW, ANF
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: GHA_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","outbound-manifests"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"63235f31-bd8a-4ab9-99d5-3810ceb6d65c","name":"Success - Create Outbound Manifest (Technical Stop)","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"d6b8fa60-7b3f-41bd-af8d-8fb940e7c37f"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E36GHA.7
\nUse Case (from Integration Points): ACS distributes technical stop flight manifest to stakeholders
\nIntegration Point (from Integration Points): ACS distributes GHA-created flight manifest to Airline, Customs, PAA, PSW, and ANF
\nProcess Flow: ACS → Airline (push FFM)
\nActors: ACS (System), Airline
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","outbound-manifests",":id","push","airline"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-tech-20251203-001","key":"id"}]}},"response":[{"id":"222e43be-786f-4b5f-b1b6-04aaf974f508","name":"Success - Push Manifest to Airline","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"f178a212-5ffe-4070-bc62-2866a1eec55a"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E36GHA.7
\nUse Case (from Integration Points): ACS distributes technical stop flight manifest to stakeholders
\nIntegration Point (from Integration Points): ACS distributes GHA-created flight manifest to Airline, Customs, PAA, PSW, and ANF
\nProcess Flow: ACS → Customs (push FFM)
\nActors: ACS (System), Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","outbound-manifests",":id","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-tech-20251203-001","key":"id"}]}},"response":[{"id":"72261271-e954-4f81-bfc8-f0b200ec5946","name":"Success - Push Manifest to Customs","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"a7aadd74-d73b-4be1-82ef-f75ba933ac19"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E36GHA.7
\nUse Case (from Integration Points): ACS distributes technical stop flight manifest to stakeholders
\nIntegration Point (from Integration Points): ACS distributes GHA-created flight manifest to Airline, Customs, PAA, PSW, and ANF
\nProcess Flow: ACS → PAA (push FFM)
\nActors: ACS (System), PAA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","outbound-manifests",":id","push","paa"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-tech-20251203-001","key":"id"}]}},"response":[{"id":"6ffd6995-2ae1-4f84-8066-0f8f1754ea8c","name":"Success - Push Manifest to PAA","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"b85576d8-e4c2-4114-8c75-fc0908b9879f"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E36GHA.7
\nUse Case (from Integration Points): ACS distributes technical stop flight manifest to stakeholders
\nIntegration Point (from Integration Points): ACS distributes GHA-created flight manifest to Airline, Customs, PAA, PSW, and ANF
\nProcess Flow: ACS → PSW (push FFM)
\nActors: ACS (System), PSW
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","outbound-manifests",":id","push","psw"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-tech-20251203-001","key":"id"}]}},"response":[{"id":"4787e7ca-7fd8-498c-b6c6-7baaedecde9c","name":"Success - Push Manifest to PSW","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"d99082ed-8f53-4f51-80fa-aa7ec6f4d050"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E36GHA.7
\nUse Case (from Integration Points): ACS distributes technical stop flight manifest to stakeholders
\nIntegration Point (from Integration Points): ACS distributes GHA-created flight manifest to Airline, Customs, PAA, PSW, and ANF
\nProcess Flow: ACS → ANF (push FFM)
\nActors: ACS (System), ANF
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","outbound-manifests",":id","push","anf"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"ffm-tech-20251203-001","key":"id"}]}},"response":[{"id":"2cd33dbf-6b96-4c52-92cc-884c50222600","name":"Success - Push Manifest to ANF","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"a5967e3f-1d8c-4fae-b00b-325791df86c6"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E37GHA.8
\nUse Case (from Integration Points): GHA transmits departure status for technical stop
\nIntegration Point (from Integration Points): ACS enables GHA to transmit departure status from technical stop to Airline, Customs, PAA, and PSW digitally
\nProcess Flow: GHA → ACS (receives FSU DEP) → Distribution to Airline, Customs, PAA, PSW
\nActors: GHA, ACS (System), Airline, Customs, PAA, PSW
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: GHA_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","departures"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"e2e56c7f-b506-4bed-acbd-279d07de17b6","name":"Success - Submit Departure Status (FSU DEP)","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"3af3b5dd-800f-4046-b055-c623289e789c"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E37GHA.8
\nUse Case (from Integration Points): GHA transmits departure status for technical stop
\nIntegration Point (from Integration Points): ACS enables GHA to transmit departure status from technical stop to Airline, Customs, PAA, and PSW digitally
\nProcess Flow: ACS → Airline (push FSU DEP)
\nActors: ACS (System), Airline
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","departures",":id","push","airline"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"dep-tech-20251203-001","key":"id"}]}},"response":[{"id":"a54df518-1bf9-4b19-955e-256a6b6e675d","name":"Success - Push Departure to Airline","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"fe70c71c-c819-4277-86d4-b0b279108bd1"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E37GHA.8
\nUse Case (from Integration Points): GHA transmits departure status for technical stop
\nIntegration Point (from Integration Points): ACS enables GHA to transmit departure status from technical stop to Airline, Customs, PAA, and PSW digitally
\nProcess Flow: ACS → Customs (push FSU DEP)
\nActors: ACS (System), Customs
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","departures",":id","push","customs"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"dep-tech-20251203-001","key":"id"}]}},"response":[{"id":"c93409e2-41c7-4755-8f14-a4abef6281fb","name":"Success - Push Departure to Customs","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"e728d422-8648-4275-97b3-435dbff5966a"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E37GHA.8
\nUse Case (from Integration Points): GHA transmits departure status for technical stop
\nIntegration Point (from Integration Points): ACS enables GHA to transmit departure status from technical stop to Airline, Customs, PAA, and PSW digitally
\nProcess Flow: ACS → PAA (push FSU DEP)
\nActors: ACS (System), PAA
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","departures",":id","push","paa"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"dep-tech-20251203-001","key":"id"}]}},"response":[{"id":"3374e411-3237-439c-aba1-714375786629","name":"Success - Push Departure to PAA","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"c6bb96fb-9a9f-4503-be37-b4576f4b40f1"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.E37GHA.8
\nUse Case (from Integration Points): GHA transmits departure status for technical stop
\nIntegration Point (from Integration Points): ACS enables GHA to transmit departure status from technical stop to Airline, Customs, PAA, and PSW digitally
\nProcess Flow: ACS → PSW (push FSU DEP)
\nActors: ACS (System), PSW
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: SYSTEM_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 200 OK
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","technical-stop","departures",":id","push","psw"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[{"type":"any","value":"dep-tech-20251203-001","key":"id"}]}},"response":[{"id":"010e0945-efcb-4821-b213-ba6bfc670e47","name":"Success - Push Departure to PSW","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"3db1a681-e5e5-48e3-8bc2-4d4d29614170"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"BearerRequirement Reference: TR.I9GHA.9
\nUse Case (from Integration Points): GHA confirms arrival of transit shipments and transfer to transit shed
\nIntegration Point (from Integration Points): ACS enables GHA to transmit transit consignment cargo received (RCF) and transfer to transit shed information to Customs and PSW digitally
\nProcess Flow: GHA → ACS (receives FSU RCF) → Distribution to Customs, PSW
\nActors: GHA, ACS (System), Customs, PSW
\nPriority: P1 (Critical Integration)
\nAuthentication: OAuth 2.0 with JWT Bearer token. Required role: GHA_CARGO_OPERATIONS
\nBusiness Rules:
\nValidation Rules:
\nSuccess Response: 201 Created
\n","auth":{"type":"bearer","bearer":{"basicConfig":[{"key":"token","value":"{{jwt_token}}"}]},"isInherited":true,"source":{"_postman_id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","id":"9d0cdaed-05d9-4c9f-a83e-b3eb39ef35f1","name":"PSW ACS Jan 22","type":"collection"}},"urlObject":{"path":["api","v1","transit","cargo-handling","received-confirmations","receipts"],"host":["https://1a557de0-701c-477d-bedd-433520441dae.mock.pstmn.io"],"query":[],"variable":[]}},"response":[{"id":"b0cfb4c9-a837-4451-93aa-b11f3988b450","name":"Success - Submit Cargo Received - JSON (FSU RCF)","originalRequest":{"method":"POST","header":[{"key":"X-Request-ID","value":"04a4431a-f22e-4cfd-8cb9-ecb32d1bd0d0"},{"key":"Content-Type","value":"application/json"},{"key":"Accept","value":"application/json"},{"description":"Added as a part of security scheme: bearer","key":"Authorization","value":"Bearer