---
schema_version: "1"
id: 09ea6b1f9292b5f7ff052191582f4a363a276c7d6c058fd44c1de214687f12f9
title: API Names for Trails, Modules, and Units
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/mth_api_names_on_mytrailhead.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.mth_api_names_on_mytrailhead.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: d48fbd0b87eb6c277debde4b6ab13ef6b02d52f46326c6d0a0eb20959a40f8a4
description: Each content collection, release, trail, module, and unit on your enablement site has its own API name, which is a globally unique ID that references a content path in URLs.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# API Names for Trails, Modules, and Units

Each content collection, release, trail, module, and unit on your enablement site has its own API name, which is a globally unique ID that references a content path in URLs.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, and <strong>Unlimited</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d5678e61">User Roles</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="User Roles" class="slds-cell-wrap" style="vertical-align:top;" headers="d5678e61 ">This topic supports these enablement site
            roles:</td>

          <td class="slds-cell-wrap" style="vertical-align:top;" headers="d5678e61 ">
            <ul>
              <li>Content Creators</li>

              <li>Release Managers</li>

              <li>Subject Matter Experts</li>

            </ul>
          </td>

        </tr>
      </tbody>
    </table>

## URL Examples

For example, let’s say that you’ve published content with these API names:

 
| Content | API Name |
| --- | --- |
| Unit | learn-the-pure-aloe-sales-pitch |
| Module | pure-aloe-sales-strategies |
| Trail | sell-well-at-pure-aloe |
| Release | q3-learning-updates |
| Content Collection | sales-team-onboarding |

All of these components, except for a release, are included in URLs.

URL for a trail

Includes the content collection and trail API names, such as:

```
https://purealoe.my.trailhead.com/en/content/sales-team-onboarding/trails/sell-well-at-pure-aloe
```

URL for a standalone module

Includes the content collection and module API names, such as:

```
https://purealoe.my.trailhead.com/en/content/sales-team-onboarding/modules/pure-aloe-sales-strategies
```

URL for a module that’s included in a trail

Includes the content collection, trail, and module API names, such as:

```
https://purealoe.my.trailhead.com/en/content/sales-team-onboarding/modules/pure-aloe-sales-strategies?trail_id=sell-well-at-pure-aloe
```

URL for a unit in a standalone module

Includes the content collection, module, and unit API names, such as:

```
https://purealoe.my.trailhead.com/en/content/sales-team-onboarding/modules/pure-aloe-sales-strategies/learn-the-pure-aloe-sales-pitch
```

URL for a unit in a module that’s included in a trail

Includes the content collection, trail, module, and unit API names, such as:

```
https://purealoe.my.trailhead.com/en/content/sales-team-onboarding/modules/pure-aloe-sales-strategies/learn-the-pure-aloe-sales-pitch?trail_id=sell-well-at-pure-aloe
```

## Guidelines for Custom API Names

When you enter a title for your content, Trailmaker Content generates an API name based on the title. Optionally, you can specify a custom API name instead of the generated value. Follow these conventions.

- To help you find and manage content in your version control system more easily, specify an API name that’s consistent with the content’s title.
- Keep API names specific but brief.
- Specify API names for content collections that are unique within your Salesforce org.
- Specify API names for releases, trails, modules, and units that are globally unique. In other words, the API names for these records must be unique among all your content collections and all Salesforce orgs. For example, you can’t reuse an API name that another company already used for a published module. And you can’t reuse an API name that your own company already used for a published module in another collection.
- For a release, an API name must contain at least 4 characters and no more than 32 characters.
- For content, an API name must contain at least 4 characters and no more than 80 characters.
- You can’t use spaces in an API name, but you can use hyphens or underscores.

## Changes to API Names

In general, don’t change the API name for any content collection, trail, module, or unit after it’s published. Otherwise, you can publish duplicate content and break links that learners have used, shared, or bookmarked.

There’s one exception to this rule. If you migrate published content to a different content collection, specify a new API name for the content when you add it to a new content collection. Trailmaker prevents you from adding content that reuses an API name to a release.

#### See Also

- [Metadata for Trails, Modules, and Units](https://help.salesforce.com/s/articleView?id=sales.mth_metadata_on_mytrailhead.htm&release=264.0.0&type=5 "When you create trails, modules, and units, you also create metadata about your content, such as the title, description, and target audience. Learners can filter the content on your enablement site based on the metadata values you assign.")
- [Backpacks for Trails and Modules](https://help.salesforce.com/s/articleView?id=sales.mth_backpacks_on_mytrailhead.htm&release=264.0.0&type=5 "A backpack is a ZIP file that contains your content’s source files that you can download, back up, or upload. An individual backpack can be up to 50 MB. You can download a backpack for content that’s in your local Trailmaker Content workspace, or download a backpack for content published from Trailmaker Release.")
- [Considerations for Managing Releases](https://help.salesforce.com/s/articleView?id=sales.mth_how_releases_work.htm&release=264.0.0&type=5 "A release specifies the list of the modules and trails that you want to publish together at the same time. You can publish a module or trail only if it’s added to a release. Before you start lining up your planned releases, review some important guidelines about how releases work in Trailmaker.")
- [Create a Module in Trailmaker Content](https://help.salesforce.com/s/articleView?id=sales.mth_create_module_in_tm_content.htm&release=264.0.0&type=5 "A module can stand alone or be a part of a trail. When you’re ready to create a module and its units, move the final draft of your content from a word processor into Trailmaker Content.")
- [Migrate Published Content to a Different Content Collection](https://help.salesforce.com/s/articleView?id=sales.mth_content_collections_migrate.htm&release=264.0.0&type=5 "You can move your company’s existing learning content from one content collection to another. For example, maybe your company previously published content under your enablement site’s single namespace before multiple content collections became available. And now, you want to move content to a content collection for a specific audience.")
- [Create SSO Links to Enablement Site Content (Trailblazer.me)](https://help.salesforce.com/s/articleView?id=sales.mth_build_sso_link_to_mytrailhead_content.htm&release=264.0.0&type=5 "If your enablement site’s authentication provider is Trailblazer.me (TBID), by default your users must log in with their TBID credentials to access your site. You can give users one-click access to your site by creating links that incorporate single sign-on (SSO).")