Collections and team sharing
Requests are only useful if you can find them again. Echo organizes everything into spaces and collections, and lets you share that structure with your team on your terms.
Organize your work
Spaces are the top level: one per project, product or client. Inside a space, collections hold your requests, and folders nest as deep as you need, with no depth limit. Echo Free includes up to 100 collections and 1,000 saved requests per organization.
Keeping things tidy is straightforward:
- Drag and drop requests and folders to restructure.
- Rename items inline, right where they sit.
- Use bulk operations when a cleanup touches many items at once.
Share with your team
After you sign in and sync a collection, you can share it with teammates while connected. Echo has in-app people search, so adding someone starts with their name.
Every share carries a permission level:
- Read: consult the collection.
- Contribute: contribute to the collection.
- Full Access: maintain the collection.
Pick the level per person, so a stakeholder who only needs to look gets Read, while the teammate maintaining the collection gets Full Access. You stay in control of who can change what.
Work across organizations
If you belong to more than one organization, the workspace switcher moves you between them without signing out and back in. Each workspace keeps its own spaces, collections and shares. Choose the same workspace in Echo and Maestro when working with synced mocks, contracts and applications.
Sync across devices
Signed-in work syncs through the Gapfy backend: collections, requests, environments, schedules, mock servers and deletions too. Remove a collection on your desktop and that deletion syncs to your other devices.
When two devices edit the same item while offline, Echo captures the conflict instead of silently overwriting one side and offers a repair action so you can resolve it.
The Android and iOS companion apps share the sync engine. Your signed-in collections can follow you between desktop and mobile without maintaining a separate export for each device.
Share a callable mock
Sharing a collection gives teammates access to your organized work. A mock on the desktop is free. To give an application a public HTTP endpoint that answers with the desktop closed, publish a synced mock through the public hosting panel in Maestro on a paid Echo plan. Publishing a team mock requires Echo/ManageHosting; the owner of a personal space can publish its own mock on a paid plan. The public mock hosting guide explains public URLs and hosting controls.
For automated access to contract publication, bound contracts or the paid .NET rules feed, use applications and keys. Collection permissions and application key scopes serve different purposes; sharing a collection does not issue a key. Creating an application key requires a paid Echo plan, even though contracts remain available on Free in Maestro.
Guest mode and local work
Organizing requests, spaces, folders and bulk operations works in guest mode too, entirely offline. Sharing, sync and workspaces need a signed-in account. See getting started for the difference between the two modes.