Doesn't seem to like many 'W' postcodes

[pafirmin]

Hi there. This may be a broader issue than stated here, but I have noticed that certain West London postcodes are not recognised by the API and a 400 error is returned along with a 'no postcode match can be found' message. A few examples are W1, W2, W3 and W7.

Example request:
curl -X GET https://api.carbonintensity.org.uk/regional/postcode/w7

Response:

    "error": {
        "code": "400 Bad Request",
        "message": "No postcode match can be found."
    }
}

[doig007]

Hi, I can't be any real help, but just on your first example there is no W1 postcode anymore.

W1A etc. seem to return matches:
https://api.carbonintensity.org.uk/regional/postcode/w1a

Nevertheless I concur that W2 etc. don't return a match which is very odd!

[mijiturka]

From my testing so far it seems like results granularity is at the region level, but some postcodes in London are in region 12 ("South England") and some are in 13 ("London") . The same is true for Glasgow for example (it is usually in South Scotland, but has one postcode in North Scotland). If anyone else is looking at this or you still are, you may be better off just using region-wide endpoints and selecting the regions from https://carbon-intensity.github.io/api-definitions/?python#region-list after some experimentation with the return values of postcode-specific endpoints.