Permit.io Condition Sets API
Condition sets are sets of objects that are dynamically defined based on conditions on the objects' attributes.Conditions sets allows you the flexibility of ABAC with the simplicity of RBAC.There are currently two types of condition sets at the moment:1) user set = the set of users that match all the specified conditions.2) resource set = the set of resources that match all the specified conditions.Examples:- `us_based_employees` = {U1, ..., Un} = {all **users** who are *located in the US* and are *assigned the employee role*}- `private_repos` = {R1, ..., Rn} = {all **resources** *of type repository* that *are private*}We can then picture a **matrix** of assignment between *user sets* and *resource sets*.Example:If we check the checkbox where `us_based_employees` and `private_repos->clone` action intersect, we are setting a rule:*all US based employees can clone private repos*.
Permit.io Condition Sets API is one of 43 APIs that Permit.io publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Condition Sets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 7 operations across 4 paths, and defines 16 schemas. It is described by OpenAPI 3.1.0, at version 2.0.0.
Requests are made against the base URL https://api.permit.io.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Permit.io Condition Sets API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (HTTPBearer).
HTTPBearer— Authorization header, we support the bearer authentication scheme (see: RFC 6750)
Paths & Operations 7
Across 4 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Condition sets are sets of objects that are dynamically defined based on conditions on the objects' attributes. Conditions sets allows you the flexibility of ABAC with the simplic…
Schemas 16
The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are ResourceRead (19 properties), ResourceRoleRead (15 properties), ConditionSetRead (15 properties), ConditionSetCreate (8 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Permit.io 12
Other APIs Permit.io publishes across the network.
This is an independent, third-party profile of Permit.io Condition Sets 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.