Amazon SNS: How to get EndpointArn by token(registrationId) using amazon .net sdk?

Barbaros Alp picture Barbaros Alp · Mar 19, 2014 · Viewed 11.7k times · Source

I am trying to get EndpointArn by registration id using aws .net sdk. But i couldn't find a nice way to do it.

My first attempt was running CreatePlatformEndpointRequest with the same registrationId, which is registered to SNS Application before, sent by the client(android). With this way, aws api gives you the EndpointArn for this registration id.

Amazon: The CreatePlatformEndpoint action is idempotent, so if the requester already owns an endpoint with the same device token and attributes, that endpoint's ARN is returned without creating a new endpoint.

But if you stored something to CustomUserData before you need to send the same user data to get endpoint arn for this registration id, otherwise you get an exception like below.

Invalid parameter: Token Reason: Endpoint {My Endpoint ARN} already exists with the same Token, but different attributes.

I think i am going to use CreatePlatformEndpoint() without user data and when i need Endpoint Arn for a registrationId i will run CreatePlatFormEndpoint only with this registration id.

Is there another way to get EndpointArn by token better than the solution above ?

Thank you.

Answer

GameSalutes picture GameSalutes · Sep 20, 2015

What we did is store the endpoint ARN returned from CreatePlatformEndpoint in our application database. If we already have an endpoint ARN association for a given device registration id, we then call

getEndpointAttributes passing in the endpoint arn from our database. If a result is returned, we then check if the endpoint is marked enabled and if not then call setEndpointAttributes and set key "Enabled" to "true".

Unfortunately it doesn't look like Amazaon API offers a "findBy" method to look up by "CustomUserData" or "Token" and only has "list" methods that list all the existing endpoints which for most applications will not suffice if there are potentially thousands or millions of entries. It is almost as if API was written only to satisfy the Amazon Console UI use cases.

Also, see Amazon docs for example API requests and responses

http://docs.aws.amazon.com/sns/latest/api/API_GetEndpointAttributes.html http://docs.aws.amazon.com/sns/latest/api/API_SetEndpointAttributes.html