Aspen Collections - Organization and a better way to share

Our free, fast, and secure API Client, Aspen, continues to be a hit.Since its launch, it’s been the sleek, new code editor that everyone wants to try out, shooting straight to #1 on the App Store’s Developer Tools category.  Today Aspen has thousands of institutional downloads which shows there is still a real need to make API requests, explore the responses, and use AI to simplify workflows. 

You can imagine Aspen as the Swiss Army knife of API clients—compact, versatile, and always ready to tackle whatever you throw at it. It's become the go-to tool for developers and institutions alike, not just because it’s free and secure, but because it cuts through the noise—no signups, no payments, no data worries—just pure, unadulterated efficiency.

In July, Aspen made waves with its JSON visualization feature, allowing you to see data in a way that feels intuitive and well-organized. Now, we’re taking another leap forward with Aspen Collections—a feature designed to bring a whole new level of organization and sharing to your workflow.

ASPEN API COLLECTIONS

Collections is a ubiquitous term in the API space serving as the de facto concept for organizing and grouping API requests. Think of Collections as your personal Git repository for API requests, except instead of managing code, you’re managing the lifeblood of your applications—APIs. 

We follow the same understanding in Aspen. In addition to providing a chronological list of API requests made in the History sidebar, users can now save those requests as a Collection and name or rename them according to their needs. In the world of API clients, Collections are like the containers you use to Dockerize your services: they group together all the related pieces, making everything neat, tidy, and easy to deploy.

With Aspen, Collections let you save and name your API requests, transforming your History sidebar into a powerful tool for managing complex workflows. It's like having a version control system, but for  your API requests, where you can create folders and sub-folders to group APIs by specific criteria. Whether you're following an API flow from endpoint to endpoint or keeping all the APIs for a single service together, Collections is the feature that brings order to the chaos.

Users can further create folders and sub-folders in order to group APIs on specific criteria. This means Collections can make it easy to do things like follow an API flow from endpoint to endpoint or keep all the APIs for a single service together.

Aspen API Collections

ASPEN HISTORY SEARCH

For the power users out there—those with hundreds or even thousands of API requests—Aspen Collections offers a Search feature that’s as responsive as a well-tuned database query. No more scrolling through endless lists; just type what you need, and Collections will find it in a flash. It’s like having an autocomplete feature that not only knows your code but also understands the structure of your entire API ecosystem.

Incorporating Collections into Aspen is just the first step towards reaching full feature parity with other modern API clients, but without the usual headaches. We’re cutting the bloat, streamlining your workflow, and making sure you spend less time managing APIs and more time building the next big thing.

So, give Aspen Collections a spin and see how it can transform the way you work with APIs. We can’t wait to hear what you think!