Service Update
| Availability | January 29th, 2026 |
| Product(s) | Email Security Cloud Gateway (CG) |
| Who's affected | Email Security Cloud Gateway, Administrators |
Overview
Mimecast is pleased to announce enhancements to the API 2.0 Application Management, which is transitioning from the API and Platform Integrations page to the new Integrations Hub. This update brings API 2.0 applications into a unified, modern platform for managing all API-based integrations. API 2.0 is Mimecast's current-generation API platform, offering advanced capabilities, a modern architecture, and support for branded partner integrations. API 1.0 remains available as a legacy version for customers who continue to use older integrations.
What's changing
-
New API 2.0 Applications:
- A dedicated API 2.0 tile will now appear on the Integrations Hub page. All new API 2.0 applications should be created using this tile moving forward. While the API 2.0 tile remains visible on the legacy API and Platform Integrations page, the option to create new apps will redirect you to the Integrations Hub.
-
Existing Applications:
- Applications that were previously created via the API and Platform Integrations page will continue to be managed there, under the API 2.0 Applications tab. You can still perform all standard management tasks, such as role changes, product modifications, and API key rotation to existing apps without any procedural changes.
Some applications on this page may have names appended with "- IH" which are applications created on the Integrations Hub. These should not be deleted or modified on the API and Platform Integrations page.
What's next?
- In a later phase, existing API 2.0 applications will be migrated to the API 2.0 tile within the Integrations Hub. Once all API 2.0 applications have been migrated, we will begin removing API 2.0 references from the legacy API and Platform Integrations page. This will complete the migration of API 2.0 to the Integrations Hub.
- The migration will happen in several phases, starting with this first phase.
- When this migration is complete, only API 1.0 applications and platform integrations will be managed through the API and Platform Integrations page.
Why We're Making This Change
By moving generic API 2.0 application management here, we're:
- Streamlining Experience: Further shifting the default place to manage API-based applications to the Integrations Hub.
- Modernizing the Interface: Updated design standards and improved usability.
- Future-proofing: Built on our current platform architecture.
- Creating Consistency: Same management experience whether you use branded or custom integrations.
Recommended actions
- No action is required, and existing API 2.0 applications will continue to function normally after the migration.
Comments
Please sign in to leave a comment.