University of Texas at Austin Scheduler Profiles API
The Systems service supports managing Tapis scheduler profiles. An HPC center often has certain conventionsand restrictions around the use of batch schedulers. A scheduler profile resource can be defined to provide theTapis Jobs service with additional site specific information to be used when executing applications using ascheduler. A scheduler profile contains information on options that should be hidden from the scheduler,the module load command to use and which modules should be loaded by default when running a job. Anyone in atenant may create a scheduler profile for use by all users in the tenant. The owner of a profile or atenant administrator may modify or delete a profile. A profile may referenced in a system definition using theattribute *batchSchedulerProfile*. The profile to be used may also be set in the job submit request using thespecial scheduler option *--tapis-profile*. The value in the job submit request takes precedence over any valuedefined for the execution system.
University of Texas at Austin Scheduler Profiles 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 Scheduler Profiles. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.
This API exposes 4 operations across 2 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 26Q2.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 Scheduler Profiles 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 4
Across 2 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
The Systems service supports managing Tapis scheduler profiles.
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are RespResourceUrl (7 properties), RespSchedulerProfile (7 properties), RespSchedulerProfiles (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 Scheduler Profiles 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.