API & Developers
Everything the dashboard does, your systems can do.
Flowyte is API-first. Describe an agent in the studio today, script the same agent from your own stack tomorrow — create it, feed it knowledge, publish it, and hear about every call the moment it ends. No separate "developer product," no second agent to maintain.
Free credits included. No credit card required.
POST /api/v1/agents
curl -X POST https://api.flowyte.com/api/v1/agents \
-H "Authorization: Bearer $FLOWYTE_SK_LIVE" \
-H "Content-Type: application/json" \
-d '{
"name": "Front desk",
"persona": "Warm, direct, never quotes exact prices",
"skills": ["book_calendar"]
}'Illustrative example — see the API docs for the live contract.
For owners
You don't have to touch it. It just means you're never boxed in.
Most owners build their agent by describing it in plain English and never open the API. It matters anyway: an agent your systems can talk to is an agent that grows with the business instead of becoming the next thing you replace.
One agent, two ways to build it
Owners describe the agent in plain English. Developers script the same agent through the same API — which means the person who knows the business and the person who runs your systems are never working on two different products.
Your systems find out first
Signed webhooks fire the moment a call completes, transfers, or a new version goes live — which means your follow-up can start while the caller’s phone is still warm, in whatever tools you already run.
No integration ceiling
Google Calendar and Google Sheets are built in, and everything else connects through secure OAuth, webhooks, and the API — which means adding Flowyte never means replacing what already works.
“The same /api/v1 your dashboard uses.”
For developers
The parts you actually check before you commit.
Scoped keys, shown once
Mint separate test and live keys, scoped to what each one is allowed to do. The secret is displayed exactly once at creation — copy it or mint again — and every key can be rotated or revoked without touching the others.
Scripted demo — a replay of the real product, not a live session.
A self-describing OpenAPI surface
The API describes itself in OpenAPI, so your tooling can explore endpoints and generate clients instead of transcribing docs by hand. Agents, knowledge, Skills, publishing, numbers, webhooks — if the dashboard can do it, there is an operation for it.
Start at docs.flowyte.com or the API tutorial.
Signed webhooks with a delivery log
Subscribe with an event multiselect, verify signatures on your end, send a test delivery before anything real depends on it, and audit every attempt in the delivery log when something looks off.
- agent.published
- call.completed
- call.transferred
- number.purchased
- knowledge.indexed
Create an agent in one request
The same create flow the studio's describe-to-build runs, callable from anywhere:
# Example only — see docs.flowyte.com for the full reference
curl -X POST https://api.flowyte.com/api/v1/agents \
-H "Authorization: Bearer $FLOWYTE_SK_LIVE" \
-H "Content-Type: application/json" \
-d '{
"name": "Front desk",
"description": "Answers, books, and routes for a home-services company"
}'Illustrative example — request shapes and the current endpoint reference live in the API docs.
Where the API meets the rest of the platform
FAQ
Frequently asked questions
Does Flowyte have a public API?
How does API authentication work?
What webhook events can I subscribe to?
Do I need to write code to use Flowyte?
Can I connect Flowyte to the tools I already use?
What does API usage cost?
Build it by describing it. Script it when you're ready.
Start in the studio today — the API will be waiting with the same agent when your systems want in.
Free credits included. No credit card required.