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

Permit.io Elements Configs (EAP) API

The Elements Configs (EAP) API from Permit.io — 4 operation(s) for elements configs (eap).

Permit.io Elements Configs (EAP) 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 Elements Configs (EAP). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 4 paths, and defines 14 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.

6 operations 4 paths 14 schemas 1 DELETE3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2.0.0
Base URL
https://api.permit.io
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Permit.io Elements Configs (EAP) 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 6

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

Elements Configs (EAP) 6
GET
/v2/elements/{proj_id}/{env_id}/config
List Elements Configs
list_elements_configs 4 params → 200422
POST
/v2/elements/{proj_id}/{env_id}/config
Create Elements Config
create_elements_config 2 params body → 200422
GET
/v2/elements/{proj_id}/{env_id}/config/{elements_config_id}
Get Elements Config
get_elements_config 3 params → 200422
PATCH
/v2/elements/{proj_id}/{env_id}/config/{elements_config_id}
Update Elements Config
update_elements_config 3 params body → 200422
GET
/v2/elements/{proj_id}/{env_id}/config/{elements_config_id}/runtime
Get Elements Config Runtime
get_elements_config_runtime 4 params → 200422
DELETE
/v2/elements/{proj_id}/{env_id}/{elements_config_id}
Delete Elements Config
delete_elements_config 3 params → 204422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are ElementsConfigRead (14 properties), WebhookRead (8 properties), ElementsConfigCreate (7 properties), ElementsConfigUpdate (6 properties). Each schema is shown below with its type and property counts.

WebhookType
string
An enumeration.
PermissionLevelRoleRead
object
4 properties 4 required
WebhookRead
object
8 properties 8 required
HTTPValidationError
object
1 property
ElementsConfigRuntimeRead
object
2 properties 2 required
PaginatedResult_ElementsConfigRead_
object
3 properties 2 required
ValidationError
object
3 properties 3 required
ElementsConfigUpdate
object
6 properties 1 required
ElementsPermissionLevel
string
An enumeration.
ElementsConfigRead
object
14 properties 12 required
WebhookUpdate
object
2 properties
ElementsType
string
An enumeration.
WebhookCreateWithElements
object
3 properties 1 required
ElementsConfigCreate
object
7 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

permit-io-elements-configs-eap-api-openapi.yml Raw ↑

Other APIs Permit.io publishes across the network.

Permit.io Access Requests (EAP) API
Permit.io Activity Log API
Permit.io API History API
Permit.io API Keys API
Permit.io Audit Elements Data API
Permit.io Audit Log Replay API
Permit.io Audit Logs API
Permit.io Bulk Operations API
Permit.io Condition Set Rules API
Permit.io Condition Sets API
Permit.io Deprecated API
Permit.io Email Configurations API
Where this information came from

This is an independent, third-party profile of Permit.io Elements Configs (EAP) 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.