> For the complete documentation index, see [llms.txt](https://help.radiantsecurity.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.radiantsecurity.ai/radiant-connectors/email-and-collaboration/mimecast-api-2.0.md).
# Mimecast API 2.0
In this guide, you'll configure the integration between Radiant and Mimecast. Adding this data connector gives your organization visibility into phishing links accessed from unmanaged devices. With this data, Radiant Security can detect users who clicked on malicious links from personal devices, enabling deeper investigations and uncovering the full scope of an incident.
At the end of this configuration, you will provide Radiant Security with these values:
* **Client ID**
* **Client Secret**
:bolt-lightning: Available actions
The following actions are available after you set up the Mimecast data connector. Keep in mind, additional permissions are required.
* Block Sender
* Block URLs
### Prerequisites
Admin access to Mimecast, with a Role that grants:
* [ ] Read and Edit API Application Permissions under the Service Menu
* [ ] Security Permissions setting must permit the Management of Application Roles
### Create the custom role
1. Log in to your [Mimecast console](https://login-us.mimecast.com/administration/app/) with an admin account.
2. In the menu, click **Account**, then select **Roles**.
3. Click **New Role,** set the **Name** and **Description** as **Radiant Security API 2.0**.
4. On **Security Permissions,** select **Cannot Manage Roles**.
5. On **Application Permissions**, leave the following settings enabled:
* Account Menu | Logs | Read
* Gateway Menu | Policies | All
* Gateway Menu | Managed Senders | All
* Services Menu | URL Protection | All
* Directories | Groups | All
* Monitoring Menu | URL Protection | All
* Directories Menu | Managed Senders | All *(in case it exists on the UI)*
6. Click **Save and Exit**.
### Configure the Mimecast API
1. Log in to your [Mimecast](https://login-us.mimecast.com/administration/app/) console with an admin account.
2. In the administration menu, click **Services,** then select **API and Platform Integrations.**
3. Under **Mimecast API 2.0,** click **Generate Keys.**
4. On **Application Details**, fill the form with the following values:
* **Application Name:** `Radiant Security API 2.0`
* **Category:** `Others`
* **Products:** Select the following entries:
* Email Security Cloud Gateway
* Policy Management
* Threat Management
* Audit Events
* Security Events
* User and Group Management
* **Application Role:** `Radiant Security API 2.0`
* **Description:** `Radiant Security API 2.0 Connector`
5. Click **Next.**
6. Fill in the following values:
* **Technical Point of Contact:** ``
* **Email:** ``
7. Click **Next.**
8. Confirm the values in the summary.
9. The wizard completes and displays a pop-up window including your **Client ID** and **Client Secret,** where you can copy and save the credentials for the API application.
10. Copy the application values for:
* **Client ID**
* **Client Secret**
{% hint style="warning" %}
**Important note:** Be sure to document and store the **Client ID** and **Client Secret** carefully, as they cannot be retrieved later. Also, remember to label which is which, as these will need to be provided to Radiant Security later.
{% endhint %}
### Add the data connector in Radiant Security
1. Log in to [Radiant Security](https://app.radiantsecurity.ai/).
2. From the navigation menu, select **Settings** > **Data Connector** and click **+ Add Connector**.
3. Search for and select the **Mimecast** option from the list and then click **Data Feeds.**
4. Under **Select your data feeds**, select the **URL Protection** click **Credentials.**
5. Under **Credential Name**, give the credential an identifiable name (e.g. `Mimecast Credentials`).
6. Under **Required** **Credentials**, add the **Client ID** and the **Client Secret Token** that you copied from the previous section.
7. Click **Add Connector** to save the changes.
### Add the action connector in Radiant Security
1. From the navigation menu, select **Settings** > **Action Connectors** and click **+ Add Connector** to create a new action connector.
2. Select the **Mimecast API 2.0** connector and click **Credentials**.
3. Select the credential for the data connector that you created previously from the drop-down menu.
4. Click **Add Connector** to save your changes.
### Verify ingestion
After Mimecast begins forwarding, confirm events are reaching Radiant.
1. In Radiant, navigate to [Log Management](https://app.radiantsecurity.ai/logs).
2. Filter by `rs_connectorType:"mimecast_url_protection_api_v2"`.
3. Confirm recent events appear.
{% hint style="info" %}
Allow several minutes for events to be parsed, indexed, and available for search.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.radiantsecurity.ai/radiant-connectors/email-and-collaboration/mimecast-api-2.0.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.