POST /accounts/{account_id}/workers/observability/telemetry/keys
List all the keys in your telemetry events.
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
account_id |
String | Yes |
Your Cloudflare account ID. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
datasets[] |
Array | No |
Leave this empty to use the default datasets |
filters[] |
Array | No |
Apply filters to narrow key discovery. Supports nested groups via kind: 'group'. Maximum nesting depth is 4. |
to |
Number | No | |
limit |
Number | No |
Advanced usage: set limit=1000+ to retrieve comprehensive key options without needing additional filtering. |
needle |
Object | No |
Search for a specific substring in any of the events |
needle.value |
String | Yes | |
needle.matchCase |
Boolean | No | |
needle.isRegex |
Boolean | No | |
keyNeedle |
Object | No |
If the user suggests a key, use this to narrow down the list of keys returned. Make sure matchCase is false to avoid case sensitivity issues. |
keyNeedle.value |
String | Yes | |
keyNeedle.matchCase |
Boolean | No | |
keyNeedle.isRegex |
Boolean | No | |
from |
Number | No |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.