Understandable onboarding
Users understand how to create their workspace, sign in, and start operating without having to decode technical jargon.
Document automation for finance and operations
Extract, validate, and operate invoice data with a frontend ready to sell and run.
Structa Engine turns invoices and expense documents into operational data with a guided flow: create workspace, enter the panel, and process documents without forcing customers into backend jargon.
BilingualTraceable jobsTenant + admin dashboardsSwagger + Explorer
POST /v1/ingest
$ curl -X POST \
https://api.structa.io/v1/ingest \
-H "Authorization: Bearer sk_structa_..." \
-F "file=@factura.pdf"
// 1.2 s · status: done
{
"vendor": "Acme Corp S.A.",
"total": 142500,
"currency": "COP",
"date": "2026-03-06"
}
Customer workspace
Documents, operational status, access, webhooks, and next steps are visible in one place.
Operator console
Customers, plans, quotas, providers, and operational monitoring are organized by task instead of raw backend contract shape.
A clear flow for demos and operations
1. Create workspace
Register the tenant and land in the main panel without expecting the customer to know APIs or endpoints.
2. Enter the workspace
The customer sees documents, account status, access, and daily operations with the right context.
3. Configure and operate
From admin you connect providers, adjust quotas, and supervise queues, workers, and failures.
Built for real operations
- ✓ Backend complexity stays hidden behind a guided flow for customers and operators.
- ✓ Bilingual dashboards with dedicated UI plus an authenticated explorer for advanced endpoints.
- ✓ Visual identity preserved: teal, orange, and a bright technical atmosphere.
Plans that communicate value from the landing page
Free
For testing, technical onboarding, and sandbox usage.
- ✓ Fast setup
- ✓ Baseline usage
- ✓ Low-friction demos
Pro
For operating teams with moderate volume and ongoing automation.
- ✓ More jobs
- ✓ Webhooks
- ✓ Full operational console
Business
For multi-tenant operation with observability and tighter control.
- ✓ Higher quota
- ✓ Configurable routing
- ✓ Tailored support
Frequently asked questions
Is access based on username and password?
For customers we present it as a workspace access code. Under the hood the MVP still uses technical credentials to stay compatible with the current backend.
Can I use every API endpoint from the frontend?
Yes. The UI covers the highest-value flows and keeps the rest reachable through an authenticated explorer.
Does public documentation remain available?
Yes. It is served as public Astro/MDX content and still coexists with backend Swagger and OpenAPI.