---
title: "Upload and fully approve a template in one call"
method: POST
path: "/templates/single-step"
tags: ["Template"]
---

# Upload and fully approve a template in one call

`POST /templates/single-step`

Executes the complete template workflow in a single request: creates the template record, uploads `template.csv` and `mappings.csv` to GCS, records a column mapping per CSV row, generates the JSON validation schema (`schema.json`), and sets the template status to `success`.

**When to use:** Prefer this endpoint when the column-to-field mapping is known in advance and no human review of suggestions is needed. Use the legacy two-step flow (`POST /templates` then `PUT /templates/{id}` then `PUT /templates/{id}/approve`) when you need to inspect or adjust auto-suggested mappings before committing.

**How:** Send a `multipart/form-data` request with the required `tenant-id` header and fields: `name` (display name), `type` (`PRACTITIONER`, `FACILITY`, or `GROUP` - `GROUP` requires the tenant's `supportGroupRosters` configuration, otherwise 400), `description` (optional), and `file`. The file must have a `.csv` extension (400 otherwise) and is a *mappings-definition* CSV: each row defines one roster column (header name, mapped Certify attribute, required flag, optional multiple-value group and separator). Every row must carry a mapped attribute; rows with missing mapping keys cause a 400.

**Returns:** A `SingleStepTemplateFlowResponse` with the new `templateId`, the resolved `fields`, the final `status` (`success`, or `failure` if schema generation failed - the record then stays `in-progress`), and the GCS object paths `schemaUrl` and `templateUrl` (paths, not signed URLs). On `success` the template is immediately usable for roster uploads.

## Headers

- `tenant-id` string, required

## Response `200`

The created template's ID, resolved column mappings, final status, and artifact object paths.

- SingleStepTemplateFlowResponse — Result of a single-step template create or update: the resolved column mappings, final status, and the GCS object paths of the template artifacts.
  - `fields` Field[] — The template's resolved column mappings. After a file upload these are the mappings extracted from the uploaded mappings CSV; after a metadata-only update they are the template's existing stored columns.
    - `name` string — CSV column header this mapping applies to, exactly as it appears in the roster file.
    - `mappedKey` string — Key of the Certify system field this column maps to, from the field catalog returned by `GET /templates/fields`. The sentinel `[skipped]` marks a column the user explicitly chose not to map: skipped columns persist in the template/mappings CSVs but are excluded from the generated validation schema.
    - `mappedEntity` string — Entity that owns the mapped attribute (for example `practitioner` or `location`). When set, `mappedKey` is accepted as-is instead of being validated against the system-field catalog.
    - `entityGroup` string — Group label linking columns that belong to the same repeating entity instance (a multiple-value group), so related columns are ingested together.
    - `isRequired` boolean — Whether every roster row must supply a value for this column; drives the `required` constraint in the generated validation schema.
    - `isStaticField` boolean — Catalog metadata: whether the mapped system field is a static (fixed-value) field rather than one populated from roster data.
    - `isSingleSelect` boolean — Catalog metadata: whether the mapped system field accepts a single value from a fixed option list.
    - `validationRegex` string — Regular expression applied to this column's values during roster validation. Rows whose values do not match are rejected.
    - `description` string — Human-readable description of the mapped system field, from the field catalog.
    - `enum` string[] — Allowed values for enum-type system fields; roster values outside this list fail validation. Absent for free-form fields.
    - `separator` string — Literal separator character used to split a single cell value into multiple tokens for multi-value attributes. Blank or absent defaults to a comma at schema-generation time.
    - `singleSelect` boolean
    - `skipped` boolean
  - `status` string — Final template status. `success` when the validation schema was generated and the template is ready for roster uploads; `failure` when schema generation failed with an I/O error. Metadata-only updates preserve and return the template's existing status.
  - `templateId` string — Server-generated ID of the created or updated template.
  - `templateUrl` string — GCS object path (not a signed URL) of the stored template CSV. Fetch a signed download URL via `GET /templates/{id}`, which returns it as `templateUrl` in the record's `data`.
  - `schemaUrl` string — GCS object path (not a signed URL) of the generated JSON validation schema. Fetch a signed download URL via `GET /templates/{id}`, which returns it as `schemaUrl` in the record's `data`.

## Other responses

- `400` — The file is not a `.csv`, a mapping row is missing its mapped attribute, or the requested `GROUP` type is not enabled for the tenant. The `errors` list carries the cause; correct the file or request and retry.
- `401` — Authentication required - supply a valid bearer token.
- `403` — The authenticated user lacks the `CREATE_TEMPLATE` permission.
- `500` — Unexpected server-side failure (for example a GCS or data-layer outage). Safe to retry once the underlying issue clears; a retry creates a new template record.

---

[API](https://skmtc.net/certifyos/apis/certify-api-layer.md) · [All operations](https://skmtc.net/certifyos/apis/certify-api-layer/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/certifyos/certify-api-layer/revisions/563848e0ecc0/schema)