Applications

Get application by council and reference

Fetch the stored record using a council ID and URL-encoded council reference. This does not re-check the council's planning page. Use the returned application id with POST /v1/applications/{id}/refresh for a supported queued source check, then inspect freshness on a subsequent read. include=supplier adds pilot supplier insights. This is a metered request with the same free/paid restrictions as application ID lookup.

get/v1/applications/ref/{council}/{reference}

Request

  • Base URL: https://api.planwire.io
  • URL: https://api.planwire.io/v1/applications/ref/{council}/{reference}
  • Auth: API key in header X-API-Key

Path parameters

councilstring required
referencestring required

Encode embedded slashes, for example 24%2F00123%2FFUL.

Query parameters

includestring
Example:supplier

Set to supplier to add pilot-1 supplierInsights: description-rule classifications, literal quantities, explicit references and geographic reasons. No demand or construction-start inference. Existing auth, metering and data-access limits apply.

Response

Success

Example response

{
  "data": {
    "councilId": "camden",
    "reference": "2025/0234/P",
    "applicationType": "Householder",
    "status": "Pending",
    "council": {
      "id": "hounslow",
      "name": "London Borough of Hounslow"
    },
    "source": {
      "type": "assure",
      "label": "Assure"
    },
    "freshness": {
      "recordCheckError": "source_timeout"
    },
    "nearbyPrices": {
      "periodYears": 2
    },
    "supplierInsights": {
      "classification": {
        "roleEvidence": {
          "field": "description"
        },
        "categories": [
          {
            "evidence": {
              "field": "description"
            }
          }
        ]
      },
      "quantities": {
        "dwellingMentions": [
          {
            "evidence": {
              "field": "description"
            }
          }
        ],
        "floorAreaMentions": [
          {
            "evidence": {
              "field": "description"
            }
          }
        ]
      },
      "history": {
        "references": [
          {
            "evidence": {
              "field": "description"
            }
          }
        ]
      }
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.