Japan Address Parse

Choose this endpoint when you need only structural parsing of a Japanese address into its hierarchical components (prefecture, city, ward, town, chome, ban, go) without needing geocoordinates or postal-code validation output. It is the right choice for data normalization pipelines, CRM imports, or form processing where you want machine-readable address fields. Use the sibling Japan Address Geocode endpoint if you also need latitude/longitude, or Japan Address Validate if you need a quality/deliverability decision.

• Address string is empty or exceeds 500 characters — validation error returned
• Postal code format doesn't match pattern (###-####) — rejected with format error
• Address is too ambiguous to resolve to a unique town even with postal code evidence — ambiguity flag set in response
• Non-Japanese or romanized address input may result in failed or partial parsing
• Strict parser profile rejects addresses with irregular formatting that standard mode would accept
• Network or service unavailability returns HTTP 5xx error