### EDGAR API GET Request Example

Source: https://api.edgarfiling.sec.gov/docs/index.html

A sample HTTP GET request to retrieve the status of the EDGAR system. It includes the necessary Authorization header with a bearer token and specifies the desired content type as JSON.

```HTTP
GET /status HTTP/1.1
Authorization: bearer eyJjaWsiOiIwMDAxMzE2MDAzIiwia2lkIjoiOThiOTg0ZTk1NTk5Y2Y3YWNlMDRjYzk1N2U2OWE1MDIiLCJhbGciOiJFUzUxMiIsImV4cGlyZXNBdCI6IjIwMjUtMDctMjVUMDM6MDA6MDBaIiwidHlwIjoiSldUIn0.eyJKV1QiOiJFTkNSWVBURUQgVkFMVUUifQ.AeF5hGsaJnQQEZUk-OBfVUzf-nuu5zJSn9MSK5Y7eSlj0RiJ_7jKKUA4J11I61tfe5TOBxrnhwqMiWuzdl3gtJnyAIqBeF-G5_A93EUbI3ttW_pUXQupKsdmW1lDnHyS3ciGbCfkeXz28VWSufMLORqzq1wi-EzgpbT9cFrZR7YGMOj9
Accept: application/json
```

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

### EDGAR API Success Response Example

Source: https://api.edgarfiling.sec.gov/docs/index.html

An example of a successful response from the EDGAR API. It includes a 200 OK status code, JSON content type, and a response body containing tracking information, a locator, a message, and the system's condition.

```HTTP
200 OK
Content-Type: application/json

{
  "tracking": "1bac520cf898f4625cf9d5c48af2c1c3",
  "locator": "df1c34",
  "message": "EDGAR is operating normally. All submissions will receive today’s filing date.",
  "condition": "ACCEPTING"
}
```

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

### Constructing an EDGAR API Request URL

Source: https://api.edgarfiling.sec.gov/docs/index.html

Example of how to combine the base URL with a resource path to form a valid endpoint URL for the EDGAR Operational Status API.

```text
https://api.edgarfiling.sec.gov/status
```

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

### GET /status

Source: https://api.edgarfiling.sec.gov/docs/index.html

Retrieve the current operational status of the EDGAR system.

```APIDOC
## GET /status

### Description
Returns the current operational status of the EDGAR system to determine if services are available for submissions.

### Method
GET

### Endpoint
/status

### Response
#### Success Response (200)
- **status** (string) - The current system state (e.g., 'operational', 'maintenance')

#### Response Example
{
  "status": "operational"
}
```

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

### Example Encoded JWT Header

Source: https://api.edgarfiling.sec.gov/docs/index.html

This is the base64 encoded header stanza from a sample Filer API Token, representing the initial segment of the JWT.

```text
ewogICJjaWsiOiAiMDAwMDAwMDAwMCIsCiAgImtpZCI6ICI3NWM4ZDM3OS0yZDgyLTQxNWUtYTNjNS03NTAxNjk5ZTMxMDEiLAogICJhbGciOiAiRUNESC1FUyIsCiAgImV4cGlyZXNBdCI6ICIyMDI1LTA3LTI1VDAzOjAwOjAwWiIKfQ==
```

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

### EDGAR API Authentication Error Response Example

Source: https://api.edgarfiling.sec.gov/docs/index.html

This JSON structure represents an error response from the EDGAR API when authentication fails due to invalid tokens. It includes tracking information, a locator, and a list of messages detailing the specific authentication issues encountered.

```json
{
  "tracking": "38ab654e20162523396d447d22ae8887",
  "locator": "4n05cc",
  "messages": [
    {
      "type": "ERROR",
      "content": "Forbidden"
    },
    {
      "type": "ERROR",
      "content": "token 2 is not in the format expected by this application, check the contents of the token"
    }
  ]
}
```

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

### Get EDGAR System Status

Source: https://api.edgarfiling.sec.gov/docs/index.html

This endpoint retrieves the current operational status of the EDGAR system. It requires an Authorization header with a bearer token.

```APIDOC
## GET /status

### Description
Retrieves the current operational status of the EDGAR system.

### Method
GET

### Endpoint
/status

### Request Headers
- **Authorization** (string) - Required - Bearer token for authentication.
- **Accept** (string) - Optional - Specifies the desired response format, e.g., `application/json`.

### Request Example
```http
GET /status HTTP/1.1
Authorization: bearer eyJjaWsiOiIwMDAxMzE2MDAzIiwia2lkIjoiOThiOTg0ZTk1NTk5Y2Y3YWNlMDRjYzk1N2U2OWE1MDIiLCJhbGciOiJFUzUxMiIsImV4cGlyZXNBdCI6IjIwMjUtMDctMjVUMDM6MDA6MDBaIiwidHlwIjoiSldUIn0.eyJKV1QiOiJFTkNSWVBURUQgVkFMVUUifQ.AeF5hGsaJnQQEZUk-OBfVUzf-nuu5zJSn9MSK5Y7eSlj0RiJ_7jKKUA4J11I61tfe5TOBxrnhwqMiWuzdl3gtJnyAIqBeF-G5_A93EUbI3ttW_pUXQupKsdmW1lDnHyS3ciGbCfkeXz28VWSufMLORqzq1wi-EzgpbT9cFrZR7YGMOj9
Accept: application/json
```

### Response
#### Success Response (200)
- **tracking** (string) - A unique identifier for the request.
- **locator** (string) - An identifier to help locate the record in the EDGAR system.
- **message** (string) - Supplemental information about the response.
- **condition** (string) - The operational status of the EDGAR system.

#### Response Example
```json
{
  "tracking": "1bac520cf898f4625cf9d5c48af2c1c3",
  "locator": "df1c34",
  "message": "EDGAR is operating normally. All submissions will receive today’s filing date.",
  "condition": "ACCEPTING"
}
```
```

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

### GET /submission/{accessionNumber}/status

Source: https://api.edgarfiling.sec.gov/docs/index.html

Retrieves the processing status of a specific filing using its accession number.

```APIDOC
## GET /submission/{accessionNumber}/status

### Description
Retrieves the status of a submission. Detailed information is available only when the 'final' field is true.

### Method
GET

### Endpoint
/submission/{accessionNumber}/status

### Parameters
#### Path Parameters
- **accessionNumber** (string) - Required - The unique accession number of the filing.

### Response
#### Success Response (200)
- **status** (string) - The current status of the filing.
- **final** (boolean) - Indicates if processing is complete.

#### Response Example
{
  "accessionNumber": "0001234567-23-000001",
  "status": "Accepted",
  "final": true
}
```

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

### EDGAR API Error Response Format

Source: https://api.edgarfiling.sec.gov/docs/index.html

Example of the JSON structure returned by the EDGAR API when an HTTP error status code (400-599) is encountered. It includes a tracking ID, a locator, and an array of error messages.

```json
{
  "tracking": "4c2a2872bb941f61b2d7e7615679c0b0",
  "locator": "91e0e3",
  "messages": [
    {"type": "ERROR", "content": "Forbidden"}
  ]
}
```

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

### Authentication Overview

Source: https://api.edgarfiling.sec.gov/docs/index.html

Details on how to construct the Authorization header for EDGAR API requests.

```APIDOC
## Authentication

### Description
All requests to the EDGAR API must be authenticated using the `Authorization` header with the `bearer` prefix.

### Header Format
- **Single Token**: `Authorization: bearer <token>`
- **Dual Tokens**: `Authorization: bearer <filer_token>,<user_token>`

### Security Schemes
- **Filer API Token**: Used for endpoints requiring only filer-level access.
- **Filer API Token and User API Token**: Used for endpoints requiring both filer and individual user authorization.

### Example Request
```http
GET /api/resource HTTP/1.1
Host: api.edgarfiling.sec.gov
Authorization: bearer filer123,user345
```
```

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

### Authentication Overview

Source: https://api.edgarfiling.sec.gov/docs/index.html

Details on how to use and interpret JWT Bearer tokens for EDGAR API access.

```APIDOC
## Authentication: Bearer Token

### Description
The EDGAR API requires HTTP Bearer authentication using JWT tokens. Tokens are issued by Filer Management and must be handled securely.

### Method
N/A (Header-based authentication)

### Parameters
#### Request Headers
- **Authorization** (string) - Required - "Bearer <JWT_TOKEN>"

### Token Structure
Tokens are JWTs in JOSE format. The header (first base64 stanza) contains:
- **cik** (string) - The CIK assigned to a Filer API Token.
- **kid** (string) - Key ID used for encryption.
- **alg** (string) - Encryption algorithm (e.g., ECDH-ES).
- **userId** (string) - Unique identifier for User API Tokens.
- **expiresAt** (string) - ISO 8601 timestamp for local expiration checks.

### Token Validity
- **Filer API Token**: Minimum 1 year validity.
- **User API Token**: Minimum 30 days validity.

### Response
#### Success Response (200)
- **Status**: Access granted to requested EDGAR resources.

#### Error Response (401)
- **Status**: Unauthorized - Token is missing, expired, or invalid.
```

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

### POST /submission/single/live

Source: https://api.edgarfiling.sec.gov/docs/index.html

Submits a single live filing to the EDGAR system.

```APIDOC
## POST /submission/single/live

### Description
Submits a single live filing to the EDGAR system. Requires Filer API Token and User API Token.

### Method
POST

### Endpoint
/submission/single/live

### Parameters
#### Request Headers
- **Filer-API-Token** (string) - Required - The Filer API Token.
- **User-API-Token** (string) - Required - The User API Token.
- **Expect** (string) - Optional - Use '100-continue' for bodies > 1MiB.

### Response
#### Success Response (202)
- **accessionNumber** (string) - The generated accession number for the filing.

#### Response Example
{
  "accessionNumber": "0001234567-23-000001"
}
```

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

### POST /submissions

Source: https://api.edgarfiling.sec.gov/docs/index.html

Submit a filing to the EDGAR system.

```APIDOC
## POST /submissions

### Description
Submit a filing to the EDGAR system. Supports both live and test submissions.

### Method
POST

### Endpoint
/submissions

### Request Body
- **filing_type** (string) - Required - The type of filing being submitted
- **content** (binary/xml) - Required - The filing document content

### Request Example
{
  "filing_type": "10-K",
  "content": "[binary_data]"
}

### Response
#### Success Response (200)
- **submission_id** (string) - Unique identifier for the submitted filing

#### Response Example
{
  "submission_id": "0001234567-23-000001"
}
```

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

### Filer Management API - Send Delegation Invitations

Source: https://api.edgarfiling.sec.gov/docs/index.html

Sends delegation invitations for a given CIK.

```APIDOC
## POST /fm/{cik}/delegations

### Description
Send delegation invitations for a given CIK.

### Method
POST

### Endpoint
/fm/{cik}/delegations

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
- **delegateCik** (string) - Required - The CIK of the delegate.
- **permission** (string) - Required - The permission being delegated.

### Response
#### Success Response (200)
- **message** (string) - Confirmation message indicating the delegation invitation was sent.

#### Response Example
```json
{
  "message": "Delegation invitation sent."
}
```
```

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

### Filer Management API - Create Custom CCC

Source: https://api.edgarfiling.sec.gov/docs/index.html

Creates a custom CCC for a given CIK.

```APIDOC
## PUT /fm/{cik}/ccc

### Description
Create a custom Company Classification Code (CCC) for a given CIK.

### Method
PUT

### Endpoint
/fm/{cik}/ccc

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
- **customCcc** (string) - Required - The custom CCC to be created.

### Response
#### Success Response (200)
- **message** (string) - Confirmation message indicating the CCC was created.

#### Response Example
```json
{
  "message": "Custom CCC created successfully."
}
```
```

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

### Filer Management API - Request Delegation Invitations

Source: https://api.edgarfiling.sec.gov/docs/index.html

Requests delegation invitations for a given CIK.

```APIDOC
## POST /fm/{cik}/delegationRequests

### Description
Request delegation invitations for a given CIK.

### Method
POST

### Endpoint
/fm/{cik}/delegationRequests

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
- **email** (string) - Required - The email address to send the invitation to.

### Response
#### Success Response (200)
- **message** (string) - Confirmation message indicating the delegation request was sent.

#### Response Example
```json
{
  "message": "Delegation invitation request sent."
}
```
```

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

### Filer Management API - View Delegations

Source: https://api.edgarfiling.sec.gov/docs/index.html

Retrieves a list of delegations for a given CIK.

```APIDOC
## GET /fm/{cik}/delegations

### Description
View delegations for a given CIK.

### Method
GET

### Endpoint
/fm/{cik}/delegations

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
None

### Response
#### Success Response (200)
- **delegations** (array) - A list of delegation objects.
  - **delegateCik** (string) - The CIK of the delegate.
  - **permission** (string) - The permission granted.
  - **status** (string) - The status of the delegation.

#### Response Example
```json
{
  "delegations": [
    {
      "delegateCik": "0000000001",
      "permission": "SubmitFilings",
      "status": "Active"
    }
  ]
}
```
```

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

### Filer Management API - Add Individuals

Source: https://api.edgarfiling.sec.gov/docs/index.html

Adds individuals associated with a filer's account.

```APIDOC
## POST /fm/{cik}/individuals

### Description
Add individuals associated with a filer's account.

### Method
POST

### Endpoint
/fm/{cik}/individuals

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
- **name** (string) - Required - The name of the individual.
- **role** (string) - Required - The role of the individual.

### Response
#### Success Response (200)
- **message** (string) - Confirmation message indicating the individual was added.

#### Response Example
```json
{
  "message": "Individual added successfully."
}
```
```

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

### Filer Management API - Filing Credentials Verification

Source: https://api.edgarfiling.sec.gov/docs/index.html

Verifies filing credentials for a given CIK.

```APIDOC
## GET /fm/{cik}/verify

### Description
Verify filing credentials for a given CIK.

### Method
GET

### Endpoint
/fm/{cik}/verify

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
None

### Response
#### Success Response (200)
- **verificationStatus** (string) - The status of the filing credentials verification.

#### Response Example
```json
{
  "verificationStatus": "Verified"
}
```
```

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

### Filer Management API - View Filer Account Information

Source: https://api.edgarfiling.sec.gov/docs/index.html

Retrieves filer account information using the CIK.

```APIDOC
## GET /fm/{cik}

### Description
View filer account information for a given CIK.

### Method
GET

### Endpoint
/fm/{cik}

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
None

### Response
#### Success Response (200)
- **accountInfo** (object) - Contains details about the filer's account.

#### Response Example
```json
{
  "accountInfo": {
    "cik": "0000000000",
    "name": "Example Filer Name",
    "status": "Active"
  }
}
```
```

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

### Common EDGAR API Response Codes

Source: https://api.edgarfiling.sec.gov/docs/index.html

This section outlines the standard HTTP status codes returned by the EDGAR APIs, along with their descriptions and specific use cases within the EDGAR system.

```APIDOC
## EDGAR API Response Codes

### Description
This table details the common HTTP status response codes used by the EDGAR APIs, explaining their meaning and typical usage scenarios.

### Method
N/A (Applies to all HTTP methods)

### Endpoint
N/A

### Parameters
N/A

### Response Codes

| Code | Status | Description |
|---|---|---|
| 200 | **OK** | The API resource was accessed successfully. Messages may be attached to the response for additional context. |
| 202 | **Accepted** | The API resource was accessed successfully. This status code is used by the submission API to indicate that the submission has been transmitted to EDGAR and that it has an Accession Number. In the HTTP standard this response is used to indicate that there is further processing that will be done on the resource after the response. |
| 204 | **No Content** | The API resource that was requested is empty. This can be used when a list of items is requested but no items were found to populate the list. A 204 response is empty and will include no JSON and cannot be parsed. |
| 400 | **Bad Request** | The API resource was not able to process the request because of an error with the request. The messages returned with this request will provide more insight into the nature of the error. |
| 401 | **Unauthorized** | The request made to the API resource was not able to be authorized. This usually means that invalid token material was provided with the "Authorization" header. This could mean a partial or corrupted token or a token that has expired. |
| 403 | **Forbidden** | The request made to the API has been authorized, meaning that the tokens presented contain enough information to identify the Filer and the User (if required), but that identifying information does not have the rights or permission to access the resource. There are several reasons this could happen. The most common is when making a submission and the Filer API Token and User API Token combination does not have delegated permissions for the CIK or Login CIK combination. A user that is locked in Filer Management will also cause a "Forbidden" response. Another scenario that produces "Forbidden" is requesting the status of a submission with a Filer API Token that does not match the CIK or Login CIK of the submission and does not have delegation to either. |
| 404 | **Not Found** | The requested API resource was not found. This may mean the URL path used is invalid or is no longer being used. |
| 405 | **Method Not Allowed** | Typically seen when using the wrong method to send data to an API resource. Each resource responds to either a single specific method or a set of methods. Using the wrong method, like PUT instead of POST, will cause this response. |
| 406 | **Not Acceptable** | Each API resource expects the client to accept a response in "application/json" format through the use of the "Accept" header. Any other value in the "Accept" header will cause the API resource to respond with the "Not Acceptable" response. |
| 411 | **Length Required** | When accessing the Submission API resources a "Content-Length" header is required if not using the "Transfer-Encoding" header with the last value "chunked". If not provided the API may respond with this status code. |
| 413 | **Content Too Large** | The EDGAR API will reject submissions that are larger than 850M. This value is independent of maximum filing sizes in EDGAR and is separately configurable. A submission successfully transmitted through an EDGAR API resource can still be suspended by EDGAR due to being too large. |
| 415 | **Unsupported Media Type** | Each API resource expects to provide a response in a supported media type. In general the preferred media type for requests and responses is "application/json" however some methods do support "application/xml" in both request and response. Notably the submission resources expect the request to be either "application/xml" or "application/octet-stream". The Filer Management resources are "application/json" only. This media type is specified by the client using the "Content-type" header. |
| 429 | **Too Many Requests** | In the event that an API resource is being requested too often a status code of 429 may be returned. This is a signal that either the service has become overloaded and cannot handle more requests or that the client is making too many requests in a given timeframe and is being asked to make requests less frequently. In the Developer Resources page there is more information on Fair Access and how various resources should be accessed. |
| 500 | **Internal Server Error** | When the EDGAR API resource that was requested encounters an error processing the request a status code of 500 will be returned. The help desk can be contacted in cases with persistent errors of this nature. |
| 503 | **Service Unavailable** | This method is returned by EDGAR API resources when they are unavailable such as when EDGAR is out of operating hours. |

```

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

### User Agent Requirement

Source: https://api.edgarfiling.sec.gov/docs/index.html

Information regarding the mandatory 'User-Agent' header for all requests to EDGAR API resources.

```APIDOC
### User Agent

It is expected that every request to an EDGAR API resource includes a "User-Agent" header that identifies the vendor and version of the software being used to contact EDGAR API resources. The content of this header will make it easier for integrators and SEC EDGAR staff to work together to identify issues accessing EDGAR resources.

Failure to provide this header may result in "NOTICE" level messages from the API or may result in a request returning a response code of 400 for failing to provide a valid user agent.
```

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

### Filer Management API - View Individuals

Source: https://api.edgarfiling.sec.gov/docs/index.html

Retrieves a list of individuals associated with a filer's account.

```APIDOC
## GET /fm/{cik}/individuals

### Description
View individuals associated with a filer's account.

### Method
GET

### Endpoint
/fm/{cik}/individuals

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
None

### Response
#### Success Response (200)
- **individuals** (array) - A list of individual objects.
  - **name** (string) - The name of the individual.
  - **role** (string) - The role of the individual.

#### Response Example
```json
{
  "individuals": [
    {
      "name": "John Doe",
      "role": "Director"
    }
  ]
}
```
```

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

### EDGAR Operational Status API

Source: https://api.edgarfiling.sec.gov/docs/index.html

This API reports the status of the EDGAR system. It requires a Filer API Token.

```APIDOC
## GET /status

### Description
Retrieves the current operational status of the EDGAR system.

### Method
GET

### Endpoint
/status

### Parameters
#### Query Parameters
None

#### Request Body
None

### Response
#### Success Response (200)
- **status** (string) - Indicates the operational status of the EDGAR system. Possible values include `OK` or `NO_COMMUNICATION`.

#### Response Example
```json
{
  "status": "OK"
}
```
```

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

### EDGAR API Authentication Errors

Source: https://api.edgarfiling.sec.gov/docs/index.html

Details on how the EDGAR API handles authentication errors, including token validation and error message formatting.

```APIDOC
## EDGAR API Authentication Errors

### Description
The EDGAR API employs token-based authentication. When tokens provided in requests are invalid or improperly formatted, the API returns specific status messages to help diagnose and resolve the issues. These messages indicate the type of error and often include the index of the problematic token.

### Token Indexing
Token indices start from '1'. If multiple tokens are sent, '1' refers to the first token and '2' to the second, and so on.

### Error Levels
- **ERROR**: Returned when authentication is prevented (e.g., 401 or 403 status codes).
- **NOTICE**: Returned when the request authenticates but contains issues with token validation.

### Common Error Messages and Recommended Actions

| Sample Error                                                                     | Recommend Action
```

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

### Error Responses

Source: https://api.edgarfiling.sec.gov/docs/index.html

Details on error responses from the EDGAR API, including structure and common scenarios.

```APIDOC
### Error Responses

The API resources will return an error response when the HTTP status code is in the range of 400-599. An error response from the API methods will consist of an HTTP code, a tracking and locator value, and any relevant messages.

#### Response Example
```json
{
  "tracking": "4c2a2872bb941f61b2d7e7615679c0b0",
  "locator": "91e0e3",
  "messages": [
    {"type": "ERROR", "content": "Forbidden"}
  ]
}
```

An error response will include at least one but possibly more messages. In many cases, the message will match the standard HTTP status code reason, but in some cases, they may provide more context to the error.
```

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

### Filer Management API - Generate CCC

Source: https://api.edgarfiling.sec.gov/docs/index.html

Generates a CCC (Company Classification Code) for a given CIK.

```APIDOC
## POST /fm/{cik}/ccc

### Description
Generate a Company Classification Code (CCC) for a given CIK.

### Method
POST

### Endpoint
/fm/{cik}/ccc

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
None

### Response
#### Success Response (200)
- **ccc** (string) - The generated CCC.

#### Response Example
```json
{
  "ccc": "XYZ123"
}
```
```

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

### Filer Management API - Change Individual Roles

Source: https://api.edgarfiling.sec.gov/docs/index.html

Changes the roles of individuals associated with a filer's account.

```APIDOC
## PUT /fm/{cik}/individuals

### Description
Change roles of individuals associated with a filer's account.

### Method
PUT

### Endpoint
/fm/{cik}/individuals

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
- **name** (string) - Required - The name of the individual.
- **newRole** (string) - Required - The new role for the individual.

### Response
#### Success Response (200)
- **message** (string) - Confirmation message indicating the role was updated.

#### Response Example
```json
{
  "message": "Individual role updated successfully."
}
```
```

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

### Filer Management API - Remove Individuals

Source: https://api.edgarfiling.sec.gov/docs/index.html

Removes individuals associated with a filer's account.

```APIDOC
## DELETE /fm/{cik}/individuals

### Description
Remove individuals associated with a filer's account.

### Method
DELETE

### Endpoint
/fm/{cik}/individuals

### Parameters
#### Path Parameters
- **cik** (string) - Required - The Central Index Key (CIK) of the filer.

#### Query Parameters
None

#### Request Body
- **name** (string) - Required - The name of the individual to remove.

### Response
#### Success Response (200)
- **message** (string) - Confirmation message indicating the individual was removed.

#### Response Example
```json
{
  "message": "Individual removed successfully."
}
```
```

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

### Decoded User API Token Header

Source: https://api.edgarfiling.sec.gov/docs/index.html

A JSON representation of the decoded header for a User API Token, including user identification and expiration details.

```json
{
  "kid": "75c8d379-2d82-415e-a3c5-7501699e3101",
  "alg": "ECDH-ES",
  "userId": "0ebc7681-2b96-42a8-8e76-efd8c23b1b13",
  "expiresAt": "2024-08-24T03:00:00Z"
}
```

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

### Decoded Filer API Token Header

Source: https://api.edgarfiling.sec.gov/docs/index.html

A JSON representation of the decoded header for a Filer API Token, showing fields like CIK, key ID, and expiration date.

```json
{
  "cik": "0000000000",
  "kid": "75c8d379-2d82-415e-a3c5-7501699e3101",
  "alg": "ECDH-ES",
  "expiresAt": "2025-07-25T03:00:00Z"
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.