Skip to main content
Convexity Infra is a suite of backend services that let your business build and operate blockchain-enabled products, without standing up your own chain nodes, custody, or payment rails. You integrate these APIs into your own application, and Convexity runs the infrastructure behind them. Its core services are Wallet Infra (provision HD wallets, sign and broadcast transactions, and move value), Tokenization (issue tokenized assets and run mint, burn, transfer, and yield operations), and Blockchain Events (stream decoded on-chain events to your webhooks). Around them sit the supporting services (authentication, payments, products, and subscriptions) that get you authorized and billed. All services share one set of conventions: a single OAuth 2.0 bearer token, a consistent JSON response envelope, uniform pagination, and a common error model. Learn those once and every endpoint behaves the same way.
Base URLThe base URL is https://dev.api.withconvexity.com. Every path in this reference is relative to that host.

​
Core services

Wallet Infra

HD wallet lifecycle, balances, transfers, signing, and chain discovery.

Tokenization

Issue tokenized assets: mint, burn, transfer, and run yield operations.

Blockchain Events

Subscribe to decoded on-chain events and inspect webhook delivery logs.

​
Supporting services

Auth-Edge

Exchange an API key for a short-lived OAuth 2.0 access token.

Projects

Rotate your project’s API keys and manage its IP allowlist.

Payments

List payments and mint deposit accounts for top-ups and subscriptions.

Products

Browse the products and capabilities available to your project.

Subscriptions

List plans and manage your project’s subscriptions.

​
Quick start

The Quickstart walks these steps with runnable requests, from API key to a funded project in about five minutes.
1

Register for an API key

There’s no self-service signup: email infra@withconvexity.com with your business details to receive a test key and a live (sk_live_...) key.
2

Get an access token

Exchange your live API key for a bearer token via the Generate Token endpoint.
3

Call an endpoint

Send the token as Authorization: Bearer <access_token> on every request. See Authentication for the full flow.
4

Read the response envelope

Every response is wrapped in a { status, message, data } envelope. See Conventions.
5

Handle errors uniformly

Errors share a single shape across all services. See Errors.

​
How requests are authorized

Tokens are minted by Auth-Edge from a project API key and carry the project and business context plus a set of scopes and capabilities. Endpoints check those claims before serving a request:
  • Live vs. test keys: Most business endpoints reject test tokens with 403. Use your sk_live_... key for production traffic.
  • Project context: Blockchain Events endpoints require a token bound to a project and business.
  • Capabilities: Fine-grained permissions (for example indexer.subscribe.evm) gate individual operations. A missing capability returns 403.
Read Authentication before integrating.