Clustering Parameters
project_name*: Name of the project for easier identification in the keywordinsights.ai UI.
keywords*: List of keywords. [“keyword 1”, “keyword 2”, “keyword 3”]
search_volumes*: List of search volumes. [213, 1561, 616] Or any data really doesn’t matter, as that is always provided by the user
language*: Language code to use for SERP results scraping.
location*: Location name to use for SERP results scraping.
insights*: The types of insights to perform within the order (cluster required).
For a full clustering order, you need to define:
Clustering: Intent Only
POST /api/keywords-insights/order/ In order to create a clustering order for intent only, you have to specify all clustering parameters, exactly as for a full clustering order.Intent Only: Example Payload
The difference to a full clustering order is the contents of the insights array inside the payload. You only need to pass “context” vs “context”, “rank” and “cluster”. A full example of an intent only order below:Intent Only: Code Example Python
Retrieving Clustering results in XLSX: Code example python
GET /api/keywords-insights/order/xlsx//| Parameter | Description |
|---|---|
| Authorization *string(header) | Bearer token |
| order_id *string(path) | ID of the order to export |
Retrieving Clustering results in JSON: Code example python
GET /api/keywords-insights/order/json//| Parameter Name | Description |
|---|---|
| Authorization *string(header) | Bearer token |
| order_id *string(path) | Order UUID (returned when the order was created) |
| page_sizeinteger(query) | Number of rows per page (max 1000) Default value : 50 |
| page_numberinteger(query) | Page number starting from 1 Default value : 1 |
| sort_bystring(query) | Sort field (e.g. search_volume, keyword, cluster_id) Default value : search_volume |
| ascendingboolean(query) | Sort direction. false = descending Default value : false —truefalse |
| filter_idstring(query) | Filter ID. Can be obtained from the filters endpoint. |