“Show me the sales report” Handle backend APIs through conversation
Even backend APIs without a frontend — just hand the docs to wiiiv. Follow along as you query, filter, and chart your data through conversation.
Problem
Sound familiar?
Your company has backend APIs but no admin dashboard.
To check inventory, you have to open Postman, get a token, find the endpoint, make the call,
and read the JSON response by eye. To create a report, you then have to copy everything into a spreadsheet.
wiiiv replaces this entire process with conversation.
Register your API spec in Knowledge, and simply say "Show me low-stock products" —
wiiiv calls the right API and presents the results.
🙅
No Postman needed
No need to manually compose URLs, headers, and parameters.
📊
JSON → Table / Chart
Instantly converts API responses into human-readable formats.
🔗
Multi-API composition
Combines multiple endpoints in a single request to build the answer.
🛡
Auto authentication
Automatically handles token issuance and renewal. No need to log in every time.
Setup
Setup: Register your API docs
For wiiiv to call APIs, it first needs to know what endpoints are available.
Register your API spec in Knowledge and wiiiv will recognize it automatically.
What does an API document look like?
Register a document in this format. You can also convert your company's Swagger/OpenAPI docs to text.
Settings > Knowledge > File Upload. Supports .md, .txt, and .pdf formats. If the document contains 3 or more HTTP methods (GET/POST/PUT/DELETE) and a Base URL, wiiiv automatically recognizes it as an API document.
Once the API document is recognized, a card is automatically created in the Connections tab. Click the card to register your ID/Password, and wiiiv will handle authentication automatically.
3
Start using it in chat
You're all set! Now just say "Show me the skymall product list" and wiiiv will call the API.
The more detailed your API document is with endpoints, parameters, and response formats, the more accurately wiiiv calls them. A field-name mapping table reduces errors when combining data.
Try it
Call APIs through conversation
Once setup is complete, you can start right from the chat window.
You don't need to know how to call APIs. Just ask what you want to know.
Try it yourself
"Show me the list of products with stock of 5 or less, along with their supplier and unit cost."
wiiiv
Me
Skytree2:15 PM
Show me the list of products with stock of 5 or less, along with their supplier and unit cost.
wiiiv2:15 PM
I've retrieved the list of products with stock of 5 or less from SkyMall, along with supplier information from SkyStock.
📦 Low Stock Products (≤ 5)
7 rows · 4 cols
📋 CSV
Product Name ⇅
Stock ⇅
Supplier ⇅
Unit Cost ⇅
Sony WH-1000XM5
0
N/A
N/A
Apple AirPods Pro 2
3
N/A
N/A
Canon EOS R50
2
Global Fashion Co.
8,000
DJI Mini 4 Pro
1
N/A
N/A
iPad Pro 12.9
5
N/A
N/A
Patagonia Better Sweater
0
N/A
N/A
Peloton Bike+
3
N/A
N/A
⚙ Execution Summary — SkyMall GET /api/products/low-stock + SkyStock GET /api/suppliers matched
wiiiv automatically calls both the SkyMall and SkyStock APIs, matches products by ID,
and merges the results into a single table. Follow-up questions flow naturally:
Follow up
"From these, show me only the products with zero stock."
Category lookup
"Show me the skymall category list."
Conversation context is maintained. Saying "from these" filters based on the previous results. You don't need to explain from scratch every time.
Visualize
Turn data into charts
For numerical data, just add "show it as a chart."
wiiiv calls the API, aggregates the results, draws a graph, and saves it as an image.
Try it yourself
"Show me the top 5 best-selling products on skymall as a bar chart."
wiiiv
Me
Skytree2:18 PM
Show me the top 5 best-selling products on skymall as a bar chart.
wiiiv2:19 PM
I called the SkyMall best-sellers API and created a bar chart of the top 5 products by sales volume.
📊 SkyMall Best Sellers — Top 5
Canon EOS R50
156
Samsung TV 65"
132
Nike Air Max 90
108
MacBook Pro 14"
87
Dyson V15
64
📎 skymall-bestsellers-top5.png (saved)
⚙ Execution Summary — GET /api/products/best-sellers?size=5 → python3 matplotlib chart
You can also request other types of visualization through conversation:
Pie chart
"Can you show me the revenue share by category as a chart?"
Comprehensive report
"Create a table and chart showing product count, revenue, and low-stock items by category."
Analysis
Multi-turn analysis conversations
Real work doesn't end in a single turn.
You can keep the conversation going to dig deeper, like
"What were March sales?" → "Show me the big ones" → "Put this in a table."
wiiiv
Me
Skytree3:10 PM
How many orders were there in March this year, and what was the total revenue?
wiiiv3:11 PM
I've analyzed the March order data.
Total orders: 47 Total revenue: ₩18,450,000
Me
Skytree3:11 PM
Show me the ones with the largest order amounts. Top 5 or so.
wiiiv3:11 PM
Here are the top 5 highest-value orders in March.
💰 Top 5 Orders by Amount (March)
5 rows · 4 cols
📋 CSV
# ⇅
Product ⇅
Amount ⇅
Date ⇅
1
MacBook Pro 14"
₩2,590,000
3/12
2
Canon EOS R50
₩1,890,000
3/05
3
Samsung TV 65"
₩1,650,000
3/18
4
Dyson V15 Complete
₩1,290,000
3/22
5
LG gram 17"
₩1,190,000
3/28
⚙ Execution Summary — GET /api/orders?size=1000 → python3 filter + sort by totalAmount
Advanced
Cross-system analysis
When you register multiple API documents, you can work across multiple systems in a single conversation.
For example, handling both a shopping mall (SkyMall) and a supply chain (SkyStock) simultaneously:
wiiiv
Me
Skytree4:30 PM
Find products with stock of 5 or less on skymall, and check their supplier and fulfillment rate on skystock.
wiiiv4:31 PM
I've matched SkyMall low-stock products with SkyStock supplier performance. Some products are shown as N/A because they don't have a supplier mapping in SkyStock.
🔗 Cross-System: Low Stock × Supplier Performance
5 rows · 5 cols
📋 CSV
Product ⇅
Stock ⇅
Supplier ⇅
Fulfillment ⇅
Lead Time ⇅
Canon EOS R50
2
Canon Korea
94%
5d
DJI Mini 4 Pro
1
DJI Direct
91%
7d
Apple AirPods Pro 2
3
N/A
—
—
Peloton Bike+
3
N/A
—
—
iPad Pro 12.9
5
N/A
—
—
Canon Korea (94%) and DJI Direct (91%) have high fulfillment rates and are reliable for reorders.
AirPods Pro 2, Peloton Bike+, and iPad Pro don't have supplier mappings in SkyStock and need manual verification.
wiiiv automatically matches product IDs across both systems. Accuracy improves when the API documents describe the relationships between fields.
Tips
Getting the most out of it
📋
Include field-name mappings in your API docs
The same data can have different names across APIs (id vs productId, price vs totalAmount). Adding a mapping table helps wiiiv combine data accurately.
⚡
Create a "Quick Reference" section
Listing frequently used APIs as a table at the top of the document helps wiiiv find the right endpoint faster.
⚠
Document caveats too
Notes like "aggregating /orders directly for sales figures is inaccurate" help wiiiv avoid incorrect approaches.
🔄
Update docs when APIs change
When endpoints change or fields are added, update your Knowledge documents. wiiiv always operates based on the latest documents.
wiiiv actually calls APIs. When connecting to production (not test) environments, we recommend using an account that only allows read-only (GET) operations. We also suggest starting with safe APIs in your Knowledge documents and gradually expanding from there.
Next
What else you can do
Once you're comfortable with basic queries and chart conversion, try these:
📈
Period comparison
"Compare March and April sales" — automatically compares data across periods.
📊
Scheduled reports
Register as a workflow to receive automated inventory/sales reports every morning.
🔍
Anomaly detection
"Are there any products with a sudden spike in orders?" — pattern analysis is possible too.
📝
Data-driven documents
"Organize these results into a report for team sharing" — connects all the way to document generation.
Although wiiiv's DACS and HazardGuard do their best to prevent destructive operations, they cannot guarantee 100% safety. wiiiv actually calls backend APIs. Exercise extreme caution before executing data-modifying APIs (POST/PUT/DELETE) and always verify before proceeding.
