Discover the queryable details$ fields for a technology or technology group
Returns the queryable details$. fields for one technology or technology group.
These fields are per-technology and are NOT part of any schema in this document, so this endpoint is the
only source of truth for them. Call it before building a component policy or a details$. component
query, and use the returned field paths verbatim - a path that is not returned does not exist and is
rejected with a 400 when the policy is created.
The response type tells you which comparison values are valid for a field, and availableValues, when
present, enumerates the only accepted values. filterable tells you whether the field is indexed - an
un-indexed field exists on the component but cannot be filtered on in a component query.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Selects which set of queryable details$. fields to return. Pass exactly one key, as either a
technology or a technology group.
Passing a technology returns its own fields unioned with the fields of the group it belongs to - so
rds includes the shared database fields. Passing a group returns only that group's fields.
Keys not listed here have no queryable detail fields and are rejected with a 404.
A technology key or a technology group key.
aws-api-gateway-rest-api, aws-auto-scaling-group, aws-bedrock-model, aws-clb, aws-cloudfront-distribution, aws-dynamodb-backup, aws-ebs-snapshot, aws-ebs-volume, aws-efs-file-system, aws-elastic-ip-address-eip, aws-elb, aws-iam-group, aws-iam-role, aws-kms-key, aws-nat-gateway, aws-organizations-account, aws-organizations-organization, aws-organizations-organizational-unit-ou, aws-redshift-cluster, aws-redshift-node, aws-route-53-hosted-zone, aws-s3-bucket, aws-secrets-manager-secret, aws-security-group, aws-sqs-queue, aws-subnet, aws-vpc, aws-vpc-endpoint-gateway, aws-vpc-endpoint-interface, azure-ai-model, azure-app-service-web-app, azure-application-gateway, azure-cosmos-db, azure-cosmos-db-for-postgresql-cluster, azure-data-lake-storage-gen2, azure-databricks-workspace, azure-db, azure-db-mysql-flexible, azure-db-postgres-flexible, azure-db-sql-managed-database, azure-db-sql-managed-instance, azure-db-sql-server-on-vm, azure-dns-zone-private, azure-dns-zone-public, azure-firewall, azure-front-door, azure-function-app, azure-key-vault, azure-load-balancer, azure-log-analytics-workspace, azure-management-group, azure-monitor-action-group, azure-nat-gateway, azure-network-security-group, azure-private-endpoint, azure-public-ip-address, azure-resource-group, azure-storage-account, azure-storage-account-blob-container, azure-subscription, azure-user-assigned-managed-identity, azure-virtual-network, azure-virtual-network-subnet, azure-vm, azure-vm-managed-disk, azure-vm-scale-set, azure-waf-policy, dynamodb, ec2, ecr, ecs, elasticache, gcp-cloud-armor-policy, gcp-cloud-logging-bucket, gcp-cloud-logging-sink, gcp-gce-persistent-disk, gcp-gcs-bucket, gcp-kms-crypto-key, gcp-organization, gcp-project, gcp-secret-manager-secret, gcp-service-account, gcp-service-account-key, gcp-vpc-firewall-rule, gcp-vpc-network, gemini-enterprise, iam-access-key, k8s, lambda, rds Response
Success
component The key the fields were resolved for, echoing the request.
Every queryable detail field for the key. This is the complete set - a details$. path that is not listed does not exist and cannot be filtered on.