/application/delete-individual/{applicationId}/individual/{individualId}Delete Individual
Removes an individual from an application. The primary user cannot be removed unless another individual is set as primary first.
Path variables
| Field | Type | Required | Possible values | Description |
|---|---|---|---|---|
applicationId | string | Required | — | Application ID. |
individualId | string | Required | — | Individual ID to remove (from `Individuals[].Id` in GET /application/detail). |
Headers
| Field | Type | Required | Possible values | Description |
|---|---|---|---|---|
session-token | string | Required | — | SessionToken obtained from the Create GMA Session endpoint. All secured endpoints require this header. |
Response
| Field | Type | Possible values | Description |
|---|---|---|---|
ResponseCode | integer | 200 | 201 | 204 | 301 | 400 | 401 | 403 | 404 | 410 | 422 | 500 | 503 | API result code in the response envelope. Indicates success or the error category (e.g. 200 success, 400 bad request, 401 unauthorized). |
ResponseMessage | string | Success | Created | NoContent | BadRequest | Unauthorized | Forbidden | NotFound | Gone | UnprocessableContent | ServerError | ResourceMoved | ServiceUnAvailable | UnProcessableEntity | Human-readable label paired with ResponseCode (e.g. Success, BadRequest, Unauthorized). Use with ResponseCode to interpret the outcome. |
ResponseData | object | Please refer to below example for response body | Returns the string `"success"` on successful deletion. |
Example response
{
"ResponseCode": 200,
"ResponseMessage": "Success",
"ResponseData": "success"
}Returns 400 if the application is locked or the individual cannot be removed.
ℹ Note
A 423 Application Locked response is returned when the application is in a locked or final status. No further modifications are permitted until FV Bank unlocks the application.
ℹ Note
On 400 validation errors, each error in ResponseErrors includes a Field property that identifies the failing PascalCase request body field (e.g. Business.Phone, Email, Address.City). Use this to surface precise field-level error messages in your UI.
Requires `session-token: {SessionToken}` from Create GMA Session. Use the same client IP as authentication.