Error reference
All the possible errors returned by the PropertyData API, with further explanation and recommended actions:
| Code | Message | Explanation / recommended action |
| X01 | Invalid API method | Check the API method is spelled correctly and that it follows immediately after the base URL, e.g. https://api.propertydata.co.uk/method-name. If in doubt, try with the example URL from the documentation first. |
| X02 | Missing input: key | You have not supplied an API key. Every PropertyData API call requires a key, in the querystring using the variable 'key'. If you're logged in to PropertyData, the example URLs in the API documentation are automatically populated with your API key. |
| X03 | Invalid input: key | You supplied an API key, but it was not recognised. Check that your key is correct. Note that this is the error you would receive if you regenerated your API key in your account home, but were trying to use the old key in your application. |
| X04 | Monthly plan limit exceeded: N calls | You have reached your API plan call limit. Note that calls limits are reset at 00:01 on the first day of each calendar month. Consider upgrading your plan. |
| X05 | Account associated with API key cancelled or card declined | The PropertyData account associated with the API key you supplied has been cancelled or had it's card declined. Login and reactivate the account if you wish to continue using the PropertyData API. |
| X06 | Missing input: postcode | You have not supplied a postcode. All API methods except 'stamp-duty' require a full UK postcode, in the querystring using the variable 'postcode'. |
| X07 | Invalid input: postcode | The postcode you supplied was not recognised as a full UK postcode. Most of the time this means the postcode is not valid, although it can also mean the postcode is newly allocated. Try a different postcode. |
| X08 | Insufficient data found | Not enough relevant data points could be found to return analytics. See 'Data collection logic' in Getting started to understand more. |
| X09 | Uncaught exception | An unexpected error occuring in processing your API request. Please contact us, copying and pasting your API request URL. |
| X10 | Full postcode required for this method | You cannot use a postcode district or sector on this method, please use only a full UK postcode. |
| X11 | Method only available in England & Wales | Due to source data limitations, some PropertyData API methods are only available in England & Wales. See the Getting started page for a breakdown. |
| X12 | Invalid points: min 15, max 100 | If you supply the number of points to analyse, this must be between 15 and 100. Otherwise the default of 20 will be used. |
| X13 | Free trial limit exceeded: 500 calls | During your API free trial you can only make 500. Please manually start your first month. |
| 102 | Invalid filter: number of bedrooms | The value you supplied in the 'bedrooms' filter variable was not valid. Valid values are 1, 2, 3, 4, 5. |
| 103 | Invalid filter: type | The value you supplied in the 'type' filter variable was not valid. Consult the valid types list. |
| 202 | Unable to generate demographic data for this postcode | This error should not occur. It is possible it could occur on special-case postcodes, or near national borders. Contact us or try a different postcode. |
| 401 | Value provided not recognised or out of range (1 - 10000000) | Stamp duty can only be calculated for prices of £1 to £10,000,000. Enter an integer in this range. |
| 402 | Country provided not recognised | The value you supplied in the 'country' variable was not valid. Consult the countries list or remove the country value to use 'england' as default. |
| 403 | A transaction cannot be both for a first-time buyer and an additional property | You entered 1 for both addtional rate stamp duty and first-time property. It is not possible for a transaction to be made both a first-time buyer and as an additional property. |
| 501 | Unable to identify council | We couldn't figure out the council from the valid postcode provided. This should not happen - please contact us us and let us know the postcode, and we will fix this. |
| 601 | No planning coverage here | There is no central national database of planning applications. Our planning database currently covers 205 out of 430 planning authorities in the UK. We hope to increase this over time. |
| 602 | Invalid input: decision_rating | Valid values for decision_rating are 'positive', 'negative' or 'neutral' |
| 603 | Invalid input: max_age_decision | The valid input for max_age_decision is an integer, minimum 1, maximum 365. |
| 604 | No planning applications matching filter | Planning applications were found in this area, but none that matched your filters. |
| 701 | Missing input: field_name | The named field is missing. All fields are required for valuations. |
| 702 | Invalid input: field_name | The named field is invalid. Consult the API documentation and accepted valuation options list and correct your inputs. |
| 801 | Title not found | Unable to find a title number matching the title number you provided. |
| 901 | Invalid filter: class | The value you supplied in the 'class' filter variable was not valid. Valid values are 'old_stock' or 'new_build'. |
| 902 | Invalid filter: tenure | The value you supplied in the 'tenure' filter variable was not valid. Valid values are 'freehold' or 'leasehold'. |
| 903 | Invalid filter: type | The value you supplied in the 'type' filter variable was not valid. Consult the valid types list. |
| 1001 | Not a Greater London postcode | The PTAL method is only available for Greater London postcodes, since it is a Transport for London metric. |
| 1101 | Missing input: list | You did not provide a property list. This is required. Consult the property lists list. |
| 1102 | Invalid input: list | The 'list' provided does not match one of our lists. Consult the property lists list. |
| 1103 | Region provided not recognised | The value you supplied in the 'region' variable was not valid. Consult the regions list. |
