GET /terminals/terminal_id/eod-reports

  • Updated on Sep 19, 2025
  • Published on Sep 10, 2025
  • 3 minute(s) read
Prev Next

GET /terminals/{terminal_id}/eod-reports

Get End of Day (EOD) report for a specific terminal. The reports are accessed from the cloud, so the terminal does not need to be connected.

Step 1 - Request

GET /v1/card-present/terminals/T650m-451-962-212/eod-report 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

terminal_id (url)

varchar(35)

e.g. T650m-451-962-212

NO

metadata

json(1024)

Optional field that can be used for debugging, filtering linking to other systems. It contains custom vendor, POS, customer or order details in JSON format. (e.g.
{"note": "Refund for overcharge"}, {"salesforce_id": "SF123456"}, {"server": "dev"}, {"partner": "Shopify", "order_id": "98765"})

YES

Step 2 - Response

HTTP/1.1 200 OK
Content-Type: application/json

[
    {
        "request_timestamp": "2025-03-26T09:43:27+01:00",
        "currency": "GBP",
        "site_branch_id": "London",
        "payment_method": "sales",
        "pos_location": "POS-25",
        "operator_id": "994228",
        "status": "Success",
        "requested_amount": 71.45,
        "transaction_id": "RXP9YZRPLR6KZEJ5",
        "terminal_id": "T650M-451-962-212-MOHSIN",
        "metadata": {
            "order_number": "6680893730"
        }
    },
    {
        "request_timestamp": "2025-03-26T09:45:07+01:00",
        "currency": "GBP",
        "site_branch_id": "London",
        "payment_method": "sales",
        "pos_location": "POS-25",
        "operator_id": "291789",
        "status": "Success",
        "requested_amount": 89.63,
        "transaction_id": "RXP9YZRP6KNPL3Q5",
        "terminal_id": "T650M-451-962-212-MOHSIN",
        "metadata": {
            "order_number": "2061073302"
        }
    }
]

Field Name

Type

Description

Nullable

Reports[]

json

Array of reports. Returns [] if there are no records.

   id

varchar(36)

GUID  (e.g., 550e8400-e29b-41d4-a716-446655440000)

NO

   mime_type

varchar(50)

String (e.g., text/csv)

NO

   report_type

varchar(16)

String e.g., EOD_REPORT

NO

   report_name

varchar(255)

String (e.g., EOD Report T650m-451-962-212 13/03/2025)

NO

   filename

varchar(255)

String (e.g., 2025-03-13-T650m-451-962-212-eod-report.csv)

NO

   created_at

datetime

ISO 8601 datetime string (e.g., 2025-02-02T14:43:59+01:00)

NO

Errors

400 Bad Request

Missing authorization header

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 <encoded_api_key:secret_key>."
    }
}

401 Unauthorized

Acquirer token not found

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

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

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 <encoded api_key:secret_key>."
    }
}

403 Forbidden

API key or secret key is invalid

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 terminal_id

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

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

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."
    }
}