Skip to main content
The Natural API is a REST API over HTTPS — JSON request and response bodies, Bearer-token authentication, one base URL: https://api.natural.co.
Most integrations should not start with raw REST. Want Claude or ChatGPT to send payments for you, no code? Use the MCP server. Building an app or service — including a Python or TypeScript backend? Use an SDK. Working from a terminal, CI job, or command-capable coding-agent harness? Use the CLI. Reach for the REST API directly only when no SDK covers your language or you need request-level control. Choosing your integration →

​
When to call the REST API directly

Use the REST API directly when:
  • You’re on a language with no official SDK — the SDKs cover Python and TypeScript.
  • You need request-level control the SDKs don’t expose.
  • You’re exploring or debugging with curl.
For most integrations an SDK or the MCP server is faster. The SDKs give typed requests with automatic retries and pagination; the MCP server’s tools go further and absorb orchestration like wallet resolution and payer-kind detection.

​
Making a request

Every request carries an API key in the Authorization header: 
curl https://api.natural.co/payments \
  -H "Authorization: Bearer sk_ntl_prod_..."
Requests and responses follow a JSON:API structure — see About the API. Authenticate with API keys; the same key works across the SDKs, the CLI, and MCP fallback paths.

​
Reference

The full endpoint reference is auto-generated from the OpenAPI spec — see API Reference. The raw spec, for code generation and tooling, is at openapi.json.
  • SDKs — Python and TypeScript client libraries
  • MCP — Connect Claude, Cursor, and other AI hosts to Natural
  • CLI — For terminal and CI use
  • Authentication — API keys: format, scopes, security