Permit.io Users API
Users represent human end-users of your applications that you'd like to enforce permissions on.You must create a user object in Permit.io prior to trying to enforce permissions for that user.A user is identified by its key, and you can only create one user with the same key inside a Permit environment.You can place users within tenants via role assignments in order to enforce multi-tenancy in your app.You may create users via the API (shown below), with one of the SDKs, or via the Permit cloud console.
Permit.io Users 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. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 8 operations across 3 paths, and defines 14 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Permit.io Users 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 8
Across 3 paths, the API surfaces 8 operations — 2 DELETE, 2 GET, 1 PATCH, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Users represent human end-users of your applications that you'd like to enforce permissions on. You must create a user object in Permit.io prior to trying to enforce permissions f…
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are UserRead (13 properties), RoleAssignmentRead (13 properties), UserCreate (6 properties), UserInTenant (4 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 Users 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.