---
type: api
title: Get allocator metadata
description: Retrieves the allocator metadata.
url: https://www.elastic.co/elastic/docs-builder/docs/4641/api/doc/cloud-enterprise/v4/operation/operation-get-allocator-metadata
resource: https://www.elastic.co/elastic/docs-builder/docs/4641/api/doc/cloud-enterprise/v4/operation/operation-get-allocator-metadata
products:
  - Elastic Cloud Enterprise
---

# Get allocator metadata

Authentication: required

## Paths

- `GET` `/platform/infrastructure/allocators/{allocator_id}/metadata`

#### Path parameters

- `allocator_id` (string) — required
  The allocator identifier.

## Description

Retrieves the allocator metadata.

## Responses

#### `200`

The allocator metadata was successfully returned

`application/json`

Type: `object[]`

An array; each item has these fields:

- `key` (string)
  The metadata field name
- `value` (string)
  The metadata value
##### Response headers

- `x-cloud-resource-version` (string)
  The resource version, which is used to avoid update conflicts with concurrent operations
- `x-cloud-resource-created` (string)
  The date-time when the resource was created (ISO format relative to UTC)
- `x-cloud-resource-last-modified` (string)
  The date-time when the resource was last modified (ISO format relative to UTC)

#### `404`

The allocator specified by {allocator_id} cannot be found. (code: `allocators.allocator_not_found`)

`application/json`

- `errors` (object[])
  A list of errors that occurred in the failing request
  - `code` (string)
    A structured code representing the error type that occurred
  - `message` (string)
    A human readable message describing the error that occurred
  - `fields` (string[])
    If the error can be tied to a specific field or fields in the user request, this lists those fields
##### Response headers

- `x-cloud-error-codes` (enum)
  The error codes associated with the response

## Code examples

#### curl

```curl
curl -X GET "${API_URL}/platform/infrastructure/allocators/${ALLOCATOR_ID}/metadata" \
  -u "${USERNAME}:${PASSWORD}"
```

## Response examples

#### 200

`application/json`

Generated from the API spec. Values are representative. Unions use the first variant; deeply nested or large bodies may omit fields.

```json
[
  {
    "key": "string",
    "value": "string"
  }
]
```

#### 404

`application/json`

Generated from the API spec. Values are representative. Unions use the first variant; deeply nested or large bodies may omit fields.

```json
{
  "errors": [
    {
      "code": "string",
      "message": "string",
      "fields": [
        "string"
      ]
    }
  ]
}
```