University of Texas at Austin Sharing API
In addition to fine grained permissions support, Tapis also supports a higher level approach to granting access.This approach is known simply as *sharing*. The sharing API allows an application owner to share an applicationwith a set of users as well as share publicly with all users in a tenant. Sharing grants users READ access to theapplication and more importantly facilitates allowing others to run a job using the application.Please note that sharing an application gives a user certain implicit access to resources in the context of runninga job. For example, if the application has defined a specific execution system id then while the job is running theuser who has been granted access to the application via sharing will also have the applications owner'sauthorizations when accessing the system and paths on the system. Note that the application owner's authorizationssupplement the user's authorizations, they do not replace them.
University of Texas at Austin Sharing 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 Sharing. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.
This API exposes 19 operations across 15 paths, and defines 22 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/.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
University of Texas at Austin Sharing 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 19
Across 15 paths, the API surfaces 19 operations — 1 DELETE, 4 GET, 14 POST. Each is listed below with its method, path, parameters, and response codes.
In addition to fine grained permissions support, Tapis also supports a higher level approach to granting access.
Schemas 22
The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are SkShareRecord (10 properties), RespUnShareJob (7 properties), RespShareInfo (7 properties), RespBasic (7 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 University of Texas at Austin 12
Other APIs University of Texas at Austin publishes across the network.
This is an independent, third-party profile of University of Texas at Austin Sharing 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.