iid.googleapis.com
Topic subscription on /iid/v1/{id}/rel/topics removal
Stops workingSubscribe to iid.googleapis.comShare
On September 29, 2027, endpoints matching /iid/v1/* will be decommissioned. After this date, calls to these Instance ID server APIs will fail. This change removes topic subscriptions and related features hosted on iid.googleapis.com.
Calls it hits
/iid/v1/*
What to use instead of these calls
Use the FCM topic subscription API instead by sending requests to POST /v1/projects/{project}/registrations/{registration}/topicSubscriptions on fcm.googleapis.com, or use a Firebase Admin SDK release that calls it.
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
- 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 /iid/v1/* 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
-
GET /iid/info/*Endpoint removal Stops workingin 327 days -
POST /iid/v1:batchAddEndpoint removal Stops workingin 327 days -
POST /iid/v1:batchImportEndpoint removal Stops workingin 327 days -
POST /iid/v1:batchRemoveEndpoint removal Stops workingin 327 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.