Skip to main content

​
Overview

The OpenAPI spec in this site is generated from the Supabase edge-function source in this repo. It currently documents the public Token Layer REST surface, including:
  • token discovery and pricing
  • Token Layer action execution
  • fees, referrals, portfolio, and leaderboard reads
  • social and hub endpoints used by the app
  • user, notification, and search endpoints

​
Base URL

https://api.tokenlayer.network/functions/v1
Testnet base URL: 
https://api-testnet.tokenlayer.network/functions/v1

​
Authentication

Authentication depends on the route. Common patterns are: 
Authorization: Bearer <API_KEY_OR_JWT>
  • many info reads are public
  • account-bound reads and actions require API key or JWT auth
  • selected action flows also support wallet signing through the SDK and CLI

​
Core endpoints

  • POST /info consolidates typed read operations behind a discriminated request union
  • POST /token-layer executes typed protocol actions
  • other routes expose direct endpoint-specific operations such as /me, /search-token, and /get-pool-data
Browse the generated endpoint pages in the navigation.

Info Endpoint

Typed read operations through POST /info

Token Layer Actions

Execute actions through POST /token-layer

SDK

Typed TypeScript client

CLI

Scriptable Rust command surface

​
Source of truth

The canonical spec file is api-docs/openapi.yaml, generated by: 
npm run generate-openapi