Skip to content

Authentication

Requests to FloQast's API must be authenticated using an API key. The API key must be included in the x-api-key header of each request and can be generated in the FloQast application. The key should also have the correct permissions to access the API endpoints you are using. Directions to generate an API key

Download OpenAPI description
Languages
Servers
Mock server

https://developer.floqast.app/_mock/content/api-reference/openapi/

https://fq-api.floqast.app/

https://fq-api.eu.floqast.app/

https://fq-api.au.floqast.app/

Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations
Operations

Deactivates one control and unlinks associated risks, tests, and FSLIs/scoping sheets

Request

Security
x-api-key
Path
idstring(ObjectId)^[a-f\d]{24}$required

The internal unique identifier for the control

Example: 61d325c84a9f97631731a690
curl -i -X PUT \
  https://developer.floqast.app/_mock/content/api-reference/openapi/api/v1/controls/61d325c84a9f97631731a690/deactivate \
  -H 'x-api-key: YOUR_API_KEY_HERE'

Responses

Control was successfully deactivated

Response
No content

Reactivate one control and link associated tests

Request

Security
x-api-key
Path
idstring(ObjectId)^[a-f\d]{24}$required

The internal unique identifier for the control

Example: 61d325c84a9f97631731a690
curl -i -X PUT \
  https://developer.floqast.app/_mock/content/api-reference/openapi/api/v1/controls/61d325c84a9f97631731a690/reactivate \
  -H 'x-api-key: YOUR_API_KEY_HERE'

Responses

Control was successfully reactivated

Response
No content
Operations
Operations
Operations