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 User API

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

Howler User API is one of 17 APIs that Howler publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 7 operations across 4 paths, and defines 1 schema. It is described by OpenAPI 3.1.0, at version 3.6.1.

Requests are made against a single base URL, https://{defaultHost}/api/v3/consumer_portal.

7 operations 4 paths 1 schemas 1 DELETE3 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
3.6.1
Base URL
https://www.howler.co.za/api/v3/consumer_portal
Authentication
OAuth 2.0, HTTP Bearer, API Key, HTTP Bearer, API Key, HTTP Basic, API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 8

Howler User API declares 8 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 3 scopes. It accepts HTTP bearer tokens (oauth2) (bearer_header). An API key is passed in the query as bearer_token (bearer_param). It accepts HTTP bearer tokens (JWT) (jwt_header). An API key is passed in the query as bearer_token (jwt_param). It accepts HTTP basic authentication (basic_auth). An API key is passed in the header as x-auth-token (api_key). It accepts HTTP bearer tokens (JWT) (bearer_auth). By default, every request must be authenticated.

  • oauth2 — OAuth2 authentication for third-party applications
  • jwt_header — JWT token obtained from basic authentication login
  • jwt_param — JWT token as query parameter (alternative to Authorization header)
  • basic_auth — Basic authentication with email and password
  • api_key — API key authentication
  • bearer_auth — JWT token authentication

Paths & Operations 7

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

User 7
DELETE
/user
request user account deletion
requestUserDeletion → 204
GET
/user
get user details
getConsumerUser → 200
PUT
/user
update user details
updateConsumerUser body → 200422
GET
/events/{event_id}/user/setup
check if user is setup for event
updateConsumerUserIsSetup 1 param → 200
POST
/user/resend_confirmation
resend user confirmation email
resendUserConfirmation → 200
GET
/user/web
input user details on a rendered form
editConsumerUserWeb → 200
PUT
/user/web
update user details from a rendered form
updateConsumerUserWeb body → 303200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is UserDetails (37 properties). Each schema is shown below with its type and property counts.

UserDetails
object
37 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

howler-user-api-openapi.yml Raw ↑

Other APIs Howler publishes across the network.

Howler Artists API
Howler Assign Ticket API
Howler Bank Account API
Howler Basic Authentication API
Howler Cashless Tags API
Howler Cashout API
Howler Email OTP API
Howler Events API
Howler OAuth API
Howler Third Party OAuth API
Howler Tickets API
Howler Top Up API