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

SnackMagic Authentication API

Stadium uses JWT (as Bearer token) for authentication. API provides 4 different methods to generate the token:1. Client Credentials2. Authorization Code (OAuth2)3. Authorization Code using PKCE4. Token using refresh tokenThe authentication method to be used depends on your use case - whether you want to place orders using a globalorganizer account or user's own Stadium Account and your implementation details.For each method, once you generate a _token_, it needs to be set as the _Bearer_ token in the **Authorization** header.The _token_ is valid for **24 hours**. The _token_ validity can be checked with our **Validate token** API endpoint.Once expired, a new _token_ will need to be generated using the same API endpoint as used earlier.### Client CredentialsThis should be used if you are an organizer and want to place an order or send points using a **global** organizer account.You can directly use the **Get Token** API endpoint to fetch the _token_ that can then be used in other APIs for authorization.### Authorization Code (OAuth2)This should be used if you want to place an order or send points on **behalf** of a Stadium user. This uses Oauth2 flow where you will needneed to make an **Authorize** request first. This will redirect the user to the Stadium login page and once they sign in, a *code* isreceived on the given `redirect_url`. Using this _code_, the _token_ can be fetched using the **Get Token by Code** API providing both`client_id` and `client_secret`. The `redirect_url` should be the same as given in the authorize call.### Authorization Code using PKCEIf you want to use the Authorization code method but cannot store the `client_secret` securely (like native application or SPA) you should usethis flow. In this you need to [generate a PKCE](https://developer.pingidentity.com/en/tools/pkce-code-generator.html) `code_challenge` and `code_verifier`using the SHA256 method. The `code_challenge` needs to sent as an additional param to the **Authorize** request. Once the _code_ is received send the`code_verifier` as the param (instead of `client_secret`) to the **Get Token by Code** API.### Token using refresh tokenYou can use this to issue a new access token using an existing access token and a refresh token.

SnackMagic Authentication API is one of 5 APIs that SnackMagic publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against 2 base URLs: https://api.bystadium.com/api/v2, https://api.preprod.bystadium.com/api/v2.

5 operations 5 paths 0 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.bystadium.com/api/v2
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

SnackMagic Authentication API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (Token).

Paths & Operations 5

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

Authentication 5

Stadium uses JWT (as Bearer token) for authentication. API provides 4 different methods to generate the token: 1. Client Credentials 2. Authorization Code (OAuth2) 3. Authorizatio…

POST
/oauth/token
Get token
getToken body → 200
GET
/oauth/authorize
Authorize
authorize body → 200
POST
/oauth/token_by_code
Get token by code
getTokenByCode body → 200
POST
/oauth/token_by_refresh_token
Get token by refresh token
getTokenByRefreshToken body → 200
POST
/oauth/validate
Validate token
validateToken → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

snackmagic-authentication-api-openapi.yml Raw ↑

Other APIs SnackMagic publishes across the network.

SnackMagic Automation management API
SnackMagic Order management API
SnackMagic Store management API
SnackMagic User management API
Where this information came from

This is an independent, third-party profile of SnackMagic Authentication 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.