Changes to Get a Geofence

Changed in 12 of the 15 revisions of this API.●9○18

1. Jul 31, 20257ee76f0ff679●3○3
2. Jul 31, 2025a800b73f11c1●3○3
3. Jul 30, 2025b79d96775b13●3○3
4. Jul 28, 2025535d42dd7dd1○1
5. Jul 28, 202521da6b936d5d○1
6. Jul 25, 2025e180c9037821○1
7. Jul 25, 2025193268acc413○1
8. Jul 25, 20255031a4562285○1
9. Jul 25, 2025b30bebc1373e○1
10. Jul 25, 2025f8f8fd74196c○1
11. Jul 25, 2025829b0241cf91○1
12. Jul 25, 202574d91edbe167○1

What changed

• Jul 31, 20257ee76f0ff679●3○3See the full diff
  • ●

    added the new circle enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new isochrone enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new polygon enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ○

    removed the circle enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the isochrone enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the polygon enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Jul 31, 2025a800b73f11c1●3○3See the full diff
  • ●

    added the new circle enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new isochrone enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new polygon enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ○

    removed the circle enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the isochrone enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the polygon enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

• Jul 30, 2025b79d96775b13●3○3See the full diff
  • ●

    added the new circle enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new isochrone enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new polygon enum value to the data/geofence/type response property for the response status 200

    response-property-enum-value-added

  • ○

    removed the circle enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the isochrone enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

  • ○

    removed the polygon enum value from the data/geofence/type response property for the response status 200

    response-property-enum-value-removed

• Jul 28, 2025535d42dd7dd1○1See the full diff
  • ○

    api operation id {id}-GET-ZF1nb-sq removed and replaced with {id}-GET-U5jn3sgB

    api-operation-id-removed

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Jul 28, 202521da6b936d5d○1See the full diff
  • ○

    api operation id {id}-GET-xAhG1jnc removed and replaced with {id}-GET-ZF1nb-sq

    api-operation-id-removed

  This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Jul 25, 2025e180c9037821○1See the full diff
  • ○

    api operation id {id}-GET-0Hl9veaC removed and replaced with {id}-GET-xAhG1jnc

    api-operation-id-removed

• Jul 25, 2025193268acc413○1See the full diff
  • ○

    api operation id {id}-GET-oF8VGpCb removed and replaced with {id}-GET-0Hl9veaC

    api-operation-id-removed

• Jul 25, 20255031a4562285○1See the full diff
  • ○

    api operation id {id}-GET-6ZLDkAIi removed and replaced with {id}-GET-oF8VGpCb

    api-operation-id-removed

• Jul 25, 2025b30bebc1373e○1See the full diff
  • ○

    api operation id {id}-GET-Pj1FaVul removed and replaced with {id}-GET-6ZLDkAIi

    api-operation-id-removed

• Jul 25, 2025f8f8fd74196c○1See the full diff
  • ○

    api operation id {id}-GET-V-70uMZQ removed and replaced with {id}-GET-Pj1FaVul

    api-operation-id-removed

  This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Jul 25, 2025829b0241cf91○1See the full diff
  • ○

    api operation id {id}-GET-JebtxMxZ removed and replaced with {id}-GET-V-70uMZQ

    api-operation-id-removed

• Jul 25, 202574d91edbe167○1See the full diff
  • ○

    api operation id {id}-GET-Wsbq0paH removed and replaced with {id}-GET-JebtxMxZ

    api-operation-id-removed