Studio Project workflows for Kentik devices, sites, and site markets
Kentik is a network observability platform for NetFlow analytics, DDoS detection, and infrastructure monitoring.
This project provides an OpenAPI spec for automating against Kentik's Device and Site APIs via an Integration Model, plus a Studio Project of CRUD workflows built on that model.
| Asset | Description |
|---|---|
| OpenAPIs/ | Kentik Device & Site API OpenAPI spec — curated -latest plus the two official dated specs it was combined from |
| Studio Projects/ | Itential Platform project containing the Devices/Sites/Site Markets CRUD workflows |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
Kentik Device & Site API:latest Integration Model | Required to run the Studio Project below |
Note: This project does not require Itential Gateway. All API calls are made directly from Itential Platform to Kentik's REST API.
Import kentik_device_site_api-latest.json as an Integration Model in Admin > Integrations, then create an integration pointing at Kentik's v6 API gateway.
Authentication is a pair of API key headers:
X-CH-Auth-Email: <your-kentik-account-email>
X-CH-Auth-API-Token: <your-kentik-api-token> Generate an API token at Kentik → Settings → My Profile → API Tokens.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"email": { "value": "<your-kentik-account-email>" },
"token": { "value": "<your-kentik-api-token>" }
},
"server": {
"protocol": "https",
"host": "grpc.api.kentik.com",
"base_path": ""
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
kentik_device_site_api-latest.json | latest (curated) | 20 | Combines the official Device and Site v6 APIs into one Integration Model — see breakdown below |
kentik_device_api-v202504beta2.json | v202504beta2 | 10 | Full, unmodified official Device API spec |
kentik_site_api-v202509.json | v202509 | 10 | Full, unmodified official Site API spec |
kentik_device_site_api-latest.jsonImportant context: Kentik's legacy v5 REST API was deprecated in January 2025, and no official OpenAPI/Swagger spec was ever published for it. Kentik's current, officially-specified, actively-supported API is v6, based on gRPC with an automatic REST/JSON translation layer (gRPC-gateway). This spec targets v6.
Combines two Kentik v6 specs into a single Integration Model: the Device API (v202504beta2, 10 operations) and the Site API (v202509, 10 operations). Both are already narrow, single-purpose service APIs — every operation is CRUD against devices, sites, or site markets — so all 20 operations are included in full.
Operations included, by category:
kentik_device_api-v202504beta2.jsonFull, unmodified official vendor spec for the Kentik Device API, version v202504beta2 — preserved as-is from github.com/kentik/api-schema-public.
kentik_site_api-v202509.jsonFull, unmodified official vendor spec for the Kentik Site API, version v202509 — preserved as-is from github.com/kentik/api-schema-public.
Backed by the Kentik Device & Site API:latest Integration Model (see kentik_device_site_api-latest.json above). The project contains 20 workflows organized into 3 folders.
| Folder | Workflows | Scope |
|---|---|---|
| Devices | 10 | Device CRUD (list, create, update, delete, get by ID/name, batch ops, labels) |
| Sites | 5 | Site CRUD |
| Site Markets | 5 | Site Market CRUD |
A few resource names in the Devices folder are prefixed with Kentik (Create Kentik Device, Get Kentik Device, Update Kentik Device) to avoid colliding with identically-named workflows already published for other products — workflow names are unique across the whole Itential Platform instance, not scoped per-project.
| Dependency | Notes |
|---|---|
Kentik Device & Site API:latest Integration Model | Import from kentik_device_site_api-latest.json before importing the project |
Kentik integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Kentik — update the adapter_id value in each workflow task if yours is named differently |