iid.googleapis.com
GET /iid/info/* endpoint removal
Stops working
On September 29, 2027, the endpoint GET /iid/info/* will be decommissioned and calls to it will fail. This removal affects calls made to iid.googleapis.com under the InstanceId server APIs. After that day, requests to this endpoint will no longer work.
Calls it hits
GET /iid/info/*
What to use instead of these calls
To validate a token, call POST /v1/projects/{project}/messages:send on fcm.googleapis.com with validate_only set to true. To read a token's topics, switch to the FCM topic subscription API at /v1/projects/{project}/registrations/{registration}/topicSubscriptions.
In iid.googleapis.com's words
All the InstanceId server APIs and the device group feature are deprecated and will be decommissioned on September 29, 2027.
Facts
- API
- iid.googleapis.com
iid.googleapis.com - Kind
- Endpoint removal
- Announced
- September 1, 2026
- Takes effect
- September 29, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against iid.googleapis.com's own pages
Questions
When does this change take effect?
Calls to GET /iid/info/* on iid.googleapis.com stop working on September 29, 2027.
What happens to calls after September 29, 2027?
They fail from that day.
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.
More from iid.googleapis.com 4
-
POST /iid/v1:batchAddEndpoint removal Stops workingin 335 days -
POST /iid/v1:batchImportEndpoint removal Stops workingin 335 days -
POST /iid/v1:batchRemoveEndpoint removal Stops workingin 335 days -
/iid/v1/*Endpoint removal Stops workingin 335 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before September 29, 2027.