How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Unlock Protocol Ticket API

The Ticket API from Unlock Protocol — 9 operation(s) for ticket.

Unlock Protocol Ticket API is one of 34 APIs that Unlock Protocol publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 9 operations across 9 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.

Requests are made against 2 base URLs: https://locksmith.unlock-protocol.com, https://staging-locksmith.unlock-protocol.com.

9 operations 9 paths 4 schemas 6 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2
Base URL
https://locksmith.unlock-protocol.com
Authentication
HTTP Bearer, API Key
License
MIT
Resource Areas
1

Authentication & Security 2

Unlock Protocol Ticket API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (User). An API key is passed in the query as api-key (Application).

Paths & Operations 9

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

Ticket 9
GET
/v2/api/ticket/{network}/{lockAddress}/{keyId}/sign
Sign ticket
signTicket 3 params → 200403404500
PUT
/v2/api/ticket/{network}/lock/{lockAddress}/key/{keyId}/checkdeprecated
Check ticket
checkTicket 3 params → 202403404409500
PUT
/v2/api/ticket/{slug}/{network}/lock/{lockAddress}/key/{keyId}/check
Check event ticket
checkEventTicket 4 params → 202403404409500
GET
/v2/api/ticket/{slug}/{network}/lock/{lockAddress}/key/{keyId}
Get event ticket
getEventTicket 4 params → 200401
POST
/v2/api/ticket/{network}/{lockAddress}/{keyId}/email
Email ticket
emailTicket 3 params → 200403404500
GET
/v2/api/ticket/{network}/{lockAddress}/{keyId}/qr
Ticket QR code
ticketQRCode 3 params → 200403404500
GET
/v2/api/ticket/{network}/{lockAddress}/{keyId}/verification
Ticket verification url
ticketVerificationUrl 3 params → 200403404500
GET
/v2/api/ticket/{network}/lock/{lockAddress}/key/{keyId}/generate
Generate ticket
generateTicket 3 params → 200401
GET
/v2/api/ticket/{network}/lock/{lockAddress}/key/{keyId}
Get ticket
getTicket 3 params → 200401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are NotAuthenticated (1 property), GenericSuccess (1 property), GenericServerError (1 property), GenericNotFound (1 property). Each schema is shown below with its type and property counts.

GenericNotFound
object
1 property
GenericServerError
object
1 property
GenericSuccess
object
1 property
NotAuthenticated
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unlock-protocol-ticket-api-openapi.yml Raw ↑

Other APIs Unlock Protocol publishes across the network.

Unlock Subgraphs (GraphQL)
Unlock Protocol Applications API
Unlock Protocol Auth API
Unlock Protocol Captcha API
Unlock Protocol Certificate API
Unlock Protocol Charges API
Unlock Protocol Checkout API
Unlock Protocol Claim API
Unlock Protocol Contracts API
Unlock Protocol Credit Card Details API
Unlock Protocol Email API
Unlock Protocol Email Subscriptions API
Where this information came from

This is an independent, third-party profile of Unlock Protocol Ticket API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.