v1.0 Beta

CapSign API

Build with tokenized securities. The CapSign API provides programmatic access to wallets, tokens, offerings, and compliance tools—all on Base (Ethereum L2).

Smart Wallets
ERC-4337
Tokens
Equity · Debt · SAFE
Compliance
SEC Reg D
Network
Base L2

Authentication

All API requests require authentication using an API key. Include your key in theAuthorizationheader as a Bearer token.

curl -X GET https://capsign.com/api/v1/wallets \
  -H "Authorization: Bearer csk_live_your_api_key" \
  -H "Content-Type: application/json"
⚠️

Keep your API keys secure

Never expose API keys in client-side code. Use environment variables and server-side requests.

Rate Limits

API requests are rate-limited based on your subscription tier. Rate limit headers are included in every response.

TierRequests/hourMonthly LimitPrice
Free1001,000$0
Starter1,00050,000$49/mo
Growth5,000500,000$199/mo
EnterpriseCustomUnlimitedCustom

Rate Limit Headers

X-RateLimit-Limit:Maximum requests allowed
X-RateLimit-Remaining:Requests remaining in window
X-RateLimit-Reset:Unix timestamp when limit resets

Errors

The API uses conventional HTTP response codes. Errors return a JSON object with details.

{
  "error": "Invalid API key provided",
  "code": "unauthorized",
  "requestId": "req_abc123"
}
400Bad RequestInvalid request parameters
401UnauthorizedMissing or invalid API key
403ForbiddenValid key but insufficient permissions
404Not FoundResource does not exist
429Rate LimitedToo many requests
500Server ErrorSomething went wrong on our end

Getting Started

Basic API endpoints for health checks and status

Wallets

Create and manage smart contract wallets

Tokens

Create and manage securities tokens

Offerings

Create and manage securities offerings

Webhooks

Configure webhook endpoints for event notifications

API Keys

Manage API keys (requires session authentication)

OpenAPI Specification

Download the complete OpenAPI 3.1 specification for use with your favorite API tools.

API Reference | CapSign