> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/crvs-v1.0-1/crvs/crvs-with-sp-mis-standards/api/methods/api.crvs.02-event-subscription.md).

# API.CRVS.02 Event Subscription

The subscriber APIS facilitates defining endpoints that facilitate to subscribe/unsubscribing events from the registry. The notify endpoint is to be implemented at the SP system end to receive event data. 

API definition link:

* [/subscribe](https://api.spdci.org/release/html/crvs_api_v1.0.0.html#tag/Async/operation/post_reg_subscribe)
  * The SP system needs to subscribe to events with expected search criteria so events with expected criteria are only received on the SP system end.
* [/unsubscribe](https://api.spdci.org/release/html/crvs_api_v1.0.0.html#tag/Async/operation/post_reg_unsubscribe)
  * The SP system can unsubscribe to events using this endpoint.

Please refer to GitHub for YAML object definitions:

* [YAML definitions](https://api.spdci.org/release/yaml/crvs_api_v1.0.0.yaml)

Note: Above YAML is consolidated, for any changes kindly raise pull request on [github](https://github.com/spdci/standards).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://standards.spdci.org/standards/dci-standards/crvs-v1.0-1/crvs/crvs-with-sp-mis-standards/api/methods/api.crvs.02-event-subscription.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.