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

Queensland University of Technology Authorization API

OAuth 2.0 authorization and device / CIBA initiation.

Queensland University of Technology Authorization API is one of 16 APIs that Queensland University of Technology publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

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

This API exposes 4 operations across 4 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://esoe.qut.edu.au/auth/realms/qut.

4 operations 4 paths 1 schemas 1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://eprints.qut.edu.au/cgi/oai2
Authentication
HTTP Bearer, OAuth 2.0
License
Not stated
Resource Areas
1

Authentication & Security 2

Queensland University of Technology Authorization API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows, exposing 14 scopes. By default, every request must be authenticated.

  • bearerAuth — Access token issued by this realm.
  • oauth2 — Scopes below are exactly the scopessupported array of the live discovery document. ServiceAccount, serviceaccount and Integsvctestclient are QUT-specific clien…

Paths & Operations 4

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

Authorization 4

OAuth 2.0 authorization and device / CIBA initiation.

GET
/protocol/openid-connect/auth
OAuth 2.0 authorization endpoint
authorize 7 params → 302400
POST
/protocol/openid-connect/auth/device
OAuth 2.0 Device Authorization (RFC 8628)
deviceAuthorization → 200401
POST
/protocol/openid-connect/ext/par/request
Pushed Authorization Request (RFC 9126)
pushedAuthorizationRequest → 201400
POST
/protocol/openid-connect/ext/ciba/auth
Client Initiated Backchannel Authentication (CIBA)
backchannelAuthentication → 200400

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is OAuthError (3 properties). Each schema is shown below with its type and property counts.

OAuthError
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qut-authorization-api-openapi.yml Raw ↑

Other APIs Queensland University of Technology publishes across the network.

QUT Shibboleth Identity Provider
QUT eResearch Agent Plugin Marketplace
QUT Library Discovery (Ex Libris Primo VE tenant)
QUT Canvas LMS (Instructure tenant)
QUT collection in ARDC Research Data Australia
DataCite DOI and RAiD registration
Crossref membership
ROR registration
Australian Access Federation membership
Queensland University of Technology Client Registration API
Queensland University of Technology Datasets API
Queensland University of Technology Discovery API
Where this information came from

This is an independent, third-party profile of Queensland University of Technology Authorization 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.