Addresses contain encoded HTML entities - change to json encoded html decoded entities

[stickfigure]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Fetching receipts, I have found several addresses that contain encoded HTML entities. This doesn't seem right? It also doesn't appear to be documented anywhere. It's caused at least one failed package delivery :-(

I've attached an example in the steps to reproduce.

Steps to reproduce

In production, GET https://api.etsy.com/v3/application/shops/19127945/receipts/2212670131

The JSON response contains:

"first_line":"13 O'Connell Street"

Expected behavior

I expect the first_line to be 13 O'Connell Street without HTML entity encoding.

Alternatively, I would expect this to be explicit in the docs somewhere. But I'd prefer straight unicode.

Additional context

No response