API reference
Talk to Wemob from your own scripts and tools.
Most people use Wemob entirely through the dashboard and never need the API. But if you're a developer building something that needs to work with your Wemob account — a script, a workflow, a custom integration — there's a clean HTTP API you can call. This section of the docs covers the main endpoints.
Who this is for#
The API is for people who write code and want to automate parts of their Wemob workflow. Common reasons to reach for it:
- Creating a new project automatically when someone submits a form elsewhere
- Syncing a list of products between Wemob and another system
- Downloading the files for a project as part of a backup script
- Wiring a webhook from another tool into a Wemob action
If none of those sound relevant, you don't need the API. The dashboard covers everything most people ever do.
Getting started#
To call the API, you need two things:
- An API key (create one from the Account menu)
- An HTTP client —
curl, your programming language's standard fetch, or a tool like Postman
Every request goes to https://api.wemob.io and includes your API key as an Authorization header.
curl -H "Authorization: Bearer YOUR_KEY" https://api.wemob.io/v2/apps. If you get back JSON, you're in.The endpoints#
The API is organized by resource. Each section below has its own page in the reference.
Authentication
How API keys work and how to include them in every request.
Apps
Create, list, update, and delete projects programmatically.
Files
Read, write, and delete the files inside a project.
Deployments
Trigger publishes and check deploy status.
Webhooks
Get notified when events happen in your account.
API keys
How to create and manage keys in the dashboard.
Rate limits#
To keep the service fair for everyone, there are soft limits on how many requests you can make per minute. If you hit one, the API will respond with a 429 status and tell you how long to wait before trying again. For normal use you'll never see this — the limits are generous and are only there to protect against runaway scripts.
