Skip to main content
POST
/
cost-insights
/
filters
Get available filters
curl --request POST \
  --url https://api.cloudcapital.co/v1/cost-insights/filters \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "fields": [
    "accounts",
    "services"
  ],
  "filters": {
    "inclusions": {
      "dateRange": {
        "start": "2026-01-01",
        "end": "2026-03-31"
      }
    }
  }
}
'
{
  "data": {
    "costLayers": [
      "<string>"
    ],
    "clouds": [
      "<string>"
    ],
    "services": [
      "<string>"
    ],
    "resourceFamilies": [
      "<string>"
    ],
    "regions": [
      "<string>"
    ],
    "instanceTypes": [
      "<string>"
    ],
    "usageTypes": [
      "<string>"
    ],
    "billingPeriods": [
      "<string>"
    ],
    "costTypes": [
      "<string>"
    ],
    "accounts": [
      "<string>"
    ],
    "accountIdToName": {},
    "integrations": [
      "<string>"
    ],
    "resourceTags": [
      "<string>"
    ],
    "tagValues": {},
    "costCategories": [
      "<string>"
    ],
    "enriched": {}
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.cloudcapital.co/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

API key authentication. Generate an API key from your Cloud Capital dashboard under Settings > API keys. Include it in the Authorization header as a Bearer token.

Body

application/json
​
fields
enum<string>[]

Specific filter fields to return. When omitted, all available filter fields are returned.

Filter field names for the filters endpoint. Pass these in the fields array to request specific filter option sets.

Available options:
costLayers,
clouds,
services,
resourceFamilies,
regions,
instanceTypes,
usageTypes,
billingPeriods,
costTypes,
accounts,
integrations,
resourceTags,
costCategories
​
filters
object

Filter container supporting both inclusion and exclusion criteria. Use inclusions to narrow results to matching data and exclusions to remove matching data from results.

Response

Filter values retrieved successfully

Successful HTTP responses wrap the endpoint-specific body in data. Each operation's 200 response schema is this object merged (allOf) with a data property referencing the payload schema for that endpoint.

​
success
enum<boolean>
required

Always true when the HTTP status is 2xx.

Available options:
true
​
data
object
required

Available filter values. Each field contains an array of valid values. The enriched field provides cost and availability metadata for cross-filterable fields.