As we announced earlier last year, API BaaS end of life (EOL) will be June 30, 2019
What do I need to know?
The API BaaS end of life (EOL) will be June 30, 2019.
There is no grace period. API BaaS will be shut down on June 30th, 2019. To avoid any business disruption on your end, kindly make use of all the resources available and migrate off of API BaaS by EOL date.
To avoid any service disruption to your applications, you must export your data from API BaaS and migrate to an alternate database solution before June 30, 2019. If you are using API BaaS push notifications, we strongly recommend that you discontinue using API BaaS immediately as Android Push Notifications that relies on Google Cloud Messaging has reached its End of Life on April 11, 2019.
To access our migration tools to export your API BaaS data, Private Cloud Customers can download and install these by following the steps in our API BaaS EOL FAQs page.
Public Cloud Customers must log a service request in the Apigee Support Portal to request access to the Apigee API BaaS query customer migration tools.
Google Cloud Platform (GCP) offers a number of database solutions, including Cloud SQL, Cloud Firestore, Cloud Spanner, and Firebase Cloud Messaging, you may wish to consider based on your needs.
For more information about our migration tools, please visit the API BaaS EOL FAQs page.
Please share any comments or ask any questions in the Apigee Community, or contact Support.
Solution to Push Notification via cURL / Postman NPE
We Are Sunsetting Apigee API BaaS
Push notification patterns with BaaS
Live webcast on BaaS/Usergrid - Get to know more about Backend As A Service
API Response Data Personalization Using BaaS
Tutorial: API BaaS Push Notifications
Unable to access API BaaS Orgs/Apps in Portal ( Apigee Cloud )