Skip to main content
The Netter public API lets you push data into your workspace programmatically. Today it exposes a single endpoint—file upload—authenticated with an API key.

​
Base URL

Partners that allowlist outbound traffic by IP can use the static-IP host instead.

​
Authentication

Send your API key as a bearer token:
Every key starts with the ntr_ prefix and is tied to the user and company it was created in. See API keys to create and manage them.

​
Connecting from an IP-allowlisted network

If your network or partner only allows outbound calls to a fixed set of IPs, send requests to the dedicated ingest host instead of api.netter.ai. It routes to the same API through two static IP addresses that never change:
Add both IPs to your firewall allowlist. Identity still comes from your API key, so the same key works against either host—no per-partner DNS or certificate changes are needed.
api.netter.ai and ingest.netter.ai serve the identical API. Use ingest.netter.ai only when you need the fixed IPs for allowlisting.