Authentication
Every request to pipe0 needs an API key, sent as a bearer token. A free account is enough to get started: sandbox requests cost nothing, and every new organization starts with 20 free credits for production requests. After those, production requests need a credit balance; see Billing.
Create an API key
Log in to your account.
Select "Organization" in the sidebar. API keys are organization credentials, managed by organization admins.
Scroll to the "API keys" section.
Click "New".
Send an authenticated request
Pass the key in the Authorization header:
curl -X POST "https://api.pipe0.com/v1/pipes/run/sync" \
-H "Authorization: Bearer <API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"pipes": [{ "pipe_id": "person:name:split@1" }],
"input": [{ "id": "1", "name": "Jane Doe" }]
}'Don't store API keys in the browser. Connect browser-based apps to pipe0 through a server or serverless function that can store keys securely.
Public keys
One pipe0 endpoint takes a different key. Autocomplete resolves the values a config field accepts, and it runs on a pk_ public key that authorizes nothing. That key is safe in a browser. Your API key is not.