Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Howler website screenshot

Howler

Howler is a South African event technology platform that consolidates ticketing, RFID cashless payments, and vendor and access-control management into a single system for event organisers and attendees. Founded out of the Barclays Accelerator powered by Techstars (2017) and Techstars-backed, Howler has processed over R1.5 billion in transactions across thousands of events. Its public Howler API v3 consumer portal exposes 67 operations for authentication (OAuth2, JWT, email OTP, third-party OAuth), tickets (buy, assign, transfer), cashless RFID tags, top-ups, and cashout to bank accounts, and a Howler Webhooks v1 surface pushes ticket, event, and payment events to partner endpoints.

agent native

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Howler the way a machine reads it — 22 machine-readable artifacts across 17 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Howler scores 47.6/100 (developing), with a separate agent-readiness read of 75/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 47.6/100 · developing
Contract Quality 13.9 / 25
Developer Ergonomics 10.9 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 1.0 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Regulatory · Payments 11.4 / 15
Agent readiness — 75/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3

How we profile Howler

Each block below is one kind of artifact we hold for Howler. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 17

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

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

Howler Artists API

The Artists API from Howler — 1 operation(s) for artists.

Howler Assign Ticket API

The Assign Ticket API from Howler — 1 operation(s) for assign ticket.

Howler Bank Account API

The Bank Account API from Howler — 3 operation(s) for bank account.

Howler Basic Authentication API

The Basic Authentication API from Howler — 4 operation(s) for basic authentication.

Howler Cashless Tags API

The Cashless Tags API from Howler — 2 operation(s) for cashless tags.

Howler Cashout API

The Cashout API from Howler — 4 operation(s) for cashout.

Howler Email OTP API

The Email OTP API from Howler — 2 operation(s) for email otp.

Howler Events API

The Events API from Howler — 2 operation(s) for events.

Howler OAuth API

The OAuth API from Howler — 4 operation(s) for oauth.

Howler Third Party OAuth API

The Third Party OAuth API from Howler — 5 operation(s) for third party oauth.

Howler Tickets API

The Tickets API from Howler — 7 operation(s) for tickets.

Howler Top Up API

The Top Up API from Howler — 1 operation(s) for top up.

Howler Top Up Cashless Tag API

The Top Up Cashless Tag API from Howler — 7 operation(s) for top up cashless tag.

Howler Top Up Ticket API

The Top Up Ticket API from Howler — 7 operation(s) for top up ticket.

Howler Topupables API

The Topupables API from Howler — 1 operation(s) for topupables.

Howler Transfer Ticket API

The Transfer Ticket API from Howler — 2 operation(s) for transfer ticket.

Howler User API

The User API from Howler — 4 operation(s) for user.

Scroll within the panel for all 17 ·

MCP Servers 1

Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.

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

howler-mcp.yml

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Howler Authentication

apiKey/http/oauth2 · 5 schemes

SECURITY

Howler Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.

OAuth scopes governing access to this provider's APIs.

Howler Scopes

3 scopes · authorizationCode

3 scopes

SCOPES

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

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

Howler Agentic Access

67 operations · 37 acting · 2 human-in-the-loop

67 operations · 37 acting

AGENTIC

Resources

Every other property we hold for Howler — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Get Started 3

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Access & Security 3

Authentication, authorization, and security posture

Operate 2

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

← All providers · Data indexed from github.com/api-evangelist/howler · machine-readable index on apis.io