Dear colleague, I hope the answer is helpful to you.
✅ 1. Customer provides x,y address coordinates: What TMF API to use to validate the address?
Yes, TMF673 - Geographic Address Management API is the correct API.
It allows you to validate, normalize, and verify postal addresses, including those that already include geographic coordinates (X, Y or lat/lon).
It also supports searching for existing addresses by coordinates or by text.
🔧 Example usage:
GET /geographicAddress?geographicLocation.latitude=...&geographicLocation.longitude=...
---
✅ 2. If the customer does not have x,y address coordinates, is there any API to obtain them?
TMF673 also covers this use case.
When the customer provides a textual address (e.g., street, number, city), you can use TMF673 to:
Validate if the address exists.
Get its normalized format.
Obtain its geographic coordinates (lat/lon) if available in the system.
🔧 Example usage:
GET /geographicAddress?streetNr=123&streetName=Main St&city=Buenos Aires
---
✅ 3. After address validation, determine what technologies (geographical coverage) are available at that address. What API should I use?
This use case corresponds to:
TMF645 - Service Qualification API
TMF645 is used to determine whether a service or technology (e.g., fiber, 5G, copper) is available at a given location (address or coordinates).
🔧 Typical usage:
POST /serviceQualification
{
"address": {
"id": "validAddressId" // Can come from TMF673
},
"serviceSpecification": {
"id": "fiber-access" // Or the service type you want to check
}
}
The response will include the services available at that address, along with technology type, speed, coverage, etc.
---
🧩 Typical API flow:
1. Customer provides address
→ Use TMF673 to validate and get coordinates.
2. With valid coordinates or addressId
→ Use TMF645 to check which services are available at that location.
------------------------------
Matias Ridelnik
TO BE VERIFIED
------------------------------