--- title: "Report a death or terminal illness" method: POST path: "/lifetime-isa/manager/{lisaManagerReferenceNumber}/accounts/{accountId}/events" tags: ["Life Events"] --- # Report a death or terminal illness `POST /lifetime-isa/manager/{lisaManagerReferenceNumber}/accounts/{accountId}/events` Report to HMRC if an investor has been diagnosed with a terminal illness or died. You need to do this to get a lifeEventId before you can request a bonus payment from HMRC. ### Test data
Scenario Request Payload Response

Request with a valid payload, LISA Manager reference number and account ID

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234567890

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 201 (Created)

{
  "status": 201,
  "success": true,
  "data": {
    "message": "Life event created",
    "lifeEventId": "1234567891"
  }
}

Request with a valid payload and accountID, but an invalid LISA Manager reference number

lisaManagerReferenceNumber: 123456
accountId: 1234567890

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 400 (Bad Request)

{
  "code": "BAD_REQUEST",
  "message": "Enter lisaManagerReferenceNumber in the correct format, like Z1234"
}

Request with a valid payload and LISA Manager reference number, but an invalid account ID

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234%3D5678

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 400 (Bad Request)

{
  "code": "BAD_REQUEST",
  "message": "Enter accountId in the correct format, like ABC12345"
}

Request containing invalid and/or missing data

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234567890

 
{
  "eventType": "Invalid Event Type"
}

HTTP status: 400 (Bad Request)

{
  "code": "BAD_REQUEST",
  "message": "Bad Request",
  "errors": [
    {
      "code": "MISSING_FIELD",
      "message": "This field is required",
      "path": "/eventDate"
    },
    {
      "code": "INVALID_FORMAT",
      "message": "Invalid format has been used",
      "path": "/eventType"
    }
  ]
}

Request containing an event date before 6 April 2017

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234567890

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-05"
}

HTTP status: 403 (Forbidden)

{
  "code": "FORBIDDEN",
  "message": "There is a problem with the request data",
  "errors": [
    {
      "code": "INVALID_DATE",
      "message": "The eventDate cannot be before 6 April 2017",
      "path": "/eventDate"
    }
  ]
}

Request containing a life event that conflicts with a previously reported event

lisaManagerReferenceNumber: Use your test user profile
accountId: 0000000403

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 403 (Forbidden)

{
  "code": "LIFE_EVENT_INAPPROPRIATE",
  "message": "The life event conflicts with a previous life event reported"
}

Request for an account that has already been closed

lisaManagerReferenceNumber: Use your test user profile
accountId: 1000000403

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 403 (Forbidden)

{
  "code": "INVESTOR_ACCOUNT_ALREADY_CLOSED",
  "message": "The LISA account is already closed"
}

Request for an account that has already been cancelled

lisaManagerReferenceNumber: Use your test user profile
accountId: 2000000403

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 403 (Forbidden)

{
  "code": "INVESTOR_ACCOUNT_ALREADY_CANCELLED",
  "message": "The LISA account is already cancelled"
}

Request for an account that has already been void

lisaManagerReferenceNumber: Use your test user profile
accountId: 3000000403

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 403 (Forbidden)

{
  "code": "INVESTOR_ACCOUNT_ALREADY_VOID",
  "message": "The LISA account is already void"
}

Request containing an account ID that does not exist

lisaManagerReferenceNumber: Use your test user profile
accountId: 0000000404

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 404 (Not found)

{
  "code": "INVESTOR_ACCOUNTID_NOT_FOUND",
  "message": "Enter a real accountId"
}

Request with an invalid 'Accept' header

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234567890

Accept: application/vnd.hmrc.1.0

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 404 (Not Found)

{
  "code": "MATCHING_RESOURCE_NOT_FOUND",
  "message": "A resource with the name in the request can not be found in the API"
}

Request containing an already reported event

lisaManagerReferenceNumber: Use your test user profile
accountId: 0000000409

 
{
  "eventType": "LISA Investor Terminal Ill Health",
  "eventDate": "2017-04-20"
}

HTTP status: 409 (Conflict)

{
  "code": "LIFE_EVENT_ALREADY_EXISTS",
  "message": "The investor’s life event has already been reported",
  "lifeEventId": "1234567891"
}
## Path parameters - `lisaManagerReferenceNumber` string, required - `accountId` string, required ## Headers - `Accept` 'application/vnd.hmrc.2.0+json', required - `Content-Type` 'application/json', required - `Authorization` string, required ## Request body - object - `eventType` 'LISA Investor Death' | 'LISA Investor Terminal Ill Health', required — The event that has occurred and triggers eligibility for the bonus payment. - `eventDate` string, required ## Response `201` Created - object - `status` number, required — The HTTP status of the result of the API call. Always 201. - `success` boolean, required — Whether the API call was successful or not. Always true. - `data` object, required — Response details. - `message` 'Life event created', required — A human-readable explanation for the result of the API call. - `lifeEventId` string, required — The life event’s ID reference number. You must store this ID as it is needed for other API calls. ## Other responses - `400` — Bad Request - `401` — Unauthorized - `403` — Forbidden - `404` — Not Found - `409` — Conflict --- [API](https://skmtc.net/hmrc/apis/lisa-api.md) · [All operations](https://skmtc.net/hmrc/apis/lisa-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hmrc/lisa-api/versions/689ca71752fb/schema)