GET /accounts/{account_id}/cloudforce-one/events/graph
Expands the single-level relationship neighborhood of one or more seed nodes (event, indicator, or tag) from R2 Data Catalog. Seeds use compact id format (type:uuid), e.g. "event:550e8400-...". Multi-seed requests merge and deduplicate results server-side. Hydrates neighbor entities with summary data from Durable Objects. Supports filtering by relationship type and dataset scope.
Servers
- https://api.cloudflare.com/client/v4
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
account_id |
String | Yes |
Account ID. |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
datasetIds[] |
Array | No |
Comma-separated dataset UUIDs to restrict neighbor scope. Intersected with ACL grants. |
seeds[] |
Array | No |
Comma-separated compact seed ids (type:uuid). Example: seeds=event:550e8400-...,indicator:661fa920-... Provide 1–50 entries; omitting seeds returns 400. |
limit |
Number | No |
Max neighbors per seed (default: 100, max: 1000). Values above 1000 return 400. |
direction |
String | No |
Edge direction relative to each seed: out (seed→neighbors), in (neighbors→seed), both (default). |
max_nodes |
Number | No |
Total accumulated node cap across all seeds (default: 500, max: 1000). Values above 1000 return 400. |
expand[] |
Array | No |
Comma-separated list of response sections to expand (hydrate). Allowed: |
hydration |
String | No |
Hydration strategy for neighbor nodes when expand=nodes is set. r2_join (default): use R2 JOIN query + DO fallback. do_only: use plain R2 query + hydrate all neighbors via Durable Objects. |
relationshipTypes[] |
Array | No |
Comma-separated relationship types to filter by. Allowed: tagged_with, appears_in, related_to, caused_by, attributed_to. |
cursor |
String | No |
Opaque pagination token. Only valid when seeds has exactly 1 entry; 400 otherwise. |
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.