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.

42.6/100 developing ▬ flat Agent 17/100 agent aware Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
AccessSelf serve
2 APIs 1 MCP Servers
CompanyTicketingAccess ControlEventDeveloper PlatformSDKSportsArts and CultureAustria

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 42.6/100 · developing
Contract Quality 14.9 / 25
Developer Ergonomics 12.3 / 20
Access Clarity 5.5 / 20
Operational Transparency 0.3 / 13
Contract Governance 2.0 / 12
Discoverability 7.6 / 10
Agent readiness — 17/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. 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. Want it done for you? Prioritized profiling — $2,500 →

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

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Keyper MCP Server

MCP SERVER

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
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  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: MCPServer
  url: mcp/keyper-mcp.yml
- 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