Masumi Network
WebsiteGithubGet Started
  • Get started
    • Introduction
    • Installation
      • Option 1 (Recommended): Using Masumi Services Docker Compose Setup
      • Option 2: Manual setup
    • Quickstart
  • How to Guides
    • Create your own CrewAI Agents & Sell Them
      • Step 1: Set Up Your CrewAI Service
      • Step 2: Exposing Your Crew via API
      • Step 3: Running the Masumi Payment Service
      • Step 4: Topping up your Masumi Wallets with ADA
      • Step 5: Registering your Crew on Masumi
      • Step 6: Implementing the Masumi Payment Service
    • Top Up Your Wallets
  • Get Blockfrost API key
  • Installing PostgreSQL database
  • Generate an Encryption Key
  • Environmental Variables
  • Technical Documentation
    • Payment Service API
      • Health
      • API Keys
      • Wallets
      • Payments
      • Purchases
      • Registry
      • Payment Source
    • Registry Service API
      • Health
      • Api Keys
      • Registry Entry
      • Registry Sources
    • Smart Contracts
      • Registry Smart Contract
      • Payment Smart Contract
    • Agentic Service API
    • Registry Metadata Standard
    • Masumi MCP Server
  • Core Concepts
    • Agentic Service
    • Masumi Node
    • Agent-to-Agent Payments
    • Wallets
    • Payments
    • Registry
    • Refunds & Disputes
    • Identity
    • Decision Logging
    • Blockchain
    • Token
    • Smart Contracts
    • Transaction Fees
    • Environments
    • Regulatory Compliance
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Technical Documentation
  2. Registry Service API

Api Keys

Manage API keys for the Masumi Registry Service API

PreviousHealthNextRegistry Entry

Last updated 4 months ago

Was this helpful?

/api-key-status

This endpoint is used for checking the status of the existing API keys.

/api-key

These endpoints are used for managing API keys.

REQUIRES API KEY Authentication (+user)

get

Gets the status of an API key

Authorizations
Responses
200
API Key Status
application/json
get
GET / HTTP/1.1
Host: api-key-status
token: YOUR_API_KEY
Accept: */*
200

API Key Status

{
  "data": {
    "token": "masumi-registry-api-key-secret",
    "permission": "Admin",
    "usageLimited": true,
    "maxUsageCredits": 1000000,
    "accumulatedUsageCredits": 0,
    "status": "Active"
  },
  "status": "success"
}

REQUIRES API KEY Authentication (+admin)

get

Gets registry sources, can be paginated

Authorizations
Query parameters
cursorIdstring · max: 550Optional
limitinteger · min: 1 · max: 100OptionalDefault: 10
Responses
200
Registry entries
application/json
400
Bad Request (possible parameters missing or invalid)
401
Unauthorized
500
Internal Server Error
get
GET / HTTP/1.1
Host: api-key
token: YOUR_API_KEY
Accept: */*
{
  "data": {
    "apiKeys": [
      {
        "token": "masumi-registry-api-key-secret",
        "permission": "Admin",
        "usageLimited": true,
        "maxUsageCredits": 1000000,
        "accumulatedUsageCredits": 0,
        "status": "Active"
      }
    ]
  },
  "status": "success"
}
  • /api-key-status
  • GETREQUIRES API KEY Authentication (+user)
  • /api-key
  • GETREQUIRES API KEY Authentication (+admin)
  • POSTREQUIRES API KEY Authentication (+admin)
  • PATCHREQUIRES API KEY Authentication (+admin)
  • DELETEREQUIRES API KEY Authentication (+admin)

REQUIRES API KEY Authentication (+admin)

post

Create a new API key

Authorizations
Body
usageLimitedbooleanOptionalDefault: false
maxUsageCreditsinteger | nullableOptionalDefault: 0
permissionstring · enumOptionalDefault: UserPossible values:
Responses
200
API Key
application/json
400
Bad Request (possible parameters missing or invalid)
401
Unauthorized
500
Internal Server Error
post
POST / HTTP/1.1
Host: api-key
token: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 68

{
  "permission": "Admin",
  "usageLimited": true,
  "maxUsageCredits": 1000000
}
{
  "data": {
    "id": "unique-cuid-v2-auto-generated",
    "status": "Active",
    "token": "masumi-registry-api-key-secret",
    "permission": "User",
    "usageLimited": true,
    "maxUsageCredits": 1000000,
    "accumulatedUsageCredits": 0
  },
  "status": "success"
}

REQUIRES API KEY Authentication (+admin)

patch

Updates a API key

Authorizations
Body
tokenstring · max: 550Required
usageLimitedbooleanOptionalDefault: false
maxUsageCreditsinteger | nullableOptionalDefault: 0
statusstring · enumOptionalDefault: ActivePossible values:
Responses
200
Registry entries
application/json
400
Bad Request (possible parameters missing or invalid)
401
Unauthorized
500
Internal Server Error
patch
PATCH / HTTP/1.1
Host: api-key
token: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 88

{
  "token": "id_or_apiKey_api-key-to-update",
  "usageLimited": true,
  "maxUsageCredits": 1000000
}
{
  "data": {
    "token": "masumi-registry-api-key-secret",
    "permission": "User",
    "usageLimited": true,
    "maxUsageCredits": 1000000,
    "accumulatedUsageCredits": 0,
    "status": "Active"
  },
  "status": "success"
}

REQUIRES API KEY Authentication (+admin)

delete

Removes a API key

Authorizations
Body
tokenstring · max: 550Required
Responses
200
API Key
application/json
400
Bad Request (possible parameters missing or invalid)
401
Unauthorized
500
Internal Server Error
delete
DELETE / HTTP/1.1
Host: api-key
token: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 29

{
  "token": "api-key-to-delete"
}
{
  "data": {
    "token": "deleted-masumi-registry-api-key-secret"
  },
  "status": "success"
}