> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hasmcp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What is the endpoint for listing all resources of a provider?

> Reference the API route used to retrieve all defined resources mapped to a specific external API provider.

# Listing All Resources of a Provider

## Using HasMCP UI

<img src="https://mintcdn.com/hasmcp/J3U3Tv-0tpxoj7dc/images/kb/provider-resources-list.png?fit=max&auto=format&n=J3U3Tv-0tpxoj7dc&q=85&s=6c52c443e4520dae8fdd830e3ceaaf62" alt="Provider Resources List" width="2560" height="1266" data-path="images/kb/provider-resources-list.png" />

When examining a specific **Provider Details** view in the web dashboard, clicking on the **Resources** tab automatically triggers this API listing, showing all configured data blobs that can be bound to your servers.

## Using REST API

If you need to programmatically crawl your API catalog to discover what static or read-only context feeds a provider exposes, you target the sub-resource listing endpoint.

### The API Endpoint

**`GET /providers/{providerId}/resources`**

*(Note: Replace `{providerId}` with your provider's 11-character hash ID).*

### Fetching the Collection

Dispatching an authenticated `GET` request to this endpoint yields a [`ListProviderResourcesResponse`](/api-reference/providers/resources/list-provider-resources) payload containing a `resources` array.

#### Example Request

```bash theme={null}
curl -X GET https://app.hasmcp.com/api/v1/providers/kSuB9Gf6aD4/resources \
 -H "Authorization: Bearer YOUR_TOKEN"
```

Each item returned in the array will present the `id` of the specific resource, its contextual `name`, expected `mimeType`, and the `uri` metadata indicating the logical path of the file or data chunk.