`admin_user_requests`

Lists user requests for the admin screen. It is a GraphQL query returning [UserRequest], and needs the ADMIN role — see Endpoint and authentication.

Input

input: AdminUserRequestInput!

Field	Type	Required	Description
`limit`	`Int`	No	Page size. Defaults to 10.
`last_id`	`String`	No	The `id` of the last row of the previous page. Defaults to `""` (first page).
`sort`	`UserRequestsSortInput`	No	`field` (only `INSERTED_AT`, the default) and `direction` (`DESC` by default). The same type the requester list uses.
`code`	`String`	No	Prefix search, not case-sensitive. A full code returns exactly one request; `fur1234` narrows. Blank is ignored.
`claimed`	`Boolean`	No	`true`: every fee is `paid`. `false`: a fee is still unpaid, or the request has no fees yet. Leave out for both.

The two filters work together and with last_id paging.

The admin list always sends claimed: false

A request stays on it until add_passenger_fee has applied every one of its fees. Requests with no fees yet — still PENDING, IN_CHARGE, or quoted before fees existed — stay on it too.

There is no status filter, so claimed: false returns requests in every status, not only RESOLVED ones. Use each fee's paid to show which fees are left to apply.

Query
query {
  admin_user_requests(input: { limit: 20, claimed: false, code: "FUR1234" }) {
    id code status amount currency corporate_amount personal_amount
    fees { id fee_type leg price corporate_amount paid }
  }
}

Every field of the UserRequest object is available.

Errors

This call has no errors of its own. It can return Middleware Errors — UNAUTHORIZED for a caller without the ADMIN role.

Input​

Errors​

Input

Errors