Build on top of UluP Spaces.
A public REST API to read and write your users' projects, nodes, tasks, and connections: personal scripts, automations or third-party plugins.
Available endpoints
curl -X POST https://www.ulupspaces.com/api/v1/projects \
-H "Authorization: Bearer <your-key>" \
-H "Content-Type: application/json" \
-d '{"name": "Podcast Launch"}'With a key generated from Profile → API Keys. The fields of each request are in the spec.
Bring SDK Studio to your desktop.
A lightweight Windows app that opens straight into the automation editor: no browser, no tab to keep open.
Getting started
1. Generate a key
From Profile → API Keys inside UluP Spaces, in a few seconds.
2. Read the reference
The full OpenAPI spec lists every endpoint, with request and response examples.
3. Call the API
Directly over HTTP, or with the official TypeScript SDK: your choice.
What you can build
Extensions and integrations
A browser extension that saves a page as a node, a Slack bot that creates tasks from your channel, an importer from another tool.
Automations
A script connecting Spaces to Zapier, IFTTT, or your own pipeline: no AI account needed, just direct calls.
Don't want to write code? Build the same thing visually with SDK StudioDashboards and analytics
A tool that reads your project state and turns it into stats, reports, or custom visualizations.
Official SDK
A typed TypeScript client, generated directly from the spec: no hand-written requests.
Install
npm install @ulupstudio/sdkFrequently asked questions
What permissions does an API key have?
Full (read/write) access to the account of whoever generates it, with the same permissions that user would have in the app. Don't share it with code you don't trust.
Does using this API cost anything?
No. UluP Spaces is free to use, and the API doesn't require any paid plan.
Can I sell a plugin I build on top of this API?
Yes. You can build and sell whatever you want on top of the API, on your own terms: the only thing not to do is resell raw access to the key itself.
How is this different from Ulupy/MCP?
Ulupy connects a conversational AI like Claude, via automatic OAuth. This REST API is for code that always does the same action automatically (an extension, a bot, a script) with no AI in the loop.
How is this different from SDK Studio?
SDK Studio is the visual, no-code alternative: triggers and actions are built by dragging them in an editor inside Spaces. This REST API is for people who want to write their own code: more flexibility, but it requires knowing how to program. It's also available as a Windows desktop app, above.