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

# Introduction

> Understand what Automated Project Creation (APC) is, how it relates to connectors, and the endpoints that manage it.

<Info>This guide is about **Automated Project Creation (APC)** — a TMS feature that watches a connector's remote storage and automatically creates translation projects when new files show up. It assumes you already have a working connector; see [Managing TMS Connectors](/en/guides/managing-connectors/overview) if you don't.</Info>

## What APC does

Automated Project Creation lets an already-configured connector do more than move files on request — it watches one or more folders (or, for connector types without a real filesystem, the equivalent browsable structure) on a schedule, and automatically creates a new translation project (or updates an existing continuous one) whenever it finds new or changed content.

APC always belongs to exactly one connector. There's no such thing as an APC setting that isn't tied to a connector — if you don't have one set up yet, create it first (see [Managing TMS Connectors](/en/guides/managing-connectors/overview)).

## Not the standalone Connectors API

The same product-boundary confusion that applies to connector lifecycle applies here too: the standalone [Connectors API](/en/api/connectors/introduction) only moves file content through an already-configured connector — it has no concept of automated project creation. APC lifecycle lives entirely on the TMS API.

## The APC lifecycle endpoints

| Method & path                                                                | Purpose                                                                                                                      |
| ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `GET /api2/v1/automatedProjects`                                             | List your APC settings (paginated — see below)                                                                               |
| `POST /api2/v3/automatedProjects`                                            | Create an APC setting                                                                                                        |
| `GET /api2/v3/automatedProjects/{settingsId}`                                | View an APC setting's full configuration                                                                                     |
| `PUT /api2/v3/automatedProjects/{settingsId}`                                | Update an APC setting (full replace — see [Troubleshooting](/en/guides/managing-automated-project-creation/troubleshooting)) |
| `DELETE /api2/v1/automatedProjects/{settingsId}`                             | Delete one APC setting                                                                                                       |
| `DELETE /api2/v1/automatedProjects/batch`                                    | Delete several APC settings by id in one call                                                                                |
| `GET /api2/v1/automatedProjects/{settingsId}/running`                        | Check whether it's currently running                                                                                         |
| `GET /api2/v1/automatedProjects/{settingsId}/status`                         | Check its last-run status                                                                                                    |
| `GET .../monitoredFolder/{folder}/connectors/{connectorId}/folders/{folder}` | Browse an existing APC's monitored folder contents                                                                           |

<Tip>APC settings are organization-scoped — they're addressed directly by their own `settingsId`, never nested under a project. Don't construct a project-nested path for them.</Tip>

<Note>`GET /api2/v1/automatedProjects` returns up to 50 results per call (`pageSize`, 0-indexed `pageNumber`). Check `totalElements`/`totalPages` on the first response and page through all of them before treating the result as complete — a large organization can easily have well over 50 APC settings.</Note>

## Choose your path

<CardGroup cols={2}>
  <Card title="Creating an APC" icon="folder-plus" href="/en/guides/managing-automated-project-creation/creating-an-apc">
    Walk through every field the create call needs — project template, target languages, monitored folder, schedule, and translation-export rule.
  </Card>

  <Card title="Troubleshooting" icon="triangle-alert" href="/en/guides/managing-automated-project-creation/troubleshooting">
    The full-replace PUT trap, listing gotchas, and per-connector-type quirks.
  </Card>
</CardGroup>