# Deploy configuration profiles to specific devices

Associates one or more published configuration profiles to specific devices for deployment. Both `profile_ids` and `device_ids` arrays are required with a maximum of 1000 items each. Only published profiles (status 110) can be associated.

## Endpoint

`POST /bsp/api/v1/bmp/profiles/devices`

## Request

### Request URL

`https://{server-hostname}:8383/bsp/api/v1/bmp/profiles/devices`

### Scope

`BrowserManager.CREATE`

### Header

`Authorization: d92d4xxxxxxxxxxxxx15f52`

### Request Parameters

#### Request Headers

| Name | Type | Required | Value |
|---|---|---|---|
| Content-Type | string | Mandatory | application/json |
| Accept | string | Mandatory | application/json |

#### Request Body

JSON body containing `profile_ids` and `device_ids` arrays for profile-to-device association.

Content type: `application/json`

**JSON Object**

Request body for associating profiles to devices.

| Attribute | Type | Required | Description |
|---|---|---|---|
| device_ids | array | Optional | Required. Device resource IDs from [List Devices](https://www.manageengine.com/products/desktop-central/help/api/onpremise/inventory-list-devices.html) response (`device_id` field). Max 1000 |
| profile_ids | array | Optional | Profile IDs from [List Profiles](https://www.manageengine.com/products/desktop-central/help/api/onpremise/profiles-list-profiles.html) response (`profile_id` field). Max 1000, only published profiles allowed |

### Sample Request

```curl
curl --request POST \
  --url https://appdomain/bsp/api/v1/bmp/profiles/devices \
  --header 'Accept: application/json' \
  --header 'Authorization:  d92d4xxxxxxxxxxxxx15f52' \
  --header 'Content-Type: application/json' \
  --data '{"device_ids":[999,888],"profile_ids":[111]}'
```

### Sample Request Body

Associate two profiles to two devices.

```json
{
  "device_ids": [
    999,
    888
  ],
  "profile_ids": [
    111
  ]
}
```

## Response Parameters

### HTTP Code 204

Response body: `application/json`

**JSON Object**

### HTTP Code 400

Response body: `application/json`

**JSON Object**

Bad request error for invalid input or constraint violations.

| Attribute | Type | Description |
|---|---|---|
| errorcode | string | Error code identifying the specific validation failure |
| errormsg | string | Message describing the validation failure |

### HTTP Code 401

Response body: `application/json`

**JSON Object**

| Attribute | Type | Description |
|---|---|---|
| errorCode | long | Unauthorized error code returned when authentication credentials are missing, expired, or invalid (authentication=required) |
| errorMsg | string | Authentication failure reason |

### HTTP Code 403

Response body: `application/json`

**JSON Object**

| Attribute | Type | Description |
|---|---|---|
| errorCode | long | Forbidden error code returned when the authenticated user does not have the required uem-roles (e.g., DataEncryption_Admin or DataEncryptionRecoveryKey_Admin) |
| errorMsg | string | Message indicating insufficient privileges to access this resource |

### HTTP Code 404

Response body: `application/json`

**JSON Object**

Resource not found error.

| Attribute | Type | Description |
|---|---|---|
| errormsg | string | Not found error message |

### HTTP Code 409

Response body: `application/json`

**JSON Object**

Conflict error due to the current state of the profile.

| Attribute | Type | Description |
|---|---|---|
| errormsg | string | Conflict error message |

### HTTP Code 429

Response body: `application/json`

**JSON Object**

| Attribute | Type | Description |
|---|---|---|
| errorCode | long | Rate limit error code returned when the API call threshold (configured via threshold/duration in security XML) is exceeded; client is locked out for lock-period minutes |
| errorMsg | string | Rate limit exceeded message with retry guidance |

### HTTP Code 500

Response body: `application/json`

**JSON Object**

Internal server error response for profile operations.

| Attribute | Type | Description |
|---|---|---|
| error_description | string | Error message describing the server failure |
| error_code | string | Error code for internal server errors |

## Possible Response Codes

| HTTP Code | Description |
|---|---|
| 204 | Returns 204 No Content on success. |
| 400 |  |
| 401 |  |
| 403 |  |
| 404 |  |
| 409 |  |
| 429 |  |
| 500 |  |

## Sample Responses

### HTTP 204

```text
204 Returns 204 No Content on success.
```

### HTTP 400

Invalid request parameters.

```json
{
  "errorcode": "IAM0003",
  "errormsg": "Invalid request."
}
```

### HTTP 401

API key is missing or invalid.

```json
{
  "errorCode": "IAM0001",
  "errorMsg": "Authentication key is invalid. Please regenerate the key and try again."
}
```

### HTTP 403

Forbidden.

```json
{
  "errorCode": "FORBIDDEN",
  "errorMsg": "User does not have permission to perform this operation"
}
```

### HTTP 404

The specified profile does not exist or is in trash.

```json
{
  "errormsg": "Profile not found"
}
```

### HTTP 409

Profile must be published before it can be associated to devices.

```json
{
  "errormsg": "Profile is not published."
}
```

### HTTP 429

Rate limit exceeded.

```json
{
  "errorCode": "RATE_LIMIT_EXCEEDED",
  "errorMsg": "Too many requests. Please try again after 5 minutes"
}
```

### HTTP 500

Server error.

```json
{
  "error_description": "Internal Server error, Please try again in a moment.",
  "error_code": "COM0004"
}
```

## Rate Limits

**Duration:** 1 minute | **Threshold:** 60 | **Lock period:** 5 minutes

Duration - Time window for the threshold.  
Threshold - Number of API calls allowed within the specified duration.  
Lock Period - Wait time before consecutive API requests.