# Get Shipment Charges

Retrieve the charges an integration holds for a shipment. Call this before paying a facility that has an `integration` block, then submit the returned charges in the payment request. Build the request from the `operations` and `queryFields` advertised on that block.
Three outcomes are possible. Charges are returned and must be paid through `integrationCharges`. An `alertMessage` of `REDIRECT_TO_STANDARD_FLOW` means the integration does not handle this shipment, and it should be paid directly with no `integrationCharges`. A `404` reporting no charges means the integration handled the shipment and nothing is payable, so no payment should be submitted.

Endpoint: GET /facility/{facilityId}/lookup
Version: 1.0.0
Security: bearerAuth, appId

## Path parameters:

  - `facilityId` (integer, required)
    Facility identifier.

## Query parameters:

  - `operation` (string, required)
    One of the facility's `integration.operations` values.

  - `queryFields` (string, required)
    Comma separated field keys, ordered to match `queryValues`.

  - `queryValues` (string, required)
    Comma separated values, ordered to match `queryFields`.

## Response 200 fields (application/json):

  - `dynamicFields` (array)
    Charge rows returned by the integration.

  - `alertMessage` (object)
    An advisory returned when retrieving charges.

  - `alertMessage.type` (string)
    Advisory type.
    Example: error

  - `alertMessage.message` (string)
    `REDIRECT_TO_STANDARD_FLOW` means the integration does not handle this shipment and it should be paid directly.
    Example: REDIRECT_TO_STANDARD_FLOW

## Response 401 fields (application/json):

  - `errors` (array)
    Error messages.

## Response 404 fields (application/json):

  - `errors` (array)
    Error messages.