---
title: Recorded Future Sandbox
slug: authentication-guides/recorded-future-sandbox
docTags: 
createdAt: 2026-04-28T11:03:18.970Z
---

# Introduction

This guide tells you how to authenticate the **Recorded Future Sandbox connector** in Swimlane using:

- **HTTP Bearer Token Authentication**
- **OAuth 2.0 Client Credentials**

You will generate an API token or OAuth client credentials in Recorded Future, collect the required identifiers, and configure the connector in Swimlane.

# Prerequisites

## Recorded Future Access Requirements

You must have Recorded Future permissions to:

- Access the Recorded Future platform
- Generate API tokens
- Create OAuth clients (if applicable)
- Access API services

## Required Credentials

During setup, you will collect:

- API Base URL
- API Token (Bearer Token)
- Client ID (OAuth)
- Client Secret (OAuth)
- Token URL (OAuth)

# Authentication Methods Overview

The Recorded Future Sandbox connector supports:

1. **HTTP Bearer Token Authentication**
2. **OAuth 2.0 Client Credentials**

# Recorded Future Setup

Take the following steps to generate an API Token (Bearer Authentication):

1. Log in to the **Recorded Future Platform**.
2. Click your **profile icon** (top-right corner).
3. Select **Settings**.
4. Navigate to **API Access**.
5. Click **Generate New Token**.
6. Enter a name for the token.
7. Click **Generate**.
8. Copy and securely store the token.

This token will not be shown again. Store it securely.

Take the following steps to configure OAuth Client Credentials (if applicable):

1. Log in to the **Recorded Future Platform**.
2. Navigate to **API / Integrations settings**.
3. Create a new **OAuth application/client**.
4. Select **Client Credentials** as the grant type.
5. Assign required permissions/scopes.
6. Save the application.
7. Copy:
   - Client ID
   - Client Secret
   - Token URL

# Connector Configuration in Swimlane

1. Log in to **Turbine**.
2. From the left-hand navigation pane, click **ORCHESTRATION → Assets**.
3. Click the **plus icon**.
4. Select **Recorded Future Sandbox** from the Asset type list.

## Configuration – HTTP Bearer Authentication

| **Field**   | **Description**                      | **Required** |
| ----------- | ------------------------------------ | ------------ |
| url         | Recorded Future Sandbox API base URL | Yes          |
| token       | API Token (Bearer Token)             | Yes          |
| verify\_ssl | Enable or disable SSL verification   | No           |
| http\_proxy | Proxy configuration                  | No           |

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/AvGautDk6wBxNVcHYqn1c_.blob)

![]()

## Configuration – OAuth 2.0 Client Credentials

| **Field**      | **Description**                      | **Required** |
| -------------- | ------------------------------------ | ------------ |
| url            | Recorded Future Sandbox API base URL | Yes          |
| token\_url     | OAuth token endpoint                 | Yes          |
| client\_id     | OAuth client ID                      | Yes          |
| client\_secret | OAuth client secret                  | Yes          |
| verify\_ssl    | Enable or disable SSL verification   | No           |
| http\_proxy    | Proxy configuration                  | No           |

![](https://api.archbee.com/api/optimize/n8uUzk0MM4uC57-zlHNtY/ENGkGchwmjaxFRPipACnD_.blob)

![]()

# Troubleshooting

Authentication failures may occur due to:

- Invalid API token or OAuth credentials
- Incorrect API base URL
- Missing permissions or scopes
- Expired or revoked token

**Fix:**

- Regenerate API token if needed
- Verify credentials in Recorded Future
- Ensure correct API endpoint
- Confirm permissions and access level

You have successfully authenticated the **Recorded Future Sandbox connector** in Swimlane.

**Sources**

- Recorded Future API Documentation: [https://api.recordedfuture.com/](https://api.recordedfuture.com/)
- Recorded Future Support: [https://support.recordedfuture.com/](https://api.recordedfuture.com/)