ezeio2:apiref:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
ezeio2:apiref:start [2022-08-11 17:14] – [Version 1 API] andrehezeio2:apiref:start [2026-06-18 21:16] (current) – andreh
Line 11: Line 11:
  
 All API calls require authentication using Digest Auth (RFC 2617). The API ID number shall be used as the Digest Auth Username, and the API key shall be used as the Password. All API calls require authentication using Digest Auth (RFC 2617). The API ID number shall be used as the Digest Auth Username, and the API key shall be used as the Password.
 +
 +Alternatively, credentials can be supplied in "ezeAPIkey" and "Authorization" Bearer token headers respectively.
  
 All API calls require HTTPS using TLS v1.2 or TLS v1.3. Calls via unencrypted HTTP are not allowed. All API calls require HTTPS using TLS v1.2 or TLS v1.3. Calls via unencrypted HTTP are not allowed.
Line 37: Line 39:
  
 === Example code === === Example code ===
 +This example shows how to call the "status" API using CURL.
 +<code php>
 +curl -H "ezeAPIkey: 00000" -H "Authorization: Bearer 12345abcde12345abcde12345abcdeff" https://api.eze.io/v1/status/ABC000
 +</code>
 +
 This example shows how to call the "syslog" API endpoint using PHP. This example shows how to call the "syslog" API endpoint using PHP.
  
Line 82: Line 89:
 </code> </code>
  
-Below is a minimal example using Python+Below is a minimal example fetching current status using Python
  
 <code python ezeioAPIexample.py> <code python ezeioAPIexample.py>
  • ezeio2/apiref/start.1660238051.txt.gz
  • Last modified: 2022-08-11 17:14
  • by andreh