Skip to main content

This is a proof of concept viewer for the planning permission specifications - your feedback will help us to improve it.

submission-details

Submission details

Details about the submitted payload, including reference information, application types, specification profile, destination, documents, and fees

Fields

Submission reference
submission-reference

A unique reference for the submission

Required
True
Datatype
string
Expected number
1
Application types
application-types

A list of planning application types that define the nature of the planning application

Required
True
Datatype
enum
Allowed values
Application type codelist
Expected number
1 or more
Specification profile
specification-profile

The specification profile used to determine context-specific allowed codelist values for the application

Required
True
Datatype
enum
Expected number
1
Planning authority
planning-authority

A reference of the planning authority the application has been submitted to, e.g. local-authority:CMD for London borough of Camden

Required
True
Datatype
enum
Expected number
1
Submitted at
submitted-at

The date and time the application was submitted

Required
True
Datatype
datetime
Expected number
1
Created at
created-at

The date and time the submission payload was created

Required
True
Datatype
datetime
Expected number
1
Documents
documents
Component

List of submitted documents with references and details

Required
True
Datatype
object
Expected number
1 or more

Document component

Reference
reference

Unique reference for the document within this application submission, generated by the submitting system

Required
True
Datatype
string
Expected number
1
Name
name

The name or title of the document

Required
True
Datatype
string
Expected number
1
Description
description

Brief description of what the document contains

Required
False
Datatype
string
Expected number
1
Document types
document-types

Planning requirement references identifying the information this document provides. A document may address more than one requirement. These references identify its coverage; they do not establish that the requirements have been satisfied.

Required
True
Datatype
enum
Expected number
1 or more
Uploaded date
uploaded-date

The date the document was uploaded to the application

Required
True
Datatype
datetime
Expected number
1
File
file
Component

Details of the digital file attached to a submission

Required
True
Datatype
object
Expected number
1

This field uses the File component.

Fee
fee
Component

The fee payable for the application including amounts and transaction details

Required
False
Datatype
object
Expected number
1

Fee component

Amount
amount

The total amount due for the application fee

Required
True
Datatype
decimal
Expected number
1
Amount paid
amount-paid

The amount paid towards the application fee

Required
True
Datatype
decimal
Expected number
1
Transactions
transactions

References to payments or financial transactions related to this application

Required
False
Datatype
string
Expected number
1 or more

Where this is used

Fields

This component is used in 1 field: