# Publish a web sandboxing profile

Publishes a Web Sandboxing profile and makes it active for deployment.

## Endpoints

`POST /bsp/api/v1/bmp/web_sandboxing/{profile_id}/publish`

## Request URL

`https://{server-hostname}:8383/bsp/api/v1/bmp/web_sandboxing/{profile_id}/publish`

## Scope

`BrowserManager.CREATE`

## Header

`Authorization: d92d4xxxxxxxxxxxxx15f52`

## Request Parameters

### Request Headers

- **Content-Type** `string` — Mandatory — `application/json`
- **Accept** `string` — Mandatory — `application/json`

### Path Parameters

- **profile_id** `string` — Mandatory

  Retrieve the web sandboxing profile ID from the profileid key in the response returned by [List Configuration Profiles](https://www.manageengine.com/products/desktop-central/help/api/onpremise/profiles-list-profiles.html).

### Request Body

JSON body with profile ID and platform type for publishing the web sandboxing profile.

#### application/json

`JSON Object`

Request body for publishing a configuration or web sandboxing profile.

- **PROFILE_ID** `string` — Optional

  Profile ID from [List Configuration Profiles](https://www.manageengine.com/products/desktop-central/help/api/onpremise/profiles-list-profiles.html) response (profileid field).

- **PLATFORM_TYPE** `string` — Optional

  Target platform type. `'1'` = Windows, `'2'` = Mac.

## Sample Request

```curl
curl --request POST \
  --url https://appdomain/bsp/api/v1/bmp/web_sandboxing/{profile_id}/publish \
  --header 'Accept: application/json' \
  --header 'Authorization:  d92d4xxxxxxxxxxxxx15f52' \
  --header 'Content-Type: application/json' \
  --data '{"PROFILE_ID":103,"PLATFORM_TYPE":"1"}'
```

## Sample Request Body

Publish a Windows web sandboxing profile.

```json
{
  "PROFILE_ID": 103,
  "PLATFORM_TYPE": "1"
}
```

## Response Parameters

### HTTP Code 204

#### Response Body — application/json

`JSON Object`

### HTTP Code 401

#### Response Body — application/json

`JSON Object`

- **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`

- **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`

Returned when the specified web sandboxing profile is not found.

- **error_description** `string`

  Message indicating the specified profile does not exist.

### HTTP Code 409

#### Response Body — application/json

`JSON Object`

Returned when the profile is already published.

- **error_description** `string`

  Message indicating the profile is already in published state.

### HTTP Code 412

#### Response Body — application/json

`JSON Object`

Returned when the profile has no settings configured to publish.

- **error_description** `string`

  Message indicating no settings have been saved in the profile to publish.

### HTTP Code 429

#### Response Body — application/json

`JSON Object`

- **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`

Returned when an unexpected server error occurs during profile publish.

- **error_description** `string`

  Message describing the internal server error.

- **error_code** `string`

  Error code identifying the type of server error.

## Possible Response Codes

- **204** — HTTP code

  Returns 204 No Content on success.

- **401** — HTTP code
- **403** — HTTP code
- **404** — HTTP code
- **409** — HTTP code
- **412** — HTTP code
- **429** — HTTP code
- **500** — HTTP code

## Sample Response: HTTP 204

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

## Sample Response: HTTP 401

Unauthorized

```json
{
  "errorCode": "UNAUTHORIZED",
  "errorMsg": "You are not authorized to perform this action"
}
```

## Sample Response: HTTP 403

Forbidden

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

## Sample Response: HTTP 404

Profile not found

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

## Sample Response: HTTP 409

Already published

```json
{
  "error_description": "Profile already published."
}
```

## Sample Response: HTTP 412

No settings saved

```json
{
  "error_description": "No Settings Saved To be Published"
}
```

## Sample Response: HTTP 429

Rate limit exceeded

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

## Sample Response: HTTP 500

Server error

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

## Rate Limits

![](https://www.zohowebstatic.com/sites/zweb/images/people/ico-help.png)

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