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

Event publication

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

This API exposes 3 operations across 3 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 26Q1.1.

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

3 operations 3 paths 3 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

University of Texas at Austin Events 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 3

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

Events 3

Event publication

POST
/v3/notifications/events/publish
Publish event
publishEvent 1 param body → 200400401500
POST
/v3/notifications/eventsdeprecated
Post event
postEvent 1 param body → 200400401500
POST
/v3/notifications/events/endSeries
End event series
endEventSeries 1 param body → 200400401500

Schemas 3

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

Event
object
13 properties 3 required
EventSeries
object
3 properties 3 required
RespBasic
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-texas-at-austin-events-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 File Operations API
University of Texas at Austin General API
University of Texas at Austin Jobs API
Where this information came from

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