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 User Attributes API

User attributes allow you to specify an arbitrary schema attributes that are partof the definition of the User resource.Attributes are used to enforce attribute-based access control policies.*NOTE: A User is a Resource by itself, so basically a user's attribute is an attribute that assigned to the resource called "user".*For example, if we are building the github's permissions system, we might want to knowwhether the user is an owner of the organization or not. In such case we willdefine a string `owner` attribute that we can now use in our policies.

Permit.io User Attributes 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 User Attributes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 2 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.permit.io.

5 operations 2 paths 6 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Permit.io User Attributes 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 5

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

User Attributes 5

User attributes allow you to specify an arbitrary schema attributes that are part of the definition of the User resource. Attributes are used to enforce attribute-based access con…

GET
/v2/schema/{proj_id}/{env_id}/users/attributes
List User Attributes
list_user_attributes 5 params → 200422
POST
/v2/schema/{proj_id}/{env_id}/users/attributes
Create User Attribute
create_user_attribute 3 params body → 200422
GET
/v2/schema/{proj_id}/{env_id}/users/attributes/{attribute_id}
Get User Attribute
get_user_attribute 4 params → 200422
DELETE
/v2/schema/{proj_id}/{env_id}/users/attributes/{attribute_id}
Delete User Attribute
delete_user_attribute 6 params → 204422
PATCH
/v2/schema/{proj_id}/{env_id}/users/attributes/{attribute_id}
Update User Attribute
update_user_attribute 4 params body → 200422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ResourceAttributeRead (12 properties), ValidationError (3 properties), ResourceAttributeCreate (3 properties), ResourceAttributeUpdate (2 properties). Each schema is shown below with its type and property counts.

ResourceAttributeCreate
object
3 properties 2 required
ResourceAttributeUpdate
object
2 properties
HTTPValidationError
object
1 property
AttributeType
string
supported attribute primitives
ResourceAttributeRead
object
12 properties 11 required
ValidationError
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

permit-io-user-attributes-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 Elements Configs (EAP) API
Where this information came from

This is an independent, third-party profile of Permit.io User Attributes 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.