--- title: "Request a property purchase extension" method: POST path: "/lifetime-isa/manager/{lisaManagerReferenceNumber}/accounts/{accountId}/events/purchase-extensions" tags: ["Life Events"] --- # Request a property purchase extension `POST /lifetime-isa/manager/{lisaManagerReferenceNumber}/accounts/{accountId}/events/purchase-extensions` Request an extension to your request to release funds to buy a property. ### Test data
Scenario Request Payload Response

First purchase extension

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234567890 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-05-10",
  "eventType": "Extension one"
}

HTTP status: 201 (Created)

{
  "status": 201,
  "success": true,
  "data": {
    "message": "Extension created",
    "lifeEventId": "6789000001"
  }
}

Superseded first purchase extension

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234567890 

{
  "eventDate": "2017-05-11",
  "eventType": "Extension one",
  "supersede": {
    "originalEventDate": "2017-05-10",
    "originalLifeEventId": "6789000001"
  }
}

HTTP status: 201 (Created)

{
  "status": 201,
  "success": true,
  "data": {
    "message": "Extension superseded",
    "lifeEventId": "6789000002"
  }
}

Second purchase extension

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234567890 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-08-10",
  "eventType": "Extension two"
}

HTTP status: 201 (Created)

{
  "status": 201,
  "success": true,
  "data": {
    "message": "Extension created",
    "lifeEventId": "6789000003"
  }
}

Superseded second purchase extension

lisaManagerReferenceNumber: Use your test user profile
accountId: 1234567890 

{
  "eventDate": "2017-08-11",
  "eventType": "Extension two",
  "supersede": {
    "originalEventDate": "2017-08-10",
    "originalLifeEventId": "6789000003"
  }
}

HTTP status: 201 (Created)

{
  "status": 201,
  "success": true,
  "data": {
    "message": "Extension superseded",
    "lifeEventId": "6789000004"
  }
}

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

lisaManagerReferenceNumber: 123456
accountId: 1234567890 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-05-10",
  "eventType": "Extension one"
}

HTTP status: 400 (Bad Request)

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

Request with a valid payload and an invalid account ID

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

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-05-10",
  "eventType": "Extension one"
}

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 

{
  "eventDate": "10-05-2017",
  "eventType": "Extension 1"
}

HTTP status: 400 (Bad Request)

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

The LISA account is already closed

lisaManagerReferenceNumber: Use your test user profile
accountId: 1000000403 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-08-10",
  "eventType": "Extension one"
}

HTTP status: 403 (Forbidden)

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

The LISA account is already cancelled

lisaManagerReferenceNumber: Use your test user profile
accountId: 2000000403 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-08-10",
  "eventType": "Extension one"
}

HTTP status: 403 (Forbidden)

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

The LISA account is already void

lisaManagerReferenceNumber: Use your test user profile
accountId: 3000000403 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-08-10",
  "eventType": "Extension one"
}

HTTP status: 403 (Forbidden)

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

A first extension has not yet been approved

lisaManagerReferenceNumber: Use your test user profile
accountId: 7000000403 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-08-10",
  "eventType": "Extension one"
}

HTTP status: 403 (Forbidden)

{
  "code": "FIRST_EXTENSION_NOT_APPROVED",
  "message": "A first extension has not yet been approved"
}

First extension already approved

lisaManagerReferenceNumber: Use your test user profile
accountId: 8000000403 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-05-10",
  "eventType": "Extension one"
}

HTTP status: 403 (Forbidden)

{
  "code": "FIRST_EXTENSION_ALREADY_APPROVED",
  "message": "A first extension has already been approved",
  "lifeEventId": "6789000001"
}

Second extension already approved

lisaManagerReferenceNumber: Use your test user profile
accountId: 9000000403 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-08-10",
  "eventType": "Extension two"
}

HTTP status: 403 (Forbidden)

{
  "code": "SECOND_EXTENSION_ALREADY_APPROVED",
  "message": "A second extension has already been approved",
  "lifeEventId": "6789000003"
}

Supersede details do not match the original request

lisaManagerReferenceNumber: Use your test user profile
accountId: 5000000403 

{
  "eventDate": "2017-05-11",
  "eventType": "Extension one",
  "supersede": {
    "originalEventDate": "2017-05-10",
    "originalLifeEventId": "6789000001"
  }
}

HTTP status: 403 (Forbidden)

{
  "code": "SUPERSEDED_LIFE_EVENT_MISMATCH_ERROR",
  "message": "originalLifeEventId and the originalEventDate do not match the information in the original request"
}

Account not found

lisaManagerReferenceNumber: Use your test user profile
accountId: 0000000404 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-05-10",
  "eventType": "Extension one"
}

HTTP status: 404 (Not Found)

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

Fund release not found

lisaManagerReferenceNumber: Use your test user profile
accountId: 1000000404 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-05-10",
  "eventType": "Extension one"
}

HTTP status: 404 (Not Found)

{
  "code": "FUND_RELEASE_NOT_FOUND",
  "message": "The fundReleaseId does not match HMRC’s records"
}

Extension already exists

lisaManagerReferenceNumber: Use your test user profile
accountId: 0000000409 

{
  "fundReleaseId": "3456789001",
  "eventDate": "2017-05-10",
  "eventType": "Extension one"
}

HTTP status: 409 (Conflict)

{
  "code": "LIFE_EVENT_ALREADY_EXISTS",
  "message": "The investor’s life event has already been reported",
  "lifeEventId": "6789000001"
}

The associated fund release has been superseded

lisaManagerReferenceNumber: Use your test user profile
accountId: 2000000409 

{
  "fundReleaseId": "3456789000",
  "eventDate": "2017-05-10",
  "eventType": "Extension one"
}

HTTP status: 409 (Conflict)

{
  "code": "FUND_RELEASE_SUPERSEDED",
  "message": "This fund release has already been superseded",
  "lifeEventId": "3456789001"
}

The extension you are superseding has already been superseded

lisaManagerReferenceNumber: Use your test user profile
accountId: 1000000409 

{
  "eventDate": "2017-05-11",
  "eventType": "Extension one",
  "supersede": {
    "originalEventDate": "2017-05-10",
    "originalLifeEventId": "6789000001"
  }
}

HTTP status: 409 (Conflict)

{
  "code": "SUPERSEDED_LIFE_EVENT_ALREADY_SUPERSEDED",
  "message": "This life event has already been superseded",
  "lifeEventId": "6789000002"
}
## 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 - `fundReleaseId` string — The reference number you get when you report a fund release. Must not be provided when correcting an existing extension. - `eventDate` string, required — The date the extension is requested. This cannot be in the future. - `eventType` 'Extension one' | 'Extension two', required — The type of extension. - `supersede` object — Correct an existing extension. - `originalLifeEventId` string, required — The ID of the extension affected by the correction. - `originalEventDate` string, required — The eventDate of the extension affected by the correction. ## 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` 'Extension created' | 'Extension superseded', required — A human-readable explanation for the result of the API call. - `lifeEventId` string, required — The extension’s ID reference number. You must store this ID as it is needed for other API calls. ## Other responses - `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/revisions/689ca71752fb/schema)