# Gather information when approaching at the forecourt **POST /gas-stations/{gasStationId}/approaching** This request will: * Return a list of paymentMethods of the user which can be used at the gas station. * Return up-to-date price information (price structure) at the gas station. * Return a list of pumps available at the gas station together with the current status (free, inUse, readyToPay, outOfOrder). No pumps might be returned if the list of payment methods is empty. The approaching is a necessary first api call for connected fueling. Without a valid approaching the [get pump](#operation/GetPump) and [wait for status change](#operation/WaitOnPumpStatusChange) calls may be answered with a `403 Forbidden` status code. An approaching is valid for one fueling only and can't be reused. If a long (not further disclosed time) has passed, the approaching is also invalidated. So if the client is receiving a `403 Forbidden` on the above mentioned calls, a new approaching has to be issued, this can be done transparent to the user. Other than authorization, the most common error states encountered should be: * 404, if the gas station does not exist or ConnectedFueling is not available at this station * 502, if there was a communication failure with a third party (e.g. the gas station in question fails to respond). Retry is possible * 503, if ConnectedFueling is available, but the site is offline ## Servers - Production server (stable release 2025-1): https://api.pace.cloud/fueling/2025-1 (Production server (stable release 2025-1)) ## Authentication methods - O auth2 - Oidc ## Parameters ### Path parameters - **gasStationId** (string(uuid)) Gas station ID ### Query parameters - **compile[openingHours]** (boolean) Reduces the opening hours rules. After compilation, only rules with the action open will remain in the response. ## Responses ### 201 Created #### Body: application/vnd.api+json (object) - **data** (object) - **included** (array[object]) ### 400 Bad request #### Body: application/vnd.api+json (object) - **errors** (array[object]) ### 401 OAuth token missing or invalid or a linked identity is missing. Linked identity missing is a special case where you need to make sure that the user has additionally logged in / authorized with a third-party. This is not relevant for most use-cases. The specific error code that identifies a missing linked identity is `missing-linked-identity` Example: ``` { "errors": [ { "id": "cbgmhslmp1o9or9kh1p0", "title": "Missing linked identity for authorized access", "detail": "Linked identity is needed to access this resource, please check why the user does not have a linked identity", "status": "401", "code": "missing-linked-identity" } ] } ``` #### Body: application/vnd.api+json (object) - **errors** (array[object]) ### 404 Resource not found #### Body: application/vnd.api+json (object) - **errors** (array[object]) ### 406 The specified accept header is invalid #### Body: application/vnd.api+json (object) - **errors** (array[object]) ### 410 Resource is gone #### Body: application/vnd.api+json (object) - **errors** (array[object]) ### 415 The specified content type header is invalid #### Body: application/vnd.api+json (object) - **errors** (array[object]) ### 500 Internal server error #### Body: application/vnd.api+json (object) - **errors** (array[object]) ### 502 Error occurred while communicating with PACE services #### Body: application/vnd.api+json (object) - **errors** (array[object]) ### 503 Error occurred while communicating with gas station network #### Body: application/vnd.api+json (object) - **errors** (array[object]) [Powered by Bump.sh](https://bump.sh)