C2DM Register API still supported by Google ?

[senthil5053]

In the source code, I see that c2dm register api url (https://android.clients.google.com/c2dm/register3) is being used in src/gcm/index.js. I know Google shut down C2DM long back in 2015. Can anybody share me with the details on how this is still supported by Google ? Will Google continue to support this in coming years ?

[PedroKantar]

I think behind the scenes, Google may keep using some "c2dm" based URLs, notably for the registration part..

[senthil5053]

Thanks @PedroKantar. I understand that Google is using it internally. In my project, we are planning to use push-receiver module for the Node.js process to receive the push notification. My concern is that any change/update in C2DM APIs might affect this module and eventually my application feature. We cannot check this with Google support desk as they deprecated the public use and only using it for internal purposes.

[PedroKantar]

We are using the push-receiver module since it was created, with the same concerns you have and so far it is still working perfectly..

[senthil5053]

Thanks @PedroKantar. Hope it continues to work :)

[wtesler]

I believe it has stopped working. Calls to the C2DM endpoint return 503 now.

[BRUHItsABunny]

As far as I can tell, both Chromium based browsers and Android itself still use /c2dm/register3 up to this day successfully
(I actually just implemented this over at: https://github.com/BRUHItsABunny/go-android-firebase)

Funny fact though, IOS checkin uses another endpoint device-provisioning.googleapis.com/checkin
Full request:

:method: POST
:scheme: https
:path: /checkin
:authority: device-provisioning.googleapis.com
accept: */*
content-type: application/json
accept-encoding: gzip, deflate, br
user-agent: YouTube/17.05.2 CFNetwork/1220.1 Darwin/20.3.0
content-length: 253
accept-language: en-us

{"locale":"en_US","digest":"","checkin":{"iosbuild":{"model":"iPhone9,4","os_version":"IOS_14.4.2"},"last_checkin_msec":0,"user_number":0,"type":2},"time_zone":"America\/Chicago","user_serial_number":0,"id":0,"version":2,"security_token":0,"fragment":0}

Where it then gets and android_id and security_token in the response (also JSON)

And then actually registers over at fcmtoken.googleapis.com/register

jan, 2023:
I finally got around to make a working proof of concept for receiving android app push notifications, c2dm still works

[piyushgarg]

That's great, a more easy way would be to use

POST /c2dm/register3 HTTP/1.1
Host: android.clients.google.com
authorization: AidLogin ANDROID_ID:SECURITY_TOKEN
content-type: application/x-www-form-urlencoded

app=com.chrome.linux&X-subtype=com.google.chrome.sharing.fcm&device=ANDROID_ID&sender=SENDER_ID

similarly only two calls like this

checkin
c2dm register3
mtalk socket