---
title: "Create a new Engagement from a template"
method: POST
path: "/v1/engagements/from-template"
tags: ["engagements"]
---

# Create a new Engagement from a template

`POST /v1/engagements/from-template`

Creates a new Engagement based on an existing template Engagement. The request is accepted for asynchronous processing; the response returns the new Engagement's UUID and the Job UUID used to poll its provisioning status.

## Request body

- EngagementCreateFromTemplate
  - `template_uuid` string, uuid, required
  - `client_company_uuid` string, uuid, required
  - `name` string, required
  - `start_date` string
  - `end_date` string
  - `report_issue_date` string
  - `identifier` string, nullable — An external identifier that can be used by integrated systems

## Response `202`

The Engagement creation has been accepted for processing

- object
  - `data` EngagementUuidRead, required
    - `uuid` string, uuid, required — The UUID of the Engagement being provisioned
    - `job_uuid` string, uuid, required — The UUID of the Engagement provisioning Job
    - `_links` JobSubmittedReadLinks, required
      - `status` HalLink, required
        - `href` string, uri, required
        - `title` string — A human-readable title for the link
        - `type` string, required — The content-type

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden (requires permission `['insert', 'engagements']`) Forbidden (requires scopes `engagements:write`)
- `429` — Too many requests

---

[API](https://skmtc.net/fieldguide/apis/fieldguide-api.md) · [All operations](https://skmtc.net/fieldguide/apis/fieldguide-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fieldguide/fieldguide-api/revisions/6f6009a58cdd/schema)