Appearance
Web app and desktop app
You can use Collapy in your browser at app.collapy.com today. A desktop app is coming soon. The two look and work the same, but they send requests differently, and that affects quotas and which addresses you can reach.
At a glance
| Web app | Desktop app (coming soon) | |
|---|---|---|
| Where requests are sent from | Collapy's cloud servers | Your computer |
| Limited by the monthly cloud execution cap | Yes | No |
| Shows in the Monthly cloud executions count | Yes | Yes |
| Rate limit | About 60 requests per minute per user | None |
Can reach localhost and your private network | No | Yes |
| Secret variable values | Filled in on Collapy's servers. They aren't loaded into the request editor or into the request your browser builds. | Fetched when you send and filled in on your computer |
| Needs the API to allow CORS | No | No |
| Recorded in execution history | Yes | Yes |
Web app
When you press Send in the browser, Collapy forwards the request to its cloud servers. They call your API and return the response. This has a few consequences.
No CORS problems. The request comes from Collapy's servers, not your browser, so your API doesn't need to allow cross-origin requests.
Secrets stay on the server. Secret values are filled in on Collapy's servers just before the request goes out. They aren't loaded into the request editor or into the request your browser builds.
Monthly cloud executions. Each send counts toward your organization's monthly cloud executions, up to your plan's limit. See Plans and limits for the numbers.
The count is shared by everyone in the organization and resets at the start of each calendar month (UTC). When the limit is reached, sends from the web app fail until the next month or until the organization moves to a higher plan. Check how much you've used under Account → Usage.
Rate limit. Each user can send about 60 requests per minute from the web app. If you go over, the request fails. Wait a moment and send it again.
Sends refused by the per-minute limit or the monthly cap are still recorded, as Failed executions.
Public addresses only. Your request starts from Collapy's cloud, so localhost, 127.0.0.1 and private addresses such as 192.168.1.20 point at the cloud, not at your computer or office network. Your local server can't be reached this way. Cloud metadata addresses (such as 169.254.169.254) are blocked outright.
Web app
Testing an API that runs on your own machine? Make it reachable on a public URL first, or use the desktop app when it's available.
Desktop app
Desktop app (coming soon)
The desktop app isn't available to download yet. Its requests will go straight from your computer to the API, without passing through Collapy's cloud.
Because requests leave from your own computer, the desktop app:
- isn't blocked by the monthly cloud execution cap, and has no per-minute limit. Its sends are still recorded, and they currently show up in your organization's Monthly cloud executions count
- can reach
localhost, your private network and anything your computer can connect to, such as a VPN - fetches secret variable values only when you send, and fills them in locally
What's the same on both
- Every send is recorded as an execution and shared with your workspace, with credentials redacted in the stored copy. Executions of a private request stay private. Stored executions count toward your organization's history limit on both the web and the desktop. See Execution history.
- Requests, collections and environments are stored in Collapy, so your work is the same wherever you sign in.
- Changes from teammates appear live on both.
FAQ
Why can't I call localhost from the web app?
The web app sends every request through Collapy's cloud servers. From there, localhost means the cloud server itself, not your computer, so a server running on your machine can't be reached. Use a public URL for your API, or the desktop app once it's available.
Do desktop requests count toward my quota?
They aren't blocked by it. Requests sent from the desktop app aren't stopped by the monthly cloud execution cap and have no per-minute limit. They are still recorded in execution history, so they count toward the history storage limit, and they currently show up in the Monthly cloud executions count on Account → Usage.
Why does my request fail with a CORS error?
It shouldn't. Collapy sends requests from its servers, so browser CORS rules don't apply. If you see an error, check the URL and whether the API is reachable from the public internet.