--- title: API Gateway API Config description: Datadog, the leading service for cloud-scale monitoring. breadcrumbs: Docs > DDSQL Reference > Data Directory > API Gateway API Config --- # API Gateway API Config API Gateway API Config in Google Cloud defines the configuration for an API deployed through API Gateway. It specifies details such as backend services, authentication, routing, and other settings that control how requests are processed. Each configuration version can be associated with one or more API Gateway deployments. ``` gcp.apigateway_api_config ``` ## Fields | Title | ID | Type | Data Type | Description | | ----------------------- | ---- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | _key | core | string | | ancestors | core | array | | create_time | core | timestamp | Output only. Created time. | | datadog_display_name | core | string | | gateway_service_account | core | string | Immutable. The Google Cloud IAM Service Account that Gateways serving this config should use to authenticate to other services. This may either be the Service Account's email (`{ACCOUNT_ID}@{PROJECT}.iam.gserviceaccount.com`) or its full resource name (`projects/{PROJECT}/accounts/{UNIQUE_ID}`). This is most often used when the service is a GCP resource such as a Cloud Run Service or an IAP-secured service. | | gcp_display_name | core | string | Optional. Display name. | | grpc_services | core | json | Optional. gRPC service definition files. If specified, openapi_documents must not be included. | | labels | core | array | Optional. Resource labels to represent user-provided metadata. Refer to cloud documentation on labels for more details. https://cloud.google.com/compute/docs/labeling-resources | | managed_service_configs | core | json | Optional. Service Configuration files. At least one must be included when using gRPC service definitions. See https://cloud.google.com/endpoints/docs/grpc/grpc-service-config#service_configuration_overview for the expected file contents. If multiple files are specified, the files are merged with the following rules: * All singular scalar fields are merged using "last one wins" semantics in the order of the files uploaded. * Repeated fields are concatenated. * Singular embedded messages are merged using these rules for nested fields. | | name | core | string | Output only. Resource name of the API Config. Format: projects/{project}/locations/global/apis/{api}/configs/{api_config} | | openapi_documents | core | json | Optional. OpenAPI specification documents. If specified, grpc_services and managed_service_configs must not be included. | | organization_id | core | string | | parent | core | string | | project_id | core | string | | project_number | core | string | | region_id | core | string | | resource_name | core | string | | service_config_id | core | string | Output only. The ID of the associated Service Config ( https://cloud.google.com/service-infrastructure/docs/glossary#config). | | state | core | string | Output only. State of the API Config. | | tags | core | hstore_csv | | update_time | core | timestamp | Output only. Updated time. | | zone_id | core | string |