# IBM Event Streams Registry

{% hint style="warning" %}
Requires Enterprise subscription on IBM Event Streams and only hard delete is supported for IBM Event streams
{% endhint %}

To configure an application to use this compatibility API, specify the Schema Registry endpoint in the following format:

```
https://token:{$APIKEY}@{$HOST}/confluent
```

{% hint style="success" %}
Use "**token**" as the username. Set the password as your API KEY from IBM Event streams

Only one Schema Registry connection is allowed.

Name must be schema-registry.

See [JSON schema](https://docs.lenses.io/latest/deployment/configuration/overview#json-schema-support) for support.

Environment variables are supported; escape the dollar sign

```yaml
sslKeystorePassword:
  value: "\${ENV_VAR_NAME}"
```

{% endhint %}

{% code title="provisioning.yaml" %}

```yaml
confluentSchemaRegistry:
  - name: schema-registry
    tags: ["tag1"]
    version: 1      
    configuration:
      schemaRegistryUrls:
        value:
          - https://token:{$APIKEY}@{$HOST}/confluent
```

{% endcode %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lenses.io/latest/deployment/configuration/agent/automation/schema-registries/ibm-event-streams-registry.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.