From idea to API in minutes.
SwiftForge creates hosted JSON endpoints from schemas you define visually. This navigator follows the same order as the workspace.
Quick start
- Create a free account and sign in.
- Create a project with a unique URL slug.
- Add a resource and define its typed fields.
- Generate a scoped API key.
- Open Developer mode to test or copy your endpoint.
1. Build your workspace
A project groups related resources, keys, records, and allowed browser origins. Resource names become URL paths. Fields support text, number, and boolean types and can be required.
2. Authenticate safely
Generate a read, write, or full key and send it as a Bearer token. The full key appears only once—store it in a server-side environment variable, never browser source or Git.
Authorization: Bearer sf_live_YOUR_KEY
3. Send requests
GET lists or retrieves records. POST creates one. PATCH updates one. DELETE removes one.
curl -X POST https://endpoints.swift7.net/v1/your-project/tasks \
-H "Authorization: Bearer sf_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"title":"Ship the app","done":false}'PATCH and DELETE use the record ID at the end of the URL: /tasks/RECORD_ID.
4. Filter and paginate
List endpoints accept limit, offset, and sort. Keep page sizes small for fast applications.
5. Connect a browser app
In Developer mode, add the exact origins allowed to call your endpoint—for example https://app.example.com. Do not include a path. Remember that keys embedded in public JavaScript can be copied; use read-only keys and a trusted backend for sensitive writes.
Public-beta limits
- 3 projects per account
- 5 resources per project
- 5,000 records per project
- 10,000 API requests per month
- 30 fields per resource
Limits may change during the beta. Avoid sensitive production data and keep backups using project export.
Need a hand?
Include the endpoint, HTTP method, status code, and reproducible steps. Never submit a password or API key.
Submit a support report