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

manage job subscriptions

University of Texas at Austin Subscriptions 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 Subscription. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 17 operations across 11 paths, and defines 30 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/.

17 operations 11 paths 30 schemas 4 DELETE6 GET1 PATCH6 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 Subscriptions 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 17

Across 11 paths, the API surfaces 17 operations — 4 DELETE, 6 GET, 1 PATCH, 6 POST. Each is listed below with its method, path, parameters, and response codes.

Subscriptions 17

manage job subscriptions

DELETE
/jobs/subscribe/{uuid}
Delete subscriptions
deleteSubscriptions 1 param → 200400401403500
GET
/jobs/subscribe/{jobUuid}
Get subscriptions
getSubscriptions 3 params → 200400401403500
POST
/jobs/subscribe/{jobUuid}
Subscribe
subscribe 1 param body → 200400401403500
GET
/v3/notifications/subscriptions
Get subscriptions
getV3NotificationsSubscriptions 9 params → 200400401500
POST
/v3/notifications/subscriptions
Post subscription
postSubscription body → 201400401409500
GET
/v3/notifications/subscriptions/search
Search subscriptions query parameters
searchSubscriptionsQueryParameters 8 params → 200400401500
POST
/v3/notifications/subscriptions/search
Search subscriptions request body
searchSubscriptionsRequestBody 7 params body → 200400401500
GET
/v3/notifications/subscriptions/byName/{name}
Get subscription by name
getSubscriptionByName 3 params → 200400401404500
PATCH
/v3/notifications/subscriptions/byName/{name}
Patch subscription by name
patchSubscriptionByName 2 params body → 200400401404500
DELETE
/v3/notifications/subscriptions/byName/{name}
Delete subscription by name
deleteSubscriptionByName 2 params → 200401404500
GET
/v3/notifications/subscriptions/byUuid/{uuid}
Get subscription by uuid
getSubscriptionByUuid 2 params → 200400401404500
DELETE
/v3/notifications/subscriptions/byUuid/{uuid}
Delete subscription by uuid
deleteSubscriptionByUuid 1 param → 200401404500
DELETE
/v3/notifications/subscriptions/bySubject/{subject}
Delete subscriptions by subject
deleteSubscriptionsBySubject 3 params → 200401500
GET
/v3/notifications/subscriptions/{name}/isEnabled
Is enabled
isEnabled 2 params → 200401404500
POST
/v3/notifications/subscriptions/{name}/enable
Enable subscription
enableSubscription 2 params → 200401404500
POST
/v3/notifications/subscriptions/{name}/disable
Disable subscription
disableSubscription 2 params → 200401404500
POST
/v3/notifications/subscriptions/{name}/updateTTL/{ttlMinutes}
Update TTL
updateTTL 3 params → 200401404500

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are TapisSubscription_2 (13 properties), TapisSubscription (13 properties), ReqPostSubscription (8 properties), RespChangeCount (7 properties). Each schema is shown below with its type and property counts.

RespGetSubscriptions
object
7 properties
TapisSubscription
object
13 properties
RespBasic
object
7 properties
RespResourceUrl
object
7 properties
ResultResourceUrl
object
1 property
ReqSubscribe
object
5 properties
ResultMetadata
object
NotifDeliveryTarget
object
2 properties
DeliveryTarget
object
2 properties
ResultChangeCount
object
1 property
TypeFilterString
string
TapisSubscription_2
object
13 properties
ResultBoolean
object
1 property
DescriptionString
string
DeliveryMethod
string
RespBasic_2
object
7 properties
ReqSearchSubscriptions
object
1 property 1 required
ReqPatchSubscription
object
4 properties
RespSubscription
object
7 properties
RespResourceUrl_2
object
7 properties
NameString
string
ReqPostSubscription
object
8 properties 3 required
UserNameApiDefaultString
string
DeliveryTarget_2
object
2 properties 2 required
RespSubscriptions
object
7 properties
UserNameString
string
SubjectFilterString
string
RespBoolean
object
7 properties
RespChangeCount
object
7 properties
DeliveryTargets
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-texas-at-austin-subscriptions-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 Subscriptions 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.