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

University of Texas at Austin Permissions API

The permissions model allows for fine grained access control of resources. The application ownermay grant READ and MODIFY permission to specific users. MODIFY implies READ.Please note that Tapis also supports a higher level approach to granting access known as *Sharing* that also includescertain implicit access to resources during the execution of a Tapis job.

University of Texas at Austin Permissions API is one of 21 APIs that University of Texas at Austin publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Permissions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 11 operations across 7 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: http://localhost:8080/, https://dev.develop.tapis.io/.

11 operations 7 paths 11 schemas 3 DELETE3 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://tacc.tapis.io/v3
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

University of Texas at Austin Permissions API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Tapis-Token (TapisJWT).

  • TapisJWT — Tapis signed JWT token authentication

Paths & Operations 11

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

Permissions 11

The permissions model allows for fine grained access control of resources. The application owner may grant READ and MODIFY permission to specific users. MODIFY implies READ. Pleas…

GET
/v3/apps/perms/{appId}/user/{userName}
Get user perms
getUserPerms 2 params → 200400403404500
POST
/v3/apps/perms/{appId}/user/{userName}
Grant user perms
grantUserPerms 2 params body → 200400403500
POST
/v3/apps/perms/{appId}/user/{userName}/revoke
Revoke user perms
revokeUserPerms 2 params body → 200403500
DELETE
/v3/apps/perms/{appId}/user/{userName}/{permission}
Revoke user perm
revokeUserPerm 3 params → 200400403500
GET
/v3/files/permissions/{systemId}/{path}
Get permissions
getPermissions 3 params → 200
POST
/v3/files/permissions/{systemId}/{path}
Grant permissions
grantPermissions 2 params body → 200
DELETE
/v3/files/permissions/{systemId}/{path}
Delete permissions
deletePermissions 3 params → 200
GET
/v3/systems/perms/{systemId}/user/{userName}
Get user perms
getV3SystemsPermsBySystemIdUserByUserName 2 params → 200400403404500
POST
/v3/systems/perms/{systemId}/user/{userName}
Grant user perms
postV3SystemsPermsBySystemIdUserByUserName 2 params body → 200400403500
POST
/v3/systems/perms/{systemId}/user/{userName}/revoke
Revoke user perms
postV3SystemsPermsBySystemIdUserByUserNameRevoke 2 params body → 200403500
DELETE
/v3/systems/perms/{systemId}/user/{userName}/{permission}
Revoke user perm
deleteV3SystemsPermsBySystemIdUserByUserNameByPermission 3 params → 200400403500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are RespNameArray (7 properties), RespBasic (7 properties), StringResponse (7 properties), FilePermissionResponse (7 properties). Each schema is shown below with its type and property counts.

UserNameString
string
RespBasic
object
7 properties
IdString
string
ResultNameArray
object
1 property
RespNameArray
object
7 properties
ReqPerms
object
1 property 1 required
FilePermission
object
5 properties
FilePermissionResponse
object
7 properties
StringResponse
object
7 properties
CreatePermissionRequest
object
2 properties 2 required
PermEnum
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-texas-at-austin-permissions-api-openapi.yml Raw ↑

Other APIs University of Texas at Austin publishes across the network.

UT Austin Enterprise Identity Provider (SAML 2.0 + OpenID Connect)
Texas ScholarWorks DSpace REST API
Texas ScholarWorks OAI-PMH Endpoint
Texas Data Repository (Dataverse) — UT Austin collection
University of Texas at Austin Applications API
University of Texas at Austin Archive transfers (Beta) API
University of Texas at Austin Child Systems API
University of Texas at Austin Content API
University of Texas at Austin Credentials API
University of Texas at Austin Events API
University of Texas at Austin File Operations API
University of Texas at Austin General API
Where this information came from

This is an independent, third-party profile of University of Texas at Austin Permissions 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.