How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

dope.security Policies API

Everything about your Policies

dope.security Policies API is one of 4 APIs that dope.security publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Policies. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 16 operations across 9 paths, and defines 25 schemas. It is described by OpenAPI 3.2.0, at version 1.0.3.

Requests are made against a single base URL, https://api.flightdeck.dope.security/v1.

16 operations 9 paths 25 schemas 3 DELETE6 GET1 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.3
Base URL
https://api.flightdeck.dope.security/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

dope.security Policies API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 16

Across 9 paths, the API surfaces 16 operations — 3 DELETE, 6 GET, 1 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Policies 16

Everything about your Policies

GET
/policies
List Policies
listPolicies 3 params → 200400403500
POST
/policies/{policy_name}
Create a Policy
createPolicy 1 param → 200400403500
DELETE
/policies/{policy_name}
Delete a Policy
deletePolicy 1 param → 200400403500
GET
/policies/{policy_name}/content
Get Policy Content
getPolicyContent 1 param → 200400403500
PUT
/policies/{policy_name}/content/restrictions
Update Policy Content Restrictions
updatePolicyRestrictions 1 param body → 200400403500
PUT
/policies/{policy_name}/content/exceptions
Update Policy Content Exceptions
updatePolicyExceptions 1 param body → 200400403500
GET
/policies/{policy_name}/assignments
Get Policy Assignments
getPolicyAssignments 1 param → 200400403500
PUT
/policies/{policy_name}/assignments
Update Policy Assignments
updatePolicyAssignments 1 param body → 200400403500
GET
/policies/{policy_name}/bypass/urls
Get URL Bypass
getUrlBypass 1 param → 200400403500
PUT
/policies/{policy_name}/bypass/urls
Upsert URL Bypass
upsertUrlBypass 1 param body → 200400401500
DELETE
/policies/{policy_name}/bypass/urls
Delete Custom URL Bypass Entries
deleteCustomUrlBypass 1 param body → 200400403500
GET
/policies/{policy_name}/bypass/applications
Get Application Bypass
getApplicationBypass 1 param → 200400403500
PUT
/policies/{policy_name}/bypass/applications
Upsert Application Bypass
upsertApplicationBypass 1 param body → 200400401500
DELETE
/policies/{policy_name}/bypass/applications
Delete Custom Application Bypass Entries
deleteCustomApplicationBypass 1 param body → 200400403500
GET
/policies/{policy_name}/ssl-inspection
Get SSL Inspection Configuration
getSslInspection 1 param → 200400403500
PUT
/policies/{policy_name}/ssl-inspection
Update SSL Inspection Configuration
updateSslInspection 1 param body → 200400403500

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are CategorySettings (4 properties), CategoryException (4 properties), CustomBypassItem (4 properties), Policy (4 properties). Each schema is shown below with its type and property counts.

SuccessMessage
object
A simple message response indicating a successful operation
1 property 1 required
Policy
object
Summary of a policy
4 properties 3 required
AssignedUser
object
A user assigned to a policy
2 properties 2 required
ApplicationBypassUpdateBody
object
Payload for upserting application bypass entries. At least one of custom or default must be provided. Under each, at least one of mac or windows must be provid…
2 properties
SslInspectionStateBody
object
Set a custom SSL inspection state on a policy.
1 property 1 required
PolicyContentResponse
object
1 property 1 required
UrlBypassUpdateBody
object
Payload for upserting URL bypass entries. At least one of custom or default must be provided. Unmentioned custom entries are preserved. Unknown default entry n…
2 properties
CategorySettings
object
Settings for a dope category
4 properties 1 required
PaginationResponse
object
Information about current and next page for cursor based pagination
2 properties 2 required
AssignedGroup
object
A group assigned to a policy
3 properties 3 required
PolicyContentRestrictionsRequest
object
Request body for updating restrictions on dope and custom categories
1 property 1 required
CustomBypassItem
object
A custom application bypass entry defined by the admin
4 properties 2 required
CategoryExceptionUpdate
object
Exception settings used in write operations
2 properties 1 required
CategoryException
object
Per-entity override of a category restriction
4 properties 1 required
BaseInheritance
object
Signals that settings are inherited from the base policy
1 property 1 required
SslInspectionResponse
SSL inspection configuration for a policy.
CustomCategoryRestrictionUpdate
object
Custom category restriction settings used in write operations
2 properties 1 required
PolicyContentExceptionsRequest
object
Request body for updating user/group exceptions on categories
1 property 1 required
CustomCategorySettings
object
Settings for a custom category
3 properties 1 required
CategoryBlock
object
Wrapper for category data with inheritance flag
2 properties 2 required
CustomCategoryBlock
object
Wrapper for custom category data with inheritance flag
2 properties 2 required
DefaultBypassItem
object
A read-only bypass entry pre-configured by Dope Security. Default entries cannot be created or deleted, but partners can set their state to ignored to prevent…
2 properties 2 required
CategoryRestrictionUpdate
object
Category restriction settings used in write operations
2 properties 1 required
CustomBypassRequestItem
object
A custom bypass entry for write operations.
2 properties 1 required
Errors
object
Error response containing a list of errors related to 400 and 500 http status
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dopesecurity-policies-api-openapi.yml Raw ↑

Other APIs dope.security publishes across the network.

dope.security Authorization API
dope.security Custom Categories API
dope.security Endpoints API
Where this information came from

This is an independent, third-party profile of dope.security Policies API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.