Keyper website screenshot

Keyper

keyper is an Austrian technology company providing connected ticketing and digital access solutions. Its developer platform lets ticketing systems, resellers and access control systems (ACS) deliver e-tickets and exchange access data through the keyper Access API, Connect Provider / Reseller APIs, Ticket Delivery API, native Android and iOS SDKs, and embeddable web components (seatmaps and checkout). The Access API sends entry transactions for keys (ticket barcodes) and their permissions (events), and returns the Grant / Block permission whitelist an access control system enforces at the gate. keyper serves sports, arts and culture organisations across Austria and Central Europe and is backed by Speedinvest.

Keyper publishes 2 APIs on the APIs.io network: Permissions API and Transactions API. Tagged areas include Company, Ticketing, Access Control, Event, and Developer Platform.

Keyper’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, sandbox, and 16 more developer resources.

31.5/100 thin ▬ flat Agent 19/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
CompanyTicketingAccess ControlEventDeveloper PlatformSDKSportsArts and CultureAustria

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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.
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 github.com/api-evangelist/keyper: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

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

Keyper Permissions API

Retrieve the permission whitelist / blacklist for an Access Control System.

Keyper Transactions API

Send access / entry transactions to keyper.

Open Collections 3

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

API Collection

OPEN COLLECTION

Security Posture 2

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

Keyper Authentication

apiKey · 1 scheme

SECURITY

Keyper Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 1

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: keyper
name: Keyper
description: keyper is an Austrian technology company providing connected ticketing and digital access solutions. Its developer
  platform lets ticketing systems, resellers and access control systems (ACS) deliver e-tickets and exchange access data through
  the keyper Access API, Connect Provider / Reseller APIs, Ticket Delivery API, native Android and iOS SDKs, and embeddable
  web components (seatmaps and checkout). The Access API sends entry transactions for keys (ticket barcodes) and their permissions
  (events), and returns the Grant / Block permission whitelist an access control system enforces at the gate. keyper serves
  sports, arts and culture organisations across Austria and Central Europe and is backed by Speedinvest.
url: https://raw.githubusercontent.com/api-evangelist/keyper/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- speedinvest
x-tier: profiled
x-tier-reason: portfolio-lead
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://www.keyper.com/wp-content/uploads/keyper-logo.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Ticketing
- Access Control
- Event
- Developer Platform
- SDK
- Sports
- Arts and Culture
- Austria
tags_raw:
- Company
- Ticketing
- Access Control
- Events
- Developer Platform
- SDK
- Sports
- Arts and Culture
- Austria
apis:
- aid: keyper:keyper-permissions-api
  name: Keyper Permissions API
  description: Retrieve the permission whitelist / blacklist for an Access Control System.
  humanURL: https://developers.keyper.com
  baseURL: https://api.keyper.io/access
  tags:
  - Permissions
  properties:
  - type: OpenAPI
    url: openapi/keyper-permissions-api-openapi.yml
  - type: APIBlueprint
    url: openapi/keyper-access.apib
  - type: Authentication
    url: authentication/keyper-authentication.yml
  - type: ErrorCatalog
    url: errors/keyper-error-codes.yml
  - type: Conventions
    url: conventions/keyper-conventions.yml
  - type: DataModel
    url: data-model/keyper-data-model.yml
  - type: Conformance
    url: conformance/keyper-conformance.yml
- aid: keyper:keyper-transactions-api
  name: Keyper Transactions API
  description: Send access / entry transactions to keyper.
  humanURL: https://developers.keyper.com
  baseURL: https://api.keyper.io/access
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/keyper-transactions-api-openapi.yml
  - type: APIBlueprint
    url: openapi/keyper-access.apib
  - type: Authentication
    url: authentication/keyper-authentication.yml
  - type: ErrorCatalog
    url: errors/keyper-error-codes.yml
  - type: Conventions
    url: conventions/keyper-conventions.yml
  - type: DataModel
    url: data-model/keyper-data-model.yml
  - type: Conformance
    url: conformance/keyper-conformance.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: X-MCPServerCandidate
  url: mcp/keyper-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/keyper-access-overlay.yaml
- type: DeveloperPortal
  url: https://developers.keyper.com
- type: Documentation
  url: https://developers.keyper.com
- type: APIReference
  url: https://developers.keyper.com
- type: GettingStarted
  url: https://developers.keyper.com
- type: Support
  url: https://support.keyper.com/developers/
- type: Blog
  url: https://www.keyper.com/news/
- type: GitHubOrganization
  url: https://github.com/keyper
- type: Login
  url: https://app.keyper.io/business/
- type: TermsOfService
  url: https://www.keyper.com/terms-and-conditions/
- type: PrivacyPolicy
  url: https://www.keyper.com/privacy-policy/
- type: Website
  url: https://www.keyper.com
- type: Packages
  url: packages/keyper-packages.yml
- type: SDKs
  url: packages/keyper-packages.yml
- type: Components
  url: components/keyper-components.yml
- type: Sandbox
  url: sandbox/keyper-sandbox.yml
- type: Lifecycle
  url: lifecycle/keyper-lifecycle.yml
- type: LLMsTxt
  url: llms/keyper-llms.txt
- type: WellKnown
  url: well-known/keyper-well-known.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/keyper-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

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/keyper"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/keyper/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/keyper/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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