# API

SR enables APIs to [Search](/1.3/social-registry/features/api/search-apis.md) and do CRUD operations. The search APIs implement GP2 Connect specification.

## API specification

[openg2p-social-registry-api](https://openg2p.stoplight.io/docs/openg2p-social-registry/yh3dm5ylwbwq7-g2-p-connect-registry-sync)

## Types of APIs

* [Search APIs](/1.3/social-registry/features/api/search-apis.md)
* [Individual APIs](/1.3/social-registry/features/api/individual-apis.md)
* [Group APIs](/1.3/social-registry/features/api/group-apis.md)

## Source code

[openg2p-social-registry-search-apis](https://github.com/OpenG2P/openg2p-social-registry/tree/17.0-develop/g2p_registry_g2p_connect_rest_api)

[openg2p-crud-apis](https://github.com/OpenG2P/openg2p-registry/tree/17.0-develop/g2p_registry_rest_api)


---

# 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.openg2p.org/1.3/social-registry/features/api.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.