# Agility App URL Patterns

> Source: https://agilitycms.com/docs/developers/agility-app-url-patterns

Every content item, page and component in the Agility CMS app has a stable URL. If you know the pattern and the IDs, you can build a link to any of them without opening the app first. This article lists the patterns for content, pages and page components, and shows three ways to find the IDs.

## Base pattern

Every URL starts with your instance GUID and a locale code:

```
https://app.agilitycms.com/instance/{instance-guid}/{locale}/...
```

- `{instance-guid}` is the ID of your instance, for example `abc12345-u`.
- `{locale}` is a locale code configured on the instance, such as `en-us`, `fr` or `fr-ca`.

Both are required. The locale decides which language version of the item opens, so a link built for `fr` opens the French version.

## Patterns by section

| What you want to open | Pattern after `/{instance-guid}/{locale}` |
|---|---|
| A content list | `/content/list-{containerID}` |
| An item in a content list | `/content/list-{containerID}/listitem-{contentID}` |
| A single-item container | `/content/item-{containerID}` |
| A page | `/pages/page-{pageID}` |
| A component on a page | `/pages/page-{pageID}/item-{containerID}` |

### An item in a content list

```
https://app.agilitycms.com/instance/{instance-guid}/{locale}/content/list-{containerID}/listitem-{contentID}
```

`{containerID}` is the ID of the content list (the container), and `{contentID}` is the ID of the item. These are different numbers. A content model also has its own model ID, which is a third number and does not appear in this URL.

To open just the list, drop the `/listitem-{contentID}` part.

### A single-item container

Some containers hold exactly one item, such as a settings record. These open with `item-` and the container ID, and no content ID:

```
https://app.agilitycms.com/instance/{instance-guid}/{locale}/content/item-{containerID}
```

### A page

```
https://app.agilitycms.com/instance/{instance-guid}/{locale}/pages/page-{pageID}
```

### A component on a page

A component on a page is stored in its own container. The URL nests that container under the page:

```
https://app.agilitycms.com/instance/{instance-guid}/{locale}/pages/page-{pageID}/item-{containerID}
```

Here `{containerID}` is the ID of the component's container, not the component's `contentID`. Search results and the Management API report both, so check which one you are holding.

## Find the IDs

### In the app

Open the item, page or component and read the address bar. The numbers after `list-`, `listitem-`, `item-` and `page-` are the IDs.

### With the Agility MCP server

The [Agility CMS MCP server](/docs/developers/agility-cms-mcp-server) can find IDs for you:

- `search_instance` is full-text search across content, components, pages and assets. For content items, pages and components, each hit includes an `editUrl` that is the finished deep link. It also returns `contentID`, `pageID` and `containerID` where they apply. A number you type also matches IDs exactly.
- `get_containers` lists containers. Each one has an `ID` (the container ID), a `modelID`, and a `modelTypeID`.
- `get_sitemap` with `flat: true` returns `pageID`, `pageName` and `parentPageID` for each page.
- `get_content_models` and `get_component_models` list the model IDs.

`search_instance` also returns hits in every locale that has the item, each with its own `editUrl`. Pass `locale` to narrow it.

### With the Management API

The [Content Management API](/docs/developers/content-management-api) returns `contentID` for items, `pageID` for pages and container IDs for containers. The [Management SDK for JavaScript](/docs/javascript/management-sdk/getting-started) wraps those calls. Build the URL yourself from the IDs and your instance GUID using the patterns above.

## Why this is useful

- **Notifications.** A Slack message or email that says "item 123 needs review" is more useful when it links to the item.
- **Scripts.** A migration or audit script can print a link next to every record it flags, so a person can click straight to the fix.
- **AI agents.** An agent that reports on your content can hand back links a person can open. Tell it the patterns, or use `search_instance` and pass on the `editUrl`.

## Other screens

For other screens, such as content models, component models, the media library and the sitemap view, open the screen and copy the address from your browser.

## Related

- [Agility CMS MCP server](/docs/developers/agility-cms-mcp-server)
- [Content Management API](/docs/developers/content-management-api)
- [Management SDK for JavaScript: Getting Started](/docs/javascript/management-sdk/getting-started)

---

## Related pages

- [Content Fetch API](https://agilitycms.com/docs/developers/content-fetch-api.md)
- [Content Sync API](https://agilitycms.com/docs/developers/content-sync-api.md)
- [Content Management API](https://agilitycms.com/docs/developers/content-management-api.md)
- [GraphQL API](https://agilitycms.com/docs/developers/graphql-api.md)
- [CLI - CI/CD Integration Guide](https://agilitycms.com/docs/developers/cli-ci-cd-integration-guide.md)
- [Testing on Swagger](https://agilitycms.com/docs/developers/testing-on-swagger.md)
- [GraphQL & Rest API Filtering](https://agilitycms.com/docs/developers/graphql-operators.md)
- [AgilityCLI (Command Line Interface)](https://agilitycms.com/docs/developers/cli.md)
- [Personal Access Tokens](https://agilitycms.com/docs/developers/personal-access-tokens.md)
- [Content Delivery & CDN Architecture](https://agilitycms.com/docs/developers/content-delivery-and-cdn-architecture.md)
- [Typed GraphQL with TypeScript and Next.js](https://agilitycms.com/docs/developers/typed-graphql-typescript-nextjs.md)
- [Image Transformation Reference](https://agilitycms.com/docs/developers/image-transformation-reference.md)
- [Fetch API Status Codes and Caching](https://agilitycms.com/docs/developers/fetch-api-status-codes-and-caching.md)
- [Field Types and What the APIs Return](https://agilitycms.com/docs/developers/field-types-api-reference.md)
- [Content Sync Explained](https://agilitycms.com/docs/developers/content-sync-explained.md)
- [Agility CLI Command Reference](https://agilitycms.com/docs/developers/cli-reference.md)
- [CLI Reference: agility pull](https://agilitycms.com/docs/developers/cli-pull.md)
- [CLI Reference: agility sync and push](https://agilitycms.com/docs/developers/cli-sync.md)
- [CLI Reference: agility reverse-sync](https://agilitycms.com/docs/developers/cli-reverse-sync.md)
- [CLI Reference: agility workflows](https://agilitycms.com/docs/developers/cli-workflows.md)
- [CLI Reference: agility login and logout](https://agilitycms.com/docs/developers/cli-login-logout.md)
- [Test Your Agility Integration in CI](https://agilitycms.com/docs/developers/test-agility-integration-in-ci.md)
- [CLI Reference: agility verify](https://agilitycms.com/docs/developers/cli-verify.md)
- [Create a Personal Access Token with the API](https://agilitycms.com/docs/developers/create-personal-access-token.md)
- [Manage Personal Access Tokens in Agility](https://agilitycms.com/docs/developers/manage-personal-access-tokens.md)

Index of every docs page: https://agilitycms.com/docs/llms.txt
