## A first API call: What deployments are there?edit

As a first API call, let’s use a GET request to retrieve information about existing deployments:

curl -k -X GET -H "Authorization: ApiKey $ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments
{
"deployments" : [
{
"id" : "c7d139e789864bf4a6e41819ece19741",
"name" : "security-cluster",
"resources" : [
{
"ref_id" : "elasticsearch",
"id" : "c7d139e789864bf4a6e41819ece19741",
"kind" : "elasticsearch",
"region" : "ece-region",
"cloud_id" : "security-cluster:MTkyLjE2OC40NC4xMC5pcC5lcy5pbzo5MjQzJGM3ZDEzOWU3ODk4NjRiZjRhNmU0MTgxOWVjZTE5NzQxJA=="
}
]
},
{
"name" : "logging-and-metrics",
"resources" : [
{
"ref_id" : "elasticsearch",
"kind" : "elasticsearch",
"region" : "ece-region",
"cloud_id" : "logging-and-metrics:MTkyLjE2OC40NC4xMC5pcC5lcy5pbzo5MjQzJDkzZGUzYTZjYWY4ZDRlNGM4ZTY2ZTExMjcyNzdjZWFkJDIwOWE4ZDM4ZGUwNDRmNzhhYjFhMWFlODNiODE2MWY0"
},
{
"ref_id" : "kibana",
"elasticsearch_cluster_ref_id" : "elasticsearch",
"id" : "209a8d38de044f78ab1a1ae83b8161f4",
"kind" : "kibana",
"region" : "ece-region"
}
]
},
{
"id" : "3e31526f42b74776a3c715e0f5277a5c",
"resources" : [
{
"ref_id" : "elasticsearch",
"id" : "3e31526f42b74776a3c715e0f5277a5c",
"kind" : "elasticsearch",
"region" : "ece-region",
}
]
}
]
}

There are three deployments, security-cluster, logging-and-metrics, and admin-console-elasticsearch, which get created with every installation of Elastic Cloud Enterprise. Take care when modifying these deployments, as they are part of the control plane of ECE. To keep your installation safe, some operations are not allowed on these deployments, but we do recommend that you enable fault tolerance for their Elasticsearch resources and resize them.

In order to obtain more detail about a specific deployment, we can use a GET request using one of the deployment IDs from the previous response (in this example, you could set $DEPLOYMENT_ID to the ID of the admin-console-elasticsearch deployment: 3e31526f42b74776a3c715e0f5277a5c): curl -k -X GET -H "Authorization: ApiKey$ECE_API_KEY" https://$COORDINATOR_HOST:12443/api/v1/deployments/$DEPLOYMENT_ID
{
"id" : "3e31526f42b74776a3c715e0f5277a5c",
"healthy" : true,
"resources" : {
"elasticsearch" : [
{
"ref_id" : "elasticsearch",
"id" : "3e31526f42b74776a3c715e0f5277a5c",
"region" : "ece-region",
"info" : {
"cluster_id" : "3e31526f42b74776a3c715e0f5277a5c",
"deployment_id" : "3e31526f42b74776a3c715e0f5277a5c",
"healthy" : true,
"status" : "started",
"plan_info" : {
"healthy" : true,
...
},
"topology": {
...
}
}
}
]
},
"organization_id" : "platform",
"system_owned" : true,
"hidden" : false,
"last_modified" : "2021-07-28T21:32:47.508Z",
"last_resource_plan_modified" : "2021-07-28T21:32:09.659Z"
}
}

To simplify things, we’ve omitted some sections from the JSON output.

#### A note on terminologyedit

If this is your first time using the ECE API, some of the terminology in the JSON output will likely be unfamiliar. For example, there is a reference to the term “plan” in output fields such as plan_info. A plan is just a resource configuration that gets applied to a resource, such as an Elasticsearch cluster or a Kibana instance. When you change an Elasticsearch cluster to resize it, for example, you are applying a new plan.

A deployment is a group of different resources such as Elasticsearch clusters, a Kibana instance, and other products of the Elastic Stack. In the previous example, the admin-console-elasticsearch deployment only had an Elasticsearch resource, and the logging-and-metrics deployment had both Elasticsearch and Kibana resources.