Functions
Functions run your server-side code on demand. Write Python once, save it against an app, then run it by name — from your application, on a schedule, or when something happens elsewhere in the platform.
How Functions is organized
Every function belongs to one app. The site URL picks your site, the app slug picks the app, and the function slug picks the code to run.
A function stores what to run and how to run it. Saving a change records a new version, and every execution leaves a record carrying the version that ran, the result, and anything the code logged.
What you can do
| Capability | What it gives you | Start here |
|---|---|---|
| Sandboxed Python | Your own code, saved against an app and run by the platform | Write a function |
| Webhook forwarding | An external endpoint reachable through the same interface as your own functions | Proxy functions |
| Synchronous and asynchronous calls | A result returned to the caller, or an immediate acknowledgement carrying an id you use to fetch the result once it is ready | Execute a function |
| Scheduled runs | Cron schedules attached to a function, each with its own parameters | Schedules |
| Event-driven runs | Execution when a platform event fires, narrowed by an expression you write | Filter conditions |
| Platform access from your code | A TaruviBase SDK client, already authenticated as the caller | Write a function |
| Version history | A record of every code and configuration change, and which version each run used | Versioning |
| Execution history | Parameters, results, tracebacks, and captured logs for past runs | Logs and invocations |
Choose an interface
| Interface | Best for | Setup |
|---|---|---|
| TaruviBase Console | Writing code, running a function with test parameters, and reading its history | Console guide |
| REST API | Every operation, including creating, editing, and deleting functions | Choose direct HTTP |
| Python SDK | Executing functions and reading results from services, jobs, and scripts | Python SDK |
| JavaScript SDK | Executing a function from a browser or server application | JavaScript SDK |
The JavaScript SDK exposes a single function method, execute. Creating,
editing, scheduling, and deleting are available through REST and Console only.
The interface support matrix
shows which interface covers each task.
Making a function public lets anyone who can reach its endpoint run it, with no credentials and no permission check. Review the code before you turn that on.
Deleting a function permanently removes its version history, invocation records, and schedules. There is no recovery path. Export what you need first, or deactivate the function instead.
Details: Security and limits.
Start here
- Create, run, and delete a function — one function, end to end.
- Learn how a call becomes a result, and when to wait for one.
- Choose between app and proxy modes.
- Add schedules or filter conditions as your needs grow.
- Review security and limits before connecting production traffic or making a function public.