# Search Connection Strings

This page describes the `connectionStrings` endpoint.

{% 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 connection strings

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

Search across all connection strings in the handler table.

#### Query parameters

| Attribute  | Description                                                                                                            | Required |
| ---------- | ---------------------------------------------------------------------------------------------------------------------- | -------- |
| searchText | `string` A string used to filter returned connection strings. The query is executed with a wildcard prefix and suffix. | No       |

#### Response parameters

| Attribute | Description                                                                 |
| --------- | --------------------------------------------------------------------------- |
| values    | `array` Details regarding connection strings, including `name` and `count`. |

### Request example

The following request searches across all connection strings in the handler table.

```bash
curl \
    --request GET \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer dea464c07bd07300095caa8" \
    https://your-immuta-url.com/connectionStrings
```

### Response example

```json
{
  "values": [
    {
      "name": "TEST@immuta.us-east-1.testcomputing.com:???/TEST",
      "count": 5
    }
  ]
}
```


---

# 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/connection-string.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.