--- title: "Get an Application List Entry by id" method: GET path: "/application-lists/{listId}/entries/{entryId}" tags: ["application-list-entries"] --- # Get an Application List Entry by id `GET /application-lists/{listId}/entries/{entryId}` ## Request - Base URL: `/` (relative, and the document was published on a file host, not at the API’s origin) - URL: `/application-lists/{listId}/entries/{entryId}` - Auth: none declared Returns a detailed Application List Entry while the parent Application List is in a state that permits standard entry access. Closed lists must be updated via the dedicated closed-entry endpoint and may reject this standard detail endpoint with 409 Conflict. ## Path parameters - `listId` string, uuid, required - `entryId` string, uuid, required ## Response `200` Returns a detailed Application List Entry - EntryGetDetailDto1: DTO representing a detailed Application List Entry. - `id` string, uuid, required: Unique identifier of the Application List Entry. - `listId` string, uuid, required: The Unique identifier of the Application List this Entry belongs to. - `standardApplicantCode` string: Code that identifies the Standard Applicant. - `standardApplicantId` integer, nullable: ID that identifies the Standard Applicant. - `applicationCodeId` integer, required: ID of the exact persisted Application Code association, including historical versions. - `applicationCode` string, required: Code that identifies the Application Code. - `applicant` Applicant: The applicant making the application. In application read and print responses, Standard Applicants are represented by their reference name in organisation.name (or their code when no reference name exists). Their personal and contact values are not returned. For these read responses the shared input contact constraints do not apply: contact fields may be null or absent. Ordinary applicant input still requires the person or organisation contact details. - `person` Person: The person making, or responding to, the application. - `name` FullName, required: A persons full name. Blank fields will be rejected, nulls should be used instead. - `title` string: Prefix before a persons name. - `firstName` string, required: The person's first name. - `middleName` string, nullable: The person's optional middle name or names. - `lastName` string, required: The person's family name. - `contactDetails` ContactDetails, required: A participant's contact details. Blank fields will be rejected, nulls should be used instead. - `addressLine1` string, required: Line one of the participant's address. - `addressLine2` string, nullable: Line two of the participant's address. - `addressLine3` string, nullable: Line three of the participant's address. - `addressLine4` string, nullable: Line four of the participant's address. - `addressLine5` string, nullable: Line five of the participant's address. - `postcode` string: The participant's postcode. - `phone` string, nullable: The participant's home-phone number. - `mobile` string, nullable: The participant's mobile number. - `email` string, nullable: The participant's email address. - `organisation` Organisation: The organisation making, or responding to, the application. Blank fields will be rejected, nulls should be used instead. - `name` string, required: The name of the organisation. - `contactDetails` ContactDetails, required: A participant's contact details. Blank fields will be rejected, nulls should be used instead. - `addressLine1` string, required: Line one of the participant's address. - `addressLine2` string, nullable: Line two of the participant's address. - `addressLine3` string, nullable: Line three of the participant's address. - `addressLine4` string, nullable: Line four of the participant's address. - `addressLine5` string, nullable: Line five of the participant's address. - `postcode` string: The participant's postcode. - `phone` string, nullable: The participant's home-phone number. - `mobile` string, nullable: The participant's mobile number. - `email` string, nullable: The participant's email address. - `respondent` Respondent: The respondent to the application. - `person` RespondentPerson: Person details for a respondent (includes DOB). - `name` FullName, required: A persons full name. Blank fields will be rejected, nulls should be used instead. - `title` string: Prefix before a persons name. - `firstName` string, required: The person's first name. - `middleName` string, nullable: The person's optional middle name or names. - `lastName` string, required: The person's family name. - `contactDetails` ContactDetails, required: A participant's contact details. Blank fields will be rejected, nulls should be used instead. - `addressLine1` string, required: Line one of the participant's address. - `addressLine2` string, nullable: Line two of the participant's address. - `addressLine3` string, nullable: Line three of the participant's address. - `addressLine4` string, nullable: Line four of the participant's address. - `addressLine5` string, nullable: Line five of the participant's address. - `postcode` string: The participant's postcode. - `phone` string, nullable: The participant's home-phone number. - `mobile` string, nullable: The participant's mobile number. - `email` string, nullable: The participant's email address. - `dateOfBirth` string, date: Date of birth (only applicable for person respondents). - `organisation` Organisation: The organisation making, or responding to, the application. Blank fields will be rejected, nulls should be used instead. - `name` string, required: The name of the organisation. - `contactDetails` ContactDetails, required: A participant's contact details. Blank fields will be rejected, nulls should be used instead. - `addressLine1` string, required: Line one of the participant's address. - `addressLine2` string, nullable: Line two of the participant's address. - `addressLine3` string, nullable: Line three of the participant's address. - `addressLine4` string, nullable: Line four of the participant's address. - `addressLine5` string, nullable: Line five of the participant's address. - `postcode` string: The participant's postcode. - `phone` string, nullable: The participant's home-phone number. - `mobile` string, nullable: The participant's mobile number. - `email` string, nullable: The participant's email address. - `numberOfRespondents` integer, nullable, required: Number of respondents required by the Application. - `wording` TemplateDetail: The wording details - `template` string, required: The template name. It contains the field names between curly braces. - `substitution-key-constraints` TemplateKeyWithConstraint[]: A list of fields and the associated constraints - `key` string, required: Field key for substitution into the template. - `value` string: The optional value for the key. - `constraint` TemplateConstraint, required: The template field with an associated value - `type` 'TEXT', required: The data type of the value. - `length` integer, required: The length of the data value. - `feeStatuses` FeeStatus[] - `paymentReference` string: The reference code used to identify the payment. - `paymentStatus` 'PAID' | 'UNDERTAKEN' | 'DUE' | 'REMITTED', required: The Status of the Fee's Payment. - `statusDate` string, date, required: The date when the payment status was updated. Must be today's date or a past date. - `hasOffsiteFee` boolean: Indicates whether an off-site fee applies. - `caseReference` string: A reference code to identify a related case (maximum 15 characters). - `accountNumber` string: The Applicants account number (maximum 20 characters). - `notes` string: Notes about the application or the hearing (maximum 4000 characters). - `lodgementDate` string, date, required: The date on which the application was submitted. Will be set to current date if omitted. - `officials` Official[]: An array of Officials who will decide the outcome of the Application. - `title` string: Prefix before a persons name. - `surname` string: The persons family name. - `forename` string: The persons first name. - `type` 'MAGISTRATE' | 'CLERK': The type of Official hearing the application. ## Other responses - `400`: Invalid request parameters. - `401`: Authentication required or token invalid. - `403`: Authenticated but not permitted to perform this action. - `404`: The requested resource was not found. - `409`: Conflict with the current state of the resource. - `500`: Unexpected server error. ## Changes - **2026-10-28** `36521cfe1ab7`: 1 info - added the optional property `standardApplicantId` to the response with the `200` status - **2026-10-27** `269185a6fe8a`: 1 info - added the required property `applicationCodeId` to the response with the `200` status - **2026-07-29** `8a3c6d9862a3`: 1 info - the response property `wording/substitution-key-constraints/items/key` became required for the status `200` - **2026-07-20** `9a5b195ecd33`: 1 breaking - the response property `numberOfRespondents` became nullable for the status `200` - **2026-06-15** `4af596840442`: 1 info - added the non-success response with the status `409` [Operation history](https://skmtc.dev/hm-courts-and-tribunals-service/apis/applications-register-api/changes/application-lists/:listId/entries/:entryId/get.md) --- [API](https://skmtc.dev/hm-courts-and-tribunals-service/apis/applications-register-api.md) - [All operations](https://skmtc.dev/hm-courts-and-tribunals-service/apis/applications-register-api/llms.txt) - [OpenAPI document](https://skmtc.dev/hm-courts-and-tribunals-service/apis/applications-register-api/revisions/36521cfe1ab7?raw)