@ -56,11 +60,11 @@ an API key. You can create read-write and read-only API keys in the
<tbody>
<tr>
<td>Regular API key</td>
<td>Have full access to all documented API endpoints.</td>
<td>Has full access to all documented API endpoints.</td>
</tr>
<tr>
<td>Read-only API key</td>
<td>Only work with the <ahref="#list-checks">Get a list of existing checks</a> endpoint. Some fields are omitted from the API responses.</td>
<td>Only works with the <ahref="#list-checks">Get a list of existing checks</a>and <ahref="#get-check">Get a single check</a>endpoints. Some fields are omitted from the API responses.</td>
</tr>
</tbody>
</table>
@ -599,9 +603,78 @@ check that was just deleted.</p>
</code></pre></div>
<h2class="rule"id="list-pings">Get a list of checks's logged pings</h2>
[Get a list of checks's logged pings](#list-pings) | `GET SITE_ROOT/api/v1/checks/<uuid>/pings/`
[Get a list of existing integrations](#list-channels) | `GET SITE_ROOT/api/v1/channels/`
## Authentication
@ -25,8 +26,8 @@ an API key. You can create read-write and read-only API keys in the
Key Type | Description
-------------------|------------
Regular API key | Have full access to all documented API endpoints.
Read-only API key | Only work with the [Get a list of existing checks](#list-checks) endpoint. Some fields are omitted from the API responses.
Regular API key | Has full access to all documented API endpoints.
Read-only API key | Only works with the [Get a list of existing checks](#list-checks) and [Get a single check](#get-check) endpoints. Some fields are omitted from the API responses.
The client can authenticate itself by sending an appropriate HTTP
request header. The header's name should be `X-Api-Key` and