SnackMagic

SnackMagic is a 100% customizable snack-box gifting service, now part of Stadium, that lets recipients build their own box from 500+ snacks and beverages or receive curated gifts, delivered worldwide. Companies use it for employee, client, prospect, and event gifting. SnackMagic is exposed to developers through the Stadium API (api.bystadium.com), a JSON REST API for embedding a global gift, rewards, and branded-swag catalog, placing orders funded by a pre-purchased Wallet balance, sending Stadium Shop points via treat links, and triggering webhook-automation gift orders. This profile was enriched from the provider's public OpenAPI and developer surface.

SnackMagic publishes 5 API contracts indexed on the APIs.io network, including Authentication API, Automation management API, Order management API, and 2 more. Tagged areas include Company, Consumer, Gifting, Rewards, and Swag.

The SnackMagic catalog on APIs.io includes 1 Spectral governance ruleset.

SnackMagic’s developer surface includes engineering blog, documentation, API reference, getting-started guide, authentication, pricing, signup flow, and 19 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

54.6/100 strong ▬ flat Agent 27/100 agent aware Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

1 published contract 3 Agent Skills

Company Consumer Gifting Rewards Swag Snacks E-Commerce Fulfillment

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Supply Chain Management

BC-520

Order Management

POST /orders POST /orders/{order_number}/checkout GET /orders/{order_number} GET /orders/{order_number}/shipment_status

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 54.6/100 · strong

Contract Quality 10.9 / 19

Developer Ergonomics 9.9 / 15

Access Clarity 11.4 / 15

Operational Transparency 1.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/snackmagic/"><img src="https://apis.io/badge/snackmagic/card.svg" alt="SnackMagic on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Operational Transparency scores 10.5 — up to +11.6 composite points
Contract Quality scores 58.3 — up to +10.4 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/snackmagic/apis.yml: open an issue on github.com/api-evangelist/snackmagic to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Food Safety (GFSI-recognised certification)	long-tail	6.0	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

SnackMagic Authentication API

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. Authorizat...

SnackMagic Automation management API

Automation related API endpoints

SnackMagic Order management API

Order related API endpoints

SnackMagic Store management API

Store related API endpoints

SnackMagic User management API

User related API endpoints

Open Collections 5

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Stadium Authentication API

OPEN COLLECTION

Stadium Authentication Automation management API

OPEN COLLECTION

Stadium Authentication Order management API

OPEN COLLECTION

Stadium Authentication Store management API

OPEN COLLECTION

Stadium Authentication User management API

OPEN COLLECTION

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

Trigger a webhook-automation gift order

AGENT SKILL

Browse a store catalog and place an order

AGENT SKILL

Send Stadium Shop points to a recipient

AGENT SKILL

SnackMagic API pricing

Prices published by SnackMagic, read 2026-10-28 from www.bystadium.com/go/pricing.

Plan	Price
Pay-As-You-Go	No pass needed Includes: Snack Boxes (Snackmagic), Bulk Swag (Swagmagic), Hosted Experiences (Confetti)
Shops Pass	talk to sales Includes: Pay-as-you-go, plus Unlimited Swag & Gift Shops, Free Domestic Delivery
Swag Pass	talk to sales Includes: All of Shops, plus Swag Storage, Inventory Management, Swag Kits
Engagement Pass	talk to sales Includes: All of Swag, plus Automated Gifting, HRIS, ATS, & CRM Integrations, Kudos Programs
Enterprise Pass	talk to sales Includes: All of Engagement, plus SSO, Stadium API, Custom Contracts, Custom Domain & White-Labeled Shops, Cus

Plan details, limits and sources →

Pricing Plans 1

Published pricing tiers and plan structures.

Snackmagic Plans Pricing

5 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

SnackMagic

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Snackmagic Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

SnackMagic API Rules

66 rules · 64 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Snackmagic Stadium Overlay

4 actions · update · snackmagic-stadium-openapi.yml

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Snackmagic Authentication

http/apiKey/oauth2 · 2 schemes

SECURITY

Snackmagic Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Snackmagic Trust Center

trust center published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Snackmagic Agentic Access

15 operations · 8 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgenticAccess

LLMsTxt

AgentSkill

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

TrustCenter

TrustCenter

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 4

The organization behind the API

Blog

BlogRSS

Website

Blog

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Wallet

Wallet

Source (apis.yml)

aid: snackmagic
name: SnackMagic
description: SnackMagic is a 100% customizable snack-box gifting service, now part of Stadium, that lets recipients build
  their own box from 500+ snacks and beverages or receive curated gifts, delivered worldwide. Companies use it for employee,
  client, prospect, and event gifting. SnackMagic is exposed to developers through the Stadium API (api.bystadium.com), a
  JSON REST API for embedding a global gift, rewards, and branded-swag catalog, placing orders funded by a pre-purchased Wallet
  balance, sending Stadium Shop points via treat links, and triggering webhook-automation gift orders. This profile was enriched
  from the provider's public OpenAPI and developer surface.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: high
  source:
  - plans
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://fecdn.snackmagic.com/static/media/snackmagic-logo.b9e03ebf.svg
url: https://raw.githubusercontent.com/api-evangelist/snackmagic/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- craft-ventures
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
tags:
- Company
- Consumer
- Gifting
- Rewards
- Swag
- Snacks
- E-Commerce
- Fulfillment
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: snackmagic:snackmagic-authentication-api
  name: SnackMagic Authentication API
  description: '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. Authorization Code using PKCE

    4. Token using refresh token


    The authentication method to be used depends on your use case - whether you want to place orders using a global

    organizer 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 Credentials


    This 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 need

    need to make an **Authorize** request first. This will redirect the user to the Stadium login page and once they sign
    in, a *code* is

    received 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 PKCE


    If you want to use the Authorization code method but cannot store the `client_secret` securely (like native application
    or SPA) you should use

    this 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 token


    You can use this to issue a new access token using an existing access token and a refresh token.'
  humanURL: https://api.bystadium.com/api/v2/docs
  baseURL: https://api.bystadium.com/api/v2
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/snackmagic-authentication-api-openapi.yml
  - type: ErrorCatalog
    url: errors/snackmagic-problem-types.yml
  - type: Conventions
    url: conventions/snackmagic-conventions.yml
  - type: DataModel
    url: data-model/snackmagic-data-model.yml
  - type: Conformance
    url: conformance/snackmagic-conformance.yml
  - type: Lifecycle
    url: lifecycle/snackmagic-lifecycle.yml
  - type: Sandbox
    url: sandbox/snackmagic-sandbox.yml
- aid: snackmagic:snackmagic-automation-management-api
  name: SnackMagic Automation management API
  description: Automation related API endpoints
  humanURL: https://api.bystadium.com/api/v2/docs
  baseURL: https://api.bystadium.com/api/v2
  tags:
  - Automation management
  properties:
  - type: OpenAPI
    url: openapi/snackmagic-automation-management-api-openapi.yml
  - type: ErrorCatalog
    url: errors/snackmagic-problem-types.yml
  - type: Conventions
    url: conventions/snackmagic-conventions.yml
  - type: DataModel
    url: data-model/snackmagic-data-model.yml
  - type: Conformance
    url: conformance/snackmagic-conformance.yml
  - type: Lifecycle
    url: lifecycle/snackmagic-lifecycle.yml
  - type: Sandbox
    url: sandbox/snackmagic-sandbox.yml
- aid: snackmagic:snackmagic-order-management-api
  name: SnackMagic Order management API
  description: Order related API endpoints
  humanURL: https://api.bystadium.com/api/v2/docs
  baseURL: https://api.bystadium.com/api/v2
  tags:
  - Order Management
  tags_raw:
  - Order management
  properties:
  - type: OpenAPI
    url: openapi/snackmagic-order-management-api-openapi.yml
  - type: ErrorCatalog
    url: errors/snackmagic-problem-types.yml
  - type: Conventions
    url: conventions/snackmagic-conventions.yml
  - type: DataModel
    url: data-model/snackmagic-data-model.yml
  - type: Conformance
    url: conformance/snackmagic-conformance.yml
  - type: Lifecycle
    url: lifecycle/snackmagic-lifecycle.yml
  - type: Sandbox
    url: sandbox/snackmagic-sandbox.yml
- aid: snackmagic:snackmagic-store-management-api
  name: SnackMagic Store management API
  description: Store related API endpoints
  humanURL: https://api.bystadium.com/api/v2/docs
  baseURL: https://api.bystadium.com/api/v2
  tags:
  - Store Management
  tags_raw:
  - Store management
  properties:
  - type: OpenAPI
    url: openapi/snackmagic-store-management-api-openapi.yml
  - type: ErrorCatalog
    url: errors/snackmagic-problem-types.yml
  - type: Conventions
    url: conventions/snackmagic-conventions.yml
  - type: DataModel
    url: data-model/snackmagic-data-model.yml
  - type: Conformance
    url: conformance/snackmagic-conformance.yml
  - type: Lifecycle
    url: lifecycle/snackmagic-lifecycle.yml
  - type: Sandbox
    url: sandbox/snackmagic-sandbox.yml
- aid: snackmagic:snackmagic-user-management-api
  name: SnackMagic User management API
  description: User related API endpoints
  humanURL: https://api.bystadium.com/api/v2/docs
  baseURL: https://api.bystadium.com/api/v2
  tags:
  - User Management
  tags_raw:
  - User management
  properties:
  - type: OpenAPI
    url: openapi/snackmagic-user-management-api-openapi.yml
  - type: ErrorCatalog
    url: errors/snackmagic-problem-types.yml
  - type: Conventions
    url: conventions/snackmagic-conventions.yml
  - type: DataModel
    url: data-model/snackmagic-data-model.yml
  - type: Conformance
    url: conformance/snackmagic-conformance.yml
  - type: Lifecycle
    url: lifecycle/snackmagic-lifecycle.yml
  - type: Sandbox
    url: sandbox/snackmagic-sandbox.yml
common:
- type: Plans
  url: plans/snackmagic-plans-pricing.yml
- url: https://www.snackmagic.com:443/blog/
  type: Blog
- url: https://www.snackmagic.com/blog/feed/
  type: BlogRSS
- type: CapabilityMap
  url: capabilities/snackmagic-capability-edges.yml
  name: SnackMagic Business Capability Map
- type: X-MCPServerCandidate
  url: mcp/snackmagic-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/snackmagic-stadium-overlay.yaml
- type: Website
  url: https://snackmagic.com
- type: DeveloperPortal
  url: https://www.bystadium.com/api-integrations
- type: Documentation
  url: https://api.bystadium.com/api/v2/docs
- type: APIReference
  url: https://api.bystadium.com/api/v2/docs
- type: GettingStarted
  url: https://www.bystadium.com/api-integrations
- type: Authentication
  url: authentication/snackmagic-authentication.yml
- type: AgenticAccess
  url: agentic-access/snackmagic-agentic-access.yml
- type: LLMsTxt
  url: llms/snackmagic-llms.txt
- type: DomainSecurity
  url: security/snackmagic-domain-security.yml
- type: TrustCenter
  url: https://trust.bystadium.com
- type: StatusPage
  url: https://status.bystadium.com
- type: AgentSkill
  url: skills/_index.yml
- type: Pricing
  url: https://www.bystadium.com/go/pricing
- type: SignUp
  url: https://www.bystadium.com/
- type: TermsOfService
  url: https://www.bystadium.com/terms-of-use
- type: PrivacyPolicy
  url: https://www.bystadium.com/privacy-policy
- type: Blog
  url: https://www.bystadium.com/blog
- type: Support
  url: https://help.bystadium.com/hc
- type: GitHubOrganization
  url: https://github.com/snackmagic
- type: Wallet
  url: https://www.bystadium.com/wallet
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 17
  pass: local-v1

SnackMagic API — frequently asked questions

Does SnackMagic have an API?

Yes. APIs.io lists 5 APIs from SnackMagic, including SnackMagic Authentication API, SnackMagic Automation management API and SnackMagic Order management API, and 2 more.

Is there an OpenAPI specification for the SnackMagic API?

Yes. APIs.io indexes 5 OpenAPI specifications for SnackMagic, each linked for download from this page.

How do I authenticate with the SnackMagic API?

SnackMagic uses bearer-token authentication (http/apiKey/oauth2 · 2 schemes). The details are profiled on APIs.io as Snackmagic Authentication.

How much does the SnackMagic API cost?

SnackMagic publishes its prices; its Pay-As-You-Go plan is No pass needed as of 2026-10-28. APIs.io lists 5 pricing plans for SnackMagic, with each plan's price, limits and inclusions under Pricing on this page.

Is the SnackMagic API ready for AI agents?

SnackMagic has a Kin Score of 54.6 out of 100 (strong) and an Agent Readiness score of 27.0 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/snackmagic"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/snackmagic/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/snackmagic/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.