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 Invites API

The User Invites API from Permit.io — 3 operation(s) for user invites.

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

This API exposes 6 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.

6 operations 3 paths 14 schemas 1 DELETE2 GET1 PATCH2 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 Invites 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 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

User Invites 6
GET
/v2/facts/{proj_id}/{env_id}/user_invites
List User Invites
list_user_invites 7 params → 200422
POST
/v2/facts/{proj_id}/{env_id}/user_invites
Create User Invite
create_user_invite 2 params body → 200422
GET
/v2/facts/{proj_id}/{env_id}/user_invites/{user_invite_id}
Get User Invite
get_user_invite 3 params → 200422
DELETE
/v2/facts/{proj_id}/{env_id}/user_invites/{user_invite_id}
Delete User Invite
delete_user_invite 3 params → 204422
PATCH
/v2/facts/{proj_id}/{env_id}/user_invites/{user_invite_id}
Update User Invite
update_user_invite 3 params body → 200422
POST
/v2/facts/{proj_id}/{env_id}/user_invites/{user_invite_id}/approve
Approve User Invite
approve_user_invite 3 params body → 200400422

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are ElementsUserInviteRead (14 properties), UserRead (13 properties), ElementsUserInviteCreate (8 properties), ElementsUserInviteUpdate (8 properties). Each schema is shown below with its type and property counts.

UserStatus
string
An enumeration.
ElementsUserInviteCreate
object
8 properties 8 required
UserRead
object
13 properties 7 required
HTTPValidationError
object
1 property
UserRole
object
2 properties 2 required
ElementsUserInviteRead
object
14 properties 14 required
UserInTenant
object
4 properties 3 required
ElementsUserInviteUpdate
object
8 properties 8 required
PaginatedResult_ElementsUserInviteRead_
object
3 properties 2 required
UserInviteStatus
string
An enumeration.
ApproveMessage
object
1 property 1 required
UserResourceInstanceRole
object
3 properties 3 required
ValidationError
object
3 properties 3 required
ElementsUserInviteApprove
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

permit-io-user-invites-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 Invites 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.