Hi Vineet,

We would like to get logs from LinkPOS ingested into Splunk.

Is this something we can discuss?

Regards,

William

Team Leader

Technology Services

Hi William

Good afternoon Vineet,

Thank you for getting in touch.

Before we go ahead with the configuration can you please expand on the mechanism/method you’ll be using to forward over the logs to Splunk.

If we can review an example of the logs this will allow me to answer the queries you had regarding which logs and fields to include.

Timestamp format can be epoch.

All the best,

Jonathan

Good morning Vineet,

Thanks for following up and apologies for the delay.

Can you please elaborate on the API endpoints available in this case, while we can provide forwarding via HEC it would be preferable to manage the configuration and deployment centrally.

Thank you for your assistance again.

All the best,

Jonathan

Bula Jonathan,

We can build the following API's in LinkPOS that can expose the following endpoints for log retrieval:  

1. Authentication Endpoint – Generates a bearer token for secure access.
   
   1. Method: POST
   2. URL: https://[linkpos-server]/api/auth/token
   3. Auth: Username + Password or API Key
2. Event Logs Endpoint – Returns requested logs in JSON format, filtered by date/time or log type.
   1. Method: GET
   2. URL: https://[linkpos-server]/api/logs/events
   3. Parameters:
   4. startDateTime 
   5. endDateTime
   6. logType (e.g., login, error, processRun)
3. Error Logs Endpoint – For application errors only.
   1. Method: GET
   2. URL: https://[linkpos-server]/api/logs/errors
4. Automated Process Logs Endpoint – Includes backup times, scheduler runs, invoice postings, etc.
   1. Method: GET
   2. URL: https://[linkpos-server]/api/logs/processes

If you prefer, we can send logs directly to your HEC endpoint instead, but centralised management through your configuration is fine from our side as long as API requests are scheduled and handled securely.

Do note that building this into our POS application specifically for KPMG will incur development costs of 2 days, plus upgrade costs for your KPMG Administration and Advisory company.

We can provide this once we are clear about all the details. Please confirm your preferred approach so we can proceed.

Vinaka,
Vineet Ram
222 0085

Hi Vineet,

Thank you for clarifying.

If you wouldn’t mind sending over a quote with the details, I will be able to send this on to the relevant authority for review and/or approval if that’s the way we decide to go.

All the best,

Jonathan

Bula Vineet,

Please find attached PO for API, build, test and deployment.

Regards,
Shane

Added case to project and to Licence Portal.

*** Tems Discussion ***

1. The change will be available in version: 16.00

2. The following changes were made (Include Database object names, Program classes, and any other relevant information):

1. Added a new REST API called "Event-Log" to the LinkSOFT suite
2. The API follows the same mechanism as the Standard LinkSOFT API. Details in 3. below.
3. Figure 1 shows the API Call instructions using Postman
   1. The API can be called using the REST API URL: "{{apiurl}}/api/security/event-log?tokenId=1AEAF8A9-21FD-4792-9BAA-5C77AEA15342&startDateTime=2025/07/31 15:00&endDateTime=2025/07/31 15:59&Status=Information"
   2. The Parameters are:
      1. TokenID which is created in menu "Global Administration ~> Security Token" (see item 1 in figure 1) 
      2. startDateTime - This is the filter for event log entries. (see item 2 in figure 1) 
      3. endDateTime - This is the filter for event log entries . (see item 2 in figure 1) 
      4. status - This is the filter for event log entries. (see item 3 in figure 1). You can leave this field blank if you want all Status.
   3. If the API call is successful, the result is returned in JSON format (see item 4 in figure 1)
   4. If the API call is not successful, the status is "false" and the "data" contains the reason for failure 
      

3. Affected Areas:

1. New API call

4. The issue was caused by:

1. Customer Request

5. Other Relevant Notes: 
6. Next Step (Review and System Test (Developer) -> UAT (Quality) -> Documentation): Release.

PART B - Development Reference (Place descriptor for objects changed):

Figure 1 - POSTMAN API Test Results

1. <add key="API.RateLimit.RequestsPerMinute" value="5" />
2. <add key="API.DataLimit.KBPerMinute" value="10240" />

The purpose is to allow users to LIMIT the API "Requests Per minute" and the "Data Size Per Minute". These limits apply to individual actions. Users can change this as required.

These throttling limits are important security concerns and can be used to limit API calls based on requirements.

Default values are shown above.