--- title: "GET /terminals/terminal_id/eod-reports?date-date" slug: "eod-reports-data" updated: 2025-09-19T15:11:52Z published: 2025-09-19T15:11:52Z canonical: "api-docs.blinkpayment.co.uk/eod-reports-data" --- > ## Documentation Index > Fetch the complete documentation index at: https://api-docs.blinkpayment.co.uk/llms.txt > Use this file to discover all available pages before exploring further. # GET /terminals/terminal_id/eod-reports?date-date GET /terminals/{terminal_id}/eod-reports?date={date} Get End of Day (EOD) report of a specific terminal by specifying a date in format of YYYY-MM-DD. The reports are accessed from the cloud, so the terminal does not need to be connected. ## Step 1 - Request Code SnippetData Dictionary ```json GET /v1/card-present/terminals/T650m-451-962-212/eod-reports?date=2025-07-24 HTTP/1.1                         Host: api.blinkpayment.co.uk                     Content-Type: application/json Authorization: Basic ACCESS_TOKEN    # from Blink pos_api_key:pos_api_secret User-Agent: AcmeApp/1.2.0 (ReactNative; Android 11+; POS2.0+; Build/123) {} ``` | **Field Name** | **Type** | **Description** | **Nullable** | | --- | --- | --- | --- | | **Content-type (header)** | varchar(50) | `application/json` | NO | | **Authorization (header)** | varchar(512) | Authorization header for authenticating the request made up of **pos_api_key** and **pos_api_secret**. (e.g., `Basic ZjdkNDcxNjYtMThhYy00????`) | NO | | **User-Agent (header)** | varchar(255) | A brief overview of the app or software, version and comments related to the software stack and minimum client specifications. e.g. `AcmeApp/1.2.0 (ReactNative; Android 11+; POS2.0+; Build/123)` | NO | | **device_id (url)** | varchar(35) | e.g. `T650m-451-962-212` | NO | | **date (url)** | varchar(35) | e.g. `2025-03-24` | NO | ## Step 2 - Response Code SnippetData Dictionary ```json HTTP/1.1 200 OK Content-Type: application/json [    {        "request_timestamp": "2025-03-24T08:03:01+01:00",        "currency": "GBP",        "site_branch_id": "London",        "payment_method": "sales",        "pos_location": "POS-25",        "operator_id": "988483",        "status": "Success"        "requested_amount": 25.7,        "transaction_id": "6XM32K8MVKE62EWX",        "terminal_id": "T650M-451-962-212-MOHSIN",        "metadata": {            "order_number": "7680961466"        },    },    {        "request_timestamp": "2025-03-24T08:56:44+01:00",        "currency": "GBP",        "site_branch_id": "London",        "payment_method": "sales",        "pos_location": "POS-25",        "operator_id": "141243",        "status": "Failure",        "requested_amount": 89.19,        "transaction_id": "K5N43PZJ6GJ48GW5",        "terminal_id": "T650M-451-962-212-MOHSIN",        "metadata": {            "order_number": "5413683484"        }    } ] ``` | Field Name | Type | Description | **Nullable** | | --- | --- | --- | --- | | **Content-Type** | varchar(50) | String (e.g., `text/csv`) | NO | | **Content-Disposition** | varchar(255) | file download with a meaningful filename. | NO | | **Content-Length** | varchar(15) | Size of the file in bytes (e.g., `12221`) | NO | ## Errors ## **400 Bad Request** ### **Missing authorization header** ```json HTTP/1.1 400 Bad Request   Content-Type: application/json   {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "Authorization": "The Authorization header is required and must be provided in the format: Basic ."    } } ``` ## **401 Unauthorized** ### **Acquirer token not found** ```json HTTP/1.1 401 Unauthorized   Content-Type: application/json   {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "acquirer_token": "The acquirers token was not found in our system. Please contact the support team."    } } ``` ### **Invalid acquirer Token** ```json HTTP/1.1 401 Unauthorized   Content-Type: application/json   {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "acquirer_token": "The acquirers token provided is invalid in our system. Please contact the support team."    } } ``` ### **Invalid authorization header** ```json HTTP/1.1 401 Unauthorized   Content-Type: application/json   {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "Authorization": "The provided Authorization header is invalid. Ensure it follows the correct format: Basic ."    } } ``` ## **403 Forbidden** ### **API key or secret key is invalid** ```json HTTP/1.1 403 Forbidden   Content-Type: application/json   {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "Authorization": "The provided api_key or secret_key is invalid. Please ensure the credentials are correct and try again."    } } ``` ## **404 Not Found** ### **Invalid date** ```json HTTP/1.1 404 Not Found Content-Type: application/json {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "terminal_id": "The terminal_id provided is invalid in our system. Please contact the support team."    } } ``` ## **422 Unprocessable Entity** ### **Invalid terminal_id** ```json HTTP/1.1 422 Unprocessable Entity   Content-Type: application/json {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "date": "The date must be a valid ISO 8601 datetime string (e.g., 2025-02-02)."    } } ``` ### **Invalid terminal_id** ```json HTTP/1.1 422 Unprocessable Entity   Content-Type: application/json {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "terminal_id": "The terminal_id must be a valid string with a maximum length of 35 characters."    } } ``` ## **500 Internal Server Error** ### **Generic error** ```json HTTP/1.1 500 Internal Server Error   Content-Type: application/json   {    "result": "FAILURE",    "message": "Field validation failed",    "errors": {        "We're experiencing an issue with our server, but rest assured our team is already working to resolve it. Please try again, and we apologize for the inconvenience."    } } ```