Discrepancy between the USPS data attribute on the google API site and the data returned when we call the Google API

Discrepancy between the USPS data attribute on the google API site and the data returned when we call the Google API -On the Google API site, the response data is structured across different properties, whereas via our code, everything seems to be returned as part of a single field. -For the same input address — 8418 N Overland Ctt, Kansas City, MO 64154 — the site returns "CT" in the usps data address, but via the package, we receive "CTT" instead

Request - {"address":{"addressLines":["8418 N Overland Ctt, Kansas City, MO 64154"],"regionCode":"US"},"enableUspsCass":true} Response- "uspsData": { "standardizedAddress": { "firstAddressLine": "8418 N OVERLAND CTT, KANSAS CITY, MO 64154" }, "dpvFootnote": "A1", "carrierRoute": "R081", "cassProcessed": true }

1)On the Google API site, the response data is structured across different properties, whereas here you can see everything seems to be returned as part of a single field firstAddressLine.

Expectation:- "standardizedAddress": { "firstAddressLine": "18418 N OVERLAND CTT", "cityStateZipAddressLine": "KANSAS CITY", "city": "KANSAS CITY", "state": "MO", "zipCode": " 64154" },

2)For the same input address — 8418 N Overland Ctt, Kansas City, MO 64154 — the google API site returns "CT" in the usps data address, but here , we receive "CTT" instead