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 Calgary Auroral Transport Model (ATM) API

Endpoints to utilize the Auroral Transport Model

University of Calgary Auroral Transport Model (ATM) API is one of 16 APIs that University of Calgary publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Auroral Transport Model (ATM). The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 4 paths, and defines 22 schemas. It is described by OpenAPI 3.0.1, at version stable.

Requests are made against 3 base URLs: https://api.aurorax.space, https://api.staging.aurorax.space, http://localhost:8080/.

4 operations 4 paths 22 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
stable
Base URL
https://api.phys.ucalgary.ca/
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

University of Calgary Auroral Transport Model (ATM) API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (Generated by server) (AccessToken). An API key is passed in the header as x-aurorax-api-key (ApiKeyAuth).

  • AccessToken — Send the Authorization header found in the response of a successful /authentication request on all secure endpoints. Copy it verbatim to the request header. It…
  • ApiKeyAuth — API keys are intended to be used by non-interactive software interfacing with the REST API. These can be used instead of an Access Token approach.

Paths & Operations 4

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

Auroral Transport Model (ATM) 4

Endpoints to utilize the Auroral Transport Model

POST
/api/v1/atm/forward
Perform forward ATM calculation
atm_forward_api_v1_atm_forward_post body → 200400500422
POST
/api/v1/atm/inverse
Perform inverse ATM calculation
atm_inverse_api_v1_atm_inverse_post body → 200400500422
POST
/api/v2/atm/forward
Perform forward ATM calculation
atm_forward_api_v2_atm_forward_post body → 200400500422
POST
/api/v2/atm/inverse
Perform inverse ATM calculation
atm_inverse_api_v2_atm_inverse_post body → 200400500422

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are src__atm__v2__schemas_forward__ATMForwardRequestOutputFlags (40 properties), src__atm__v2__schemas_forward__ATMForwardResponseData (40 properties), src__atm__v1__schemas_forward__ATMForwardResponseData (29 properties), src__atm__v1__schemas_forward__ATMForwardRequestOutputFlags (29 properties). Each schema is shown below with its type and property counts.

ATMForwardCustomNeutralProfile
object
7 properties 7 required
src__atm__v2__schemas_inverse__ATMInverseResponse
object
3 properties 3 required
src__atm__v1__schemas_inverse__ATMInverseResponseData
object
26 properties
src__atm__v1__schemas_inverse__ATMInverseRequestOutputFlags
object
26 properties
src__atm__v1__schemas_inverse__ATMInverseRequest
object
13 properties 3 required
src__atm__v2__schemas_forward__ATMForwardResponseData
object
40 properties
src__atm__v2__schemas_forward__ATMForwardRequestOutputFlags
object
40 properties
ATMForwardCustomSpectrum
object
2 properties 2 required
src__atm__v1__schemas_forward__ATMForwardResponse
object
3 properties 3 required
ATMInverseForwardRequest
object
9 properties 9 required
src__atm__v2__schemas_inverse__ATMInverseRequestOutputFlags
object
4 properties
src__atm__v1__schemas_forward__ATMForwardResponseData
object
29 properties
src__atm__v2__schemas_forward__ATMForwardResponse
object
3 properties 3 required
src__atm__v2__schemas_inverse__ATMInverseRequest
object
12 properties 3 required
src__atm__v1__schemas_forward__ATMForwardRequestOutputFlags
object
29 properties
ValidationError
object
5 properties 3 required
src__atm__v2__schemas_forward__ATMForwardRequest
object
25 properties 3 required
src__atm__v1__schemas_forward__ATMForwardRequest
object
16 properties 3 required
HTTPValidationError
object
1 property
ErrorMessage
object
1 property 1 required
src__atm__v1__schemas_inverse__ATMInverseResponse
object
4 properties 3 required
src__atm__v2__schemas_inverse__ATMInverseResponseData
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-calgary-auroral-transport-model-atm-api-openapi.yml Raw ↑

Other APIs University of Calgary publishes across the network.

PRISM Institutional Repository (DSpace)
PRISM Research Data Repository (Borealis Dataverse)
University of Calgary Application.wadl API
University of Calgary Authenticate API
University of Calgary Availability API
University of Calgary Conjunction Search API
University of Calgary Data Distribution API
University of Calgary Data Products Search API
University of Calgary Data Sources API
University of Calgary Ephemeris Search API
University of Calgary Manage Data API
University of Calgary Operations - SITL API
Where this information came from

This is an independent, third-party profile of University of Calgary Auroral Transport Model (ATM) 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.