I am looking to have a Push Notification service handling both FCM and Apple Push Notifications. I am looking into Amazon SNS but I can't figure out from the docs whether they support Token-Based authentication for Apple Push Notifications Service.
Amazon SNS now supports APNS token-based authentication. https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-sns-token-authentication-api-mobile-notifications/
Amazon SNS currently does not support token based APNS. Take a look on Firebase, it should be able to handle both.
Amazon Pinpoint is capable of using .p8 files when sending messages over APNS.
Related
We are sending emails using AWS SES. I know how to configure notifications for bounces and complaints using SNS. Infact I have configured SNS to deliver those notifications using https endpoint.
I have a springboot rest service that I would like to receive those notifications in. Can anybody point to a sample springboot rest controller to receive and process these notifications? Any help will be greatly appreciated.
How can I integrate email inbox from company account to my application? Gems like mail_room or gmail can connect to one mailbox given that you specify them.
I'm thinking about a web hook like a notification api, but I can't figure out how it works.
How can I add a web hook for inbox emails in company's gmail account? When a message is received in user#company.com or support#company.com I need to have a notification sent.
Check the Push Notifications for Gmail API.
1.Initial Cloud Pub/Sub Setup
The Gmail API uses the Cloud Pub/Sub API to deliver push
notifications. This allows notification via a variety of methods
including webhooks and polling on a single subscription endpoint.
Prerequisites
In order to complete the rest of this setup, make sure you fulfill the
Cloud Pub/Sub Prerequisites and then set up a Cloud Pub/Sub client.
Create a topic
Using your Cloud Pub/Sub client, create the topic that the Gmail API
should send notifications to. The topic name can be any name you
choose under your project (i.e. matching projects/myproject/topics/*,
where myproject is the Project ID listed for your project in the
Google Developers Console).
We recommend that you use a single topic for all Gmail API push
notifications for your application, due to Cloud Pub/Sub limits on the
number of topics.
Create a subscription
Follow the Cloud Pub/Sub Subscriber Guide to set up a subscription to
the topic that you created. Configure the subscription type to be
either a webhook push (i.e. HTTP POST callback) or pull (i.e.
initiated by your app). This is how your application will receive
notifications for updates.
more on the guide for additional info.
The only information I found is that you can view those events through ceilometer or RabbitMQ. Would be nice if I can get those events directly through APIs.
Each of the openstack services have 'exchanges' and 'topics' in rabbitmq
you can use Rabbitmq to connect to these exchanges and topics to get notifications via messages.
Unfortunately, currently there is no way to get notifications from individual OpenStack services.
Recently, I want to change my codes of pushing notifications to apple from basing on old binary API to new http2 API. The question is that should I use a different certificate for this http2 API when I connect to apple ? Because when I send a notification to apple with a valid token(the token is valid when I send notifications with old API) using http2 API, it returns "BadDeviceToken". So I'm wondering whether the token is really bad or the certificate that I use is not qualified .
We were also trying to break our heads with such an issue where we were trying to send push to production device tokens using the HTTP/2 API but were getting {"reason":"BadDeviceToken"} as the response and it was a clear mistake from our side, we were using the same code that we were using for test push notifications on dev environment to send push notifications on production, which was sending push to
https://api.development.push.apple.com/3/device/
rather for production it should be
https://api.push.apple.com/3/device
Hope it helps somebody but one issue with the new API is the distribution SSL certificate works for both the sandbox and production, not the other way round so be careful.
You can still use your old certificate with the new HTTP/2 API.
The BadDeviceToken is most commonly because you are trying to push through their production gateway wth a development token or vice versa.
Tokens are only valid for either development or production, and this is determined by the provisioning profile of your app.
I'm making a real-time system with API in PHP Parse.com, since I already use for Android.
I need to receive notifications (PUSH), the same that are received on mobile versions.