# Search Schemas

This page describes the `schemas` endpoint of the Immuta API and its request and response parameters.

{% hint style="info" %}
Additional fields may be included in some responses you receive; however, these attributes are for internal purposes and are therefore undocumented.
{% endhint %}

## Search for schemas

<mark style="color:green;">`GET`</mark> `/schemas`

Search across all schemas in the handler table.

#### Query parameters

| Attribute  | Description                                                                                        | Required |
| ---------- | -------------------------------------------------------------------------------------------------- | -------- |
| searchText | `string` Used to filter returned schemas. The query is executed with a wildcard prefix and suffix. | No       |

#### Response parameters

| Attribute | Description                                                         |
| --------- | ------------------------------------------------------------------- |
| values    | `metadata` The `name` and `count` for each result.                  |
| name      | `string` The name of the schema.                                    |
| count     | `integer` The total number of data sources attached to that schema. |

### Request example

This example request gets all of the schemas with the string "medical" in their name.

```bash
curl \
    --request GET \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer dea464c07bd07300095caa8" \
    https://demo.immuta.com/schemas?searchText=medical
```

### Response example

```json
{
  "values": [
    {
      "name": "medical_records",
      "count": 1
    }
  ]
}
```


---

# 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://documentation.immuta.com/saas/developer-guides/api-intro/immuta-v1-api/manage-data-access/schemas.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.