Question

You are migrating from PTV xServer (XRoute, XLocate, XMap) to PTV Developer APIs and currently use a callerContext block like:

"callerContext": {
  "properties": [
    { "key": "CoordFormat", "value": "OG_GEODECIMAL" },
    { "key": "ResponseGeometry", "value": "PLAIN" },
    { "key": "Profile", "value": "mg-truck-40t" }
  ]
}

You want to understand how these parameters should be handled in the new APIs.

Answer

The callerContext concept no longer exists in PTV Developer APIs.
All parameters must now be defined explicitly in the request body or query parameters.

Parameter Mapping

➤ CoordFormat

• No longer required
• Coordinates are handled implicitly using WGS84 (latitude/longitude)

 Reference: https://developer.myptv.com/en/documentation/map-matching-api/concepts/position-matching

➤ ResponseGeometry

• Controlled via request options (e.g. geometry format such as polyline)

References: 

• https://developer.myptv.com/en/documentation/data-api/data-api-reference
• https://developer.myptv.com/en/documentation/data-api/concepts/custom-road-attributes

➤ Profile

• Directly specified using the profile parameter in the request

Reference: https://developer.myptv.com/en/documentation/data-api/concepts/profiles

Additions hints

• Migration requires explicit parameter definition → no implicit behavior via context.
• Always review API-specific request schemas (Routing, Geocoding, Maps differ).
• This change improves clarity and maintainability of requests.

Related articles

PTV Developer: Migrating from xServer to PTV Developer
PTV Developer API Documentation