---
title: "POST /provisioning-profiles"
method: POST
path: "/provisioning-profiles"
---

# POST /provisioning-profiles

`POST /provisioning-profiles`

Create a provisioning profile for executing device provisioning flows. The provisioning profile is a document that defines the set of resources and policies applied to a device during the provisioning process.

## Request body

- object
  - `ProvisioningType` 'FLEET_PROVISIONING' | 'JITR', required — The type of provisioning workflow the device uses for onboarding to IoT managed integrations.
  - `CaCertificate` string, password — The body of the PEM-encoded certificate authority (CA) certificate.
  - `ClaimCertificate` string, password — The body of the PEM-encoded claim certificate. If a claim certificate is provided, it will be used for the provisioning profile. Otherwise, a claim certificate will be generated.
  - `Name` string — The name of the provisioning profile.
  - `ClientToken` string — An idempotency token. If you retry a request that completed successfully initially using the same client token and parameters, then the retry attempt will succeed without performing any further actions.
  - `Tags` object — A set of key/value pairs that are used to manage the provisioning profile.

## Response `201`

Success

- CreateProvisioningProfileResponse
  - `Arn` string — The Amazon Resource Name (ARN) of the provisioning profile.
  - `Name` string — The name of the provisioning profile.
  - `ProvisioningType` 'FLEET_PROVISIONING' | 'JITR' — The type of provisioning workflow the device uses for onboarding to IoT managed integrations.
  - `Id` string — The identifier of the provisioning profile.
  - `Status` 'CREATE_IN_PROGRESS' | 'CREATE_FAILED' | 'CREATED' | 'DELETE_IN_PROGRESS' | 'DELETE_FAILED' — The status of a provisioning profile.
  - `ClaimCertificate` string, password — The body of the PEM-encoded claim certificate.
  - `ClaimCertificatePrivateKey` string, password — The private key of the claim certificate. This may be stored securely on the device for validating the connection endpoint with IoT managed integrations using the public key.

## Other responses

- `480` — ValidationException
- `481` — AccessDeniedException
- `482` — InternalServerException
- `483` — UnauthorizedException
- `484` — ConflictException
- `485` — ServiceUnavailableException
- `486` — ThrottlingException
- `487` — ResourceNotFoundException

---

[API](https://skmtc.net/aws/apis/iot-managed-integrations.md) · [All operations](https://skmtc.net/aws/apis/iot-managed-integrations/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/aws/iot-managed-integrations/revisions/d043c13c812a/schema)