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

The Metadata API from Unlock Protocol — 4 operation(s) for metadata.

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

This API exposes 7 operations across 4 paths, and defines 6 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.

7 operations 4 paths 6 schemas 3 GET4 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 Metadata 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 7

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

Metadata 7
GET
/v2/api/metadata/{network}/locks/{lockAddress}
Get metadata for lock address.
lockMetadata 2 params → 200404500
PUT
/v2/api/metadata/{network}/locks/{lockAddress}
Update or create metadata for lock address.
updateLockMetadata 2 params body → 201204404500
GET
/v2/api/metadata/{network}/locks/{lockAddress}/keys/{keyId}
Get key and user metadata.
keyMetadata 3 params → 200
PUT
/v2/api/metadata/{network}/locks/{lockAddress}/keys/{keyId}
Update or create metadata for key.
updateKeyMetadata 3 params body → 201403404500
PUT
/v2/api/metadata/{network}/locks/{lockAddress}/users/{userAddress}
Update or create user metadata for lock.
updateUserMetadata 3 params body → 204400401404409500
GET
/v2/api/metadata/{network}/locks/{lockAddress}/users/{userAddress}
get user metadata for a lock.
getUserMetadata 2 params → 200401404500
PUT
/v2/api/metadata/users
Update or create user metadata for lock.
updateUsersMetadata body → 201400404500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are UserMetadata (4 properties), UserMetadataInput (2 properties), GenericInvalidBodyError (2 properties), GenericNotFound (1 property). Each schema is shown below with its type and property counts.

GenericInvalidBodyError
object
2 properties
GenericServerError
object
1 property
UserMetadata
object
4 properties 4 required
NotAuthenticated
object
1 property
UserMetadataInput
object
2 properties
GenericNotFound
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unlock-protocol-metadata-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 Metadata 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.