Recorded Future Identity API

https://docs.recordedfuture.com/reference/identity-dump-metadata

Admin

Recorded Future Identity API enables searching for metadata about data breaches and credential...

Tokens:568

Snippets:5

Trust Score:9.7

Update:5 months ago

Show doc for...

Tokens:

Raw

### Servers

Source: https://docs.recordedfuture.com/reference/identity-dump-metadata

The Recorded Future API is available through the following production server.

```APIDOC
## Servers

### Recorded Future Production Server

- **URL**: https://api.recordedfuture.com
- **Description**: Recorded Future Production Server
```

--------------------------------

### Dump Metadata Search

Source: https://docs.recordedfuture.com/reference/identity-dump-metadata

Search metadata for data dumps and breach databases by name. This endpoint requires authentication via RecordedFutureOAuth2 or RecordedFutureApiKey.

```APIDOC
## POST /identity/metadata/dump/search

### Description
Search metadata for data dumps and breach databases by name.

### Method
POST

### Endpoint
/identity/metadata/dump/search

### Request Body
- **schema** (object) - Required - The request body must conform to the DumpMetadataSearchRequest schema.

### Responses
#### Success Response (200)
- **schema** (object) - The response will contain a MetadataDumpResponse object.

#### Error Responses
- **400** - Bad Request: The request was malformed or invalid.
- **401** - Unauthorized: Authentication credentials were not provided or were invalid.
- **403** - Forbidden: The authenticated user does not have permission to access this resource.
- **500** - Internal Server Error: An unexpected error occurred on the server.
```

--------------------------------

### Security Schemes

Source: https://docs.recordedfuture.com/reference/identity-dump-metadata

The Recorded Future API supports two security schemes: RecordedFutureOAuth2 and RecordedFutureApiKey.

```APIDOC
## Security Schemes

### RecordedFutureOAuth2

- **Type**: oauth2
- **Description**: JWT-based OAuth2 security scheme supporting RFC8725 for OAuth 2.0 Access Tokens.
- **Flows**:
  - **authorizationCode**:
    - **authorizationUrl**: https://id.recordedfuture.com/authorize
    - **tokenUrl**: https://id.recordedfuture.com/token
    - **refreshUrl**: https://id.recordedfuture.com/token
    - **scopes**: {}

### RecordedFutureApiKey

- **Type**: apiKey
- **In**: header
- **Name**: X-RFToken
```

Tokens:

Raw