​Retrieve End-of-Service (EOS) Devices

Devices that have reached their EOS status pose risks such as lack of vendor support, potential security vulnerabilities, and compatibility issues. By using this API, you can:

• Identify devices that have reached their EOS date.
• Plan for device replacements or upgrades before issues arise.
• Integrate EOS data into dashboards for visibility and reporting.

​Example API

• Ensure you have a valid access token. If you do not, please referrer to the authentication section.
• The devices API provides a filter for device life-cycle status, it can be accessed with the following example:

curl -X GET https://api.securithings.com/v1/devices?lifecycleStatus=eos&limit=100 \
     -H "Accept: application/json" \
     -H "Authorization: Bearer <token>"

The response will contain up to 100 EOS devices.

Key fields to note are status and eosDate under compliance.lifecycle.

{
  "devices": [
    {
      "id": "...",
      "name": "...",
      "vendor": "...",
      "model": "...",
      "firmwareVersion": "...",
      "deviceType": "...",
      "compliance": {
        "lifecycle":{
          "status": "eos",
          "eosDate": "2024-01-31T23:59:59Z"
        }
      },
      "network": {...},
      "status": "...",
      "lastSeen": "...",
      "deviceSources": [...],
      "sites": [...]
    }
    ...
  ],
  "total": 100
}

​Notes and Limitations

• Data Refresh Rate: The EOS data is updated daily. Ensure you schedule API calls accordingly.
• Rate Limiting: The API has a rate limit of 1 requests per second. Exceeding this limit will result in a 429 Too Many Requests error.
• Time Zone: All timestamps are in UTC. Ensure your application adjusts for local time zones if necessary.
• EOS Status: Devices marked as "End of Support" are determined based on lifecycle data available in the system. SecuriThings collaborates with vendors to ensure the accuracy of this data. The information is derived from the data shared by the vendors.