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 Event Collection API

The Event Collection API from Unlock Protocol — 9 operation(s) for event collection.

Unlock Protocol Event Collection 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 Event Collection. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

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

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

13 operations 9 paths 16 schemas 3 DELETE4 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.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 Event Collection 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 13

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

Event Collection 13
POST
/v2/event-collection
Create a new event collection
createEventCollection body → 201400500
GET
/v2/event-collection/{slug}
Get details of an event collection
getEventCollection 1 param → 200404500
PUT
/v2/event-collection/{slug}
Update an existing event collection
updateEventCollection 1 param body → 200403404500
POST
/v2/event-collection/{slug}/events
Add an event to a collection
addEventToCollection 1 param body → 200400404500
GET
/v2/event-collection/{slug}/events
Get events in a collection
getEventsInCollection 3 params → 200404500
DELETE
/v2/event-collection/{slug}/events
Remove a single event from an event collection.
removeEventFromCollection 1 param body → 200400403404500
POST
/v2/event-collection/{slug}/managers
Add a new manager address to an event collection
addManagerToEventCollection 1 param body → 200400401403404500
DELETE
/v2/event-collection/{slug}/managers
Remove a manager address from an event collection
removeManagerFromEventCollection 1 param body → 200400401403404500
GET
/v2/event-collection/{slug}/unapproved-events
Get unapproved events for a collection
getUnapprovedEventsForCollection 1 param → 200400401403404500
POST
/v2/event-collection/{slug}/events/approve
Approve a single event within an event collection.
approveEvent 1 param body → 200400403404500
POST
/v2/event-collection/{slug}/events/bulk-approve
Bulk approve multiple events within an event collection.
bulkApproveEvents 1 param body → 200400403404500
DELETE
/v2/event-collection/{slug}/events/bulk-remove
Bulk remove multiple events from an event collection.
bulkRemoveEvents 1 param body → 200400403404500
GET
/v2/event-collection/by-manager/{managerAddress}
Get all event collections managed by a specific address
getEventCollectionsByManager 1 param → 200404500

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are EventCollection (10 properties), Event (8 properties), EventCollectionAssociation (6 properties), EventCollectionBody (6 properties). Each schema is shown below with its type and property counts.

GenericInvalidBodyError
object
2 properties
AddManagerBody
object
1 property 1 required
GenericServerError
object
1 property
BulkRemoveEventsBody
object
1 property 1 required
GenericNotFound
object
1 property
EventCollectionBody
object
6 properties 3 required
Event
object
8 properties 5 required
NotAuthenticated
object
1 property
BulkApproveEventsBody
object
1 property 1 required
RemoveManagerBody
object
1 property 1 required
EventCollection
object
10 properties
EventsInCollection
object
4 properties
RemoveEventBody
object
1 property 1 required
ApproveEventBody
object
1 property 1 required
AddEventToCollectionBody
object
1 property 1 required
EventCollectionAssociation
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unlock-protocol-event-collection-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 Event Collection 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.