---
title: "POST Pending Reason"
slug: "post-pending-reason"
updated: 2026-08-30T08:02:16Z
published: 2026-08-30T08:02:16Z
canonical: "help.symphonysummitai.com/post-pending-reason"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# POST Pending Reason

The POST Pending Reason Incident Master API creates a new Pending Reason master record in the Incident Management (IM) module. Authorized administrators, integrations, and automation tools can create Pending Reason records without using the application UI.

## Endpoint

```http
POST /API/v1/Master/IM/PendingReason
```

## Path Details

| Path Value | Description |
| --- | --- |
| `IM` | Module code for Incident Management. |
| `PendingReason` | Master entity used to create the new record. |

> **Note:** Before creating Pending Reason record, system retrieves its metadata to review required fields, supported fields, payload structure, constraints, and applicable endpoints. `GET /API/v1/Master/IM/PendingReason/metadata?sections=create`.

### Sample Metadata Request

```bash
curl --location 'https://<host>/API/v1/Master/IM/PendingReason/metadata?sections=create' \
  --request GET \
  --header 'Accept: application/json' \
  --header 'X-Api-Key: <API_KEY>'
```

## Request Headers

| Header | Value | Required | Description |
| --- | --- | --- | --- |
| `Accept` | `application/json` | Yes | Specifies the expected response format. |
| `Content-Type` | `application/json` | Yes | Specifies that the request body is in JSON format. |
| `X-Api-Key` | `&lt;API_KEY&gt;` | Yes | API key used to authenticate the request. |

## Sample Payload

```json
{
  "Active": true,
  "Text": "Sample Pending Reason",
  "Instance": "Info"
}
```

### Sample Payload Field Details

| Field Name | Sample Value | Data Type | Description |
| --- | --- | --- | --- |
| Active | `true` | Boolean | Indicates whether the Pending Reason record is active and available for use. |
| Text | `"Sample Pending Reason"` | String | Specifies the display name of the Pending Reason record. |
| Instance | `"Info"` | String | Specifies the application instance associated with the Pending Reason record. |

## Sample Request

```bash
curl --location 'https://<host>/API/v1/Master/IM/PendingReason' \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <API_KEY>' \
  --data-raw '{
    "Active": true,
    "Text": "Sample Pending Reason",
    "Instance": "Info"
  }'
```

### Sample Request Details

| Component | Value | Description |
| --- | --- | --- |
| HTTP Method | `POST` | Creates a new Pending Reason master record. |
| Endpoint URL | `https://&lt;host&gt;/API/v1/Master/IM/PendingReason` | API endpoint used to create a Pending Reason record. |
| Host | `&lt;host&gt;` | Base URL of the target environment, such as Development, Test, or Production. |
| API Version | `v1` | Identifies Version 1 of the API. |
| Resource Group | `Master` | Identifies the Master Data API resource group. |
| Module | `IM` | Identifies the Incident Management module. |
| Master Name | `PendingReason` | Identifies the Pending Reason master entity. |
| Accept Header | `application/json` | Indicates that the client expects the response in JSON format. |
| Content-Type Header | `application/json` | Indicates that the request body contains JSON data. |
| X-Api-Key Header | `&lt;API_KEY&gt;` | API key used to authenticate and approve the request. |
| Request Body | JSON payload | Contains the values used to create the Pending Reason record. |

### Request Body Details

| Field Name | Sample Value | Data Type | Required | Description |
| --- | --- | --- | --- | --- |
| Active | `true` | Boolean | Yes | Creates the Pending Reason as an active record that is available for use. |
| Text | `"Sample Pending Reason"` | String | Yes | Sets the display name of the Pending Reason record. |
| Instance | `"Info"` | String | Yes | Associates the Pending Reason with the specified application instance. |

The request creates an active Pending Reason named `Sample Pending Reason` and associates the record with the specified application instance.

## Sample Success Response

### HTTP 201 Created

```json
{
  "message": "Master record created successfully.",
  "data": {
    "success": true,
    "recordId": 17,
    "displayName": "PendingReason",
    "moduleCode": "IM",
    "operation": "INSERT",
    "rowsAffected": 1
  },
  "executionTime": 0.0553389
}
```

A successful request creates the Pending Reason record and returns the generated record identifier and execution details.

### Sample Success Response Field Details

| Field Name | Sample Value | Data Type | Description |
| --- | --- | --- | --- |
| message | `"Master record created successfully."` | String | Confirms the API created the Pending Reason record successfully. |
| data | Response object | Object | Contains details about the completed create operation. |
| data.success | `true` | Boolean | Indicates whether the Pending Reason creation operation succeeded. |
| data.recordId | `17` | Integer | Unique identifier generated for the newly created Pending Reason record. |
| data.displayName | `"PendingReason"` | String | Identifies the created master entity. |
| data.moduleCode | `"IM"` | String | Identifies the Incident Management module associated with the new record. |
| data.operation | `"INSERT"` | String | Indicates that the API performed an insert operation. |
| data.rowsAffected | `1` | Integer | Indicates the number of Pending Reason records created by the request. |
| executionTime | `0.0553389` | Number | Indicates the time taken to process the request, in seconds. |

A successful request returns HTTP `201 Created`. The response confirms that the API created a new Pending Reason record, generated record ID `17`, and affected one record.

## Error Responses

### 400 Bad Request

Returned when the payload is invalid, a required field is missing, or a supplied value fails validation.

```json
{
  "message": "Invalid request payload.",
  "errorCode": 400,
  "details": "One or more fields failed validation."
}
```

### 401 Unauthorized

Returned when valid API credentials are not provided or have expired.

```json
{
  "message": "Unauthorized access.",
  "errorCode": 401,
  "details": "Valid API credentials are required."
}
```

### 403 Forbidden

Returned when the authenticated client does not have permission to create Pending Reason records.

```json
{
  "message": "You do not have permission to create master records.",
  "errorCode": 403,
  "details": "The authenticated user lacks the required privileges to perform this operation."
}
```

### 404 Not Found

Returned when the Pending Reason master entity does not exist or the endpoint URL is invalid.

```json
{
  "message": "Master entity not found.",
  "errorCode": 404,
  "details": "The requested master entity or endpoint does not exist."
}
```