Service Update
| By | End of June, 2025 |
| Product(s) | Email Security Cloud Gateway (CG) |
| Who's affected | Email Security Cloud Gateway (CG), Administrators |
Overview
Mimecast is pleased to announce our intent to begin restricting access to API 1.0, at the end of June 2025.
What's changing
In November of 2024, we stated our intent to begin restricting access to API 1.0 in April 2025.
We are pushing back the first stage of our API 1.0 End of Life project to the end of June 2025, as a result of feedback from our partners and customers, that more time is needed, to move over to API 2.0.
Here's what to expect:
- Nothing will be changing in April 2025.
- At the end of June 2025, we plan to remove the API 1.0 tiles in our Cloud Gateway Mimecast Administration Console, preventing the creation of any new API 1.0 applications at that time. Any existing API 1.0 applications will continue to function normally, so long as the associated service account user, Access Key, and Secret key remain valid.
- Sometime after the ability to create API 1.0 applications has been removed, we plan to start expiring our any existing API 1.0 applications.
We will publish further details and timelines for this at a future date, and will ensure it is after a majority of integrations have already been migrated to API 2.0 versions.
Mimecast Managed Integrations
The following Mimecast-managed integrations still use API 1.0 today:
- Simply Migrate.
- Brand Exploit Protection.
- Engage.
- Incydr.
Some of these applications, such as Simply Migrate, will continue to use API 1.0, and will continue to function the same way as they do today with no changes required by our customers. Others will be updated before the ability to create API 1.0 apps is removed.
Partner Managed Integrations
Our partners were first informed of the need to update integrations in August 2025. Since then, we have been working with many of them to assist their journey from API 1.0 to API 2.0. If you have not seen an update from our partner or Mimecast about an API 2.0 version, keep an eye out for upcoming communications.
If an API 2.0 version of an integration exists today, customers should plan their migration to the new version, which will require a new set of API keys from Mimecast. API 2.0 keys can be obtained by following this guide.
Customer Bespoke Integrations
If you have built your own integration with Mimecast (e.g. scripts or using a tool that does not have an official integration with Mimecast), you should plan to update those integrations to make use of API 2.0 as soon as possible. We have a Migration Guide, to help understand the differences between API 1.0 and API 2.0.
Frequently Asked Questions
| Q: | I've Updated My Integrations to API 2.0 Versions. Now What? |
| A: | Once you have completed the migration of an integration to its API 2.0 version, you can delete the old API 1.0 application in the Mimecast Administration Console, under Services | API and Platform Integrations. In addition to monitoring API call activity , this will help us to know which API 1.0 applications are still in use. |
| Q: | Is the Mimecast Email Security Cloud Integrated Platform affected? |
| A: | Customers using Mimecast Email Security Cloud Integrated will not be impacted, as this platform has always used API 2.0. |
| Q: | What if I need more time? |
| A: | This update is to notify our customers of our intent to end-of-life API 1.0. We strongly encourage all users to begin upgrading their integrations to API 2.0. Our team will closely monitor the activity on API 1.0 and will make every effort to minimize disruptions as we transition to API 2.0. |
Comments
Please sign in to leave a comment.