# Get Catalog Metadata

Returns the Catalog metadata as a JSON Schema document describing every resource
(Category, Attribute Set, Product, Variant, Point of Sale) and the relationships
between them. Use it to build requests against the rest of the API.
            
## Authentication
            
Requires a valid API key in the X-API-KEY header.
            
## Response
            
200 OK — A JSON schema document describing every resource in the Catalog
(Category, Attribute Set, Product, Variant, Point of Sale) and the relationships
between them. Use this document to build requests against the rest of the API.
            
## Error Responses
            
- 401 Unauthorized — Missing or invalid API key.
- 404 Not Found — Tenant or model not found.
- 500 Internal Server Error — Unexpected technical error.
            
## Example
            
Request:
http
GET /$metadata HTTP/1.1
X-API-KEY: your-api-key-here

            
Response:
http
HTTP/1.1 200 OK
Content-Type: application/json

Endpoint: GET /$metadata
Version: 2.0.0

## Header parameters:

  - `X-API-KEY` (string)
    Tenant's API key (required)

## Response 200 fields (application/json):

  - `readLink` (object)

  - `readLink.uri` (string,null)

  - `value` (any,null)

## Response 400 fields (application/json):

  - `validationFailures` (object,null)
    Example: {"Layout":[{"PropertyName":"Layout","ErrorMessage":"The layout must contain exactly the attributes of the stored layout. Missing: tags. Unknown: extra_field.","AttemptedValue":null}]}

## Response 401 fields (application/json):

  - `type` (string,null)

  - `title` (string,null)

  - `status` (integer,null)

  - `detail` (string,null)

  - `instance` (string,null)

## Response 500 fields (application/json):

  - `error` (string,null)

  - `details` (any,null)