Hey, I’m using the following endpoint:
domain/api/v1/deals?limit=500&start=0
At one of our customer sites, the response contains some unusual geocoded properties, as shown in this example:
{
"45ba940d053f8329a24ba8c70c5eec062c9d06ae": "Dog",
"985daa00e5145dc1792ea720da3f4a57b0955246": "sensitive info",
"985daa00e5145dc1792ea720da3f4a57b0955246_admin_area_level_1": "England",
"985daa00e5145dc1792ea720da3f4a57b0955246_admin_area_level_2": "sensitive info",
"985daa00e5145dc1792ea720da3f4a57b0955246_country": "UK",
"985daa00e5145dc1792ea720da3f4a57b0955246_formatted_address": "sensitive info",
"985daa00e5145dc1792ea720da3f4a57b0955246_locality": "sensitive info",
"985daa00e5145dc1792ea720da3f4a57b0955246_postal_code": "sensitive info",
"985daa00e5145dc1792ea720da3f4a57b0955246_route": "Clare Close",
"985daa00e5145dc1792ea720da3f4a57b0955246_street_number": "25",
"985daa00e5145dc1792ea720da3f4a57b0955246_sublocality": "",
"985daa00e5145dc1792ea720da3f4a57b0955246_subpremise": "",
"7590423c279d13fbeb01cdf9a1f4816113713400": "sensitive info",
"7590423c279d13fbeb01cdf9a1f4816113713400_admin_area_level_1": "England",
"7590423c279d13fbeb01cdf9a1f4816113713400_admin_area_level_2": "sensitive info",
"7590423c279d13fbeb01cdf9a1f4816113713400_country": "UK",
"7590423c279d13fbeb01cdf9a1f4816113713400_formatted_address": "sensitive info",
"7590423c279d13fbeb01cdf9a1f4816113713400_locality": "",
"7590423c279d13fbeb01cdf9a1f4816113713400_postal_code": "sensitive info",
"7590423c279d13fbeb01cdf9a1f4816113713400_route": "sensitive info",
"7590423c279d13fbeb01cdf9a1f4816113713400_street_number": "6",
"7590423c279d13fbeb01cdf9a1f4816113713400_sublocality": "",
"7590423c279d13fbeb01cdf9a1f4816113713400_subpremise": "",
"active": true,
"activities_count": 0,
"add_time": "2024-09-26"
}
The response includes encoded information (e.g., address details, administrative areas) for some properties. How can I decode these keys into a more readable text format?