What is a request?

High-level definition

A Request captures the act of asking for a refund (or related operation) for a given ticket. It contains who requested it, when, how it was processed, and links back to the underlying Document. Requests progress through statuses and may reference waivers or manual processing references.

Key concepts

• Identity: id, ticketNum, pnr.
• Ownership & channel: requestedBy, agent, travelAgencyId, gds.
• Financial context: totalFare, currency, fop (form of payment).
• Timeline & status: issueDate, refundRequestDate, status.
• Processing details: manuallyRefundedVia, manuallyRefundedBspDocument, waiver, freeText.
• Relation: document — the ticket this request is about.

Typical queries

Fetch a request and its document:

query GetRequest($id: Int!) {
    requests(filter: { id: $id }) {
        edges {
            node {
                id
                status
                ticketNum
                requestedBy {
                    id
                    email
                }
                document {
                    id
                    ticketNum
                    pnr
                }
            }
        }
    }
}

List requests with filters and pagination (fields depend on your schema):

query Requests($filter: RequestFilter, $limit: Int = 25, $offset: Int = 0) {
    requests(filter: $filter, limit: $limit, offset: $offset) {
        pageInfo {
            total
            hasNextPage
        }
        edges {
            cursor
            node {
                id
                status
                ticketNum
            }
        }
    }
}

When to use

• To track a user- or agent-initiated refund action.
• To audit who requested, when, and under what terms (e.g., waiver).