Skip to main content
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 if you don’t.

​
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).

​
Not the standalone Connectors API

The same product-boundary confusion that applies to connector lifecycle applies here too: the standalone Connectors API 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

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.
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.

​
Choose your path

Creating an APC

Walk through every field the create call needs — project template, target languages, monitored folder, schedule, and translation-export rule.

Troubleshooting

The full-replace PUT trap, listing gotchas, and per-connector-type quirks.