Radar API
userId body parameter removal on PUT /v1/geofences/*
Deprecated, no dateSubscribe to Radar APIShare
Radar deprecated the body parameter userId on PUT /v1/geofences/* without a shutdown date. Radar API notes that the geofence will generate events for all users if it is not set. After removal, requests relying on this parameter will fail.
Calls it hits
PUT /v1/geofences/*body parameter userId
What to use instead of these calls
Send userIds, providing a comma-separated string of user IDs, instead of userId.
In Radar API's words
If not set, the geofence will generate events for all users. Deprecated.
Facts
- API
- Radar API
api.radar.io - Kind
- Parameter removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Radar API's own pages
Questions
When does this change take effect?
Radar API deprecated PUT /v1/geofences/*, body parameter userId without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Radar API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.