Open-source project
requestly/requestly avatar
requestly/requestly

Nine entries, no source: what the requestly/requestly repository actually holds

Community hub for Requestly API Client — bugs, feature requests, and roadmap. The privacy-first Postman alternative.

6,767 stars683 forksUnknownNOASSERTION

At a glance

What is it?
The repository everyone links for Requestly is a community hub for a proprietary API client, not the application source. Its page is worth reading for what it says about licensing, downloads and where each piece of the ecosystem lives.
Who is it for?
Use requestly/requestly as the place to file bugs, ask questions and read the roadmap for the Requestly API Client, and go to requestly/interceptor for anything about the browser extension.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
GitHub does not report a main language for this repository.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • requestly/requestly6,767 ★ · +12
Star history
Repository2026-09-112026-11-15
requestly/requestly6.8k6.8k

12 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

This repository holds issues and a roadmap, and no source at all

The top level of requestly/requestly contains .gitattributes, .github/, .gitignore, CODE_OF_CONDUCT.md, CONTRIBUTING.md, LICENSE, README.md, assets/ and community-guidelines.md. There is no package.json, no build configuration and no src directory. That is deliberate and stated on the page: this repository is the community hub for the Requestly API Client, and it exists so you can report a bug, request a feature, ask a question or browse the roadmap. The first three go through issue templates named bug-report.yml, feature-request.yml and question.yml. The roadmap is a GitHub project board rather than a file in the tree. For developers who have been with the project since 2018 the page carries an explanation: this URL previously hosted the source for the open source browser extension and web app, and that code now lives at requestly/interceptor.

The application arrives as a per-architecture download, with no build step

Because there is no source here, there is nothing to compile. The README carries one download link per platform and per CPU, and each points at a different path under the same host:

code
https://get.requestly.com/api-client-macos-arm
https://get.requestly.com/api-client-macos-intel
https://get.requestly.com/api-client-windows
https://get.requestly.com/api-client-linux

Separate Apple Silicon and Intel builds is the detail to notice if your machine is an Intel Mac, since there is no single universal binary on offer. The product documentation sits at docs.requestly.com/api-client. Nothing on this page states a minimum macOS or Windows version, names a Linux packaging format, publishes a checksum, or explains how updates are delivered, so those answers belong to the product docs rather than to the repository.

Three places to keep collections: local files, team sync, or self-hosted

Where your API collections live is the first decision the product asks you to make, and the README frames the choice as data sovereignty with three answers: local, team sync, or self-hosted. Local workspaces are described as everything private and under your control, no cloud storage, just secure local files. Team Projects sync instantly and let several people work on the same collections. Self-hosting exists for organisations that want the server inside their own perimeter. Git Sync is the fifth row of the feature table and cuts across that choice differently: it keeps API collections in sync with a Git repository and asks you to collaborate using Git, which puts review, branching and history on the same footing as application code. The page does not explain how the Git-backed mode and the local or team modes compose, so treat them as separate routes rather than one combined configuration.

Pre and post scripts are the hook that decides whether Requestly fits your tests

The feature table names six capabilities. Two of them carry the behaviour worth understanding. Pre and post scripts adjust requests before they are sent and process responses once received, which is where signing a request, injecting a token or rewriting a payload belongs. The REST API playground saves your APIs in one place and tests them whenever you need. GraphQL support tests endpoints with schema introspection and auto-completion. Easy import and export moves API contracts in and out of cURL, Postman and OpenAPI, and that is the mechanism behind the one click Postman switch the README advertises. What the page does not describe is the mapping used during import, so what happens to a collection that carries scripts, environment variables or runner steps is not documented here.

AGPLv3 covers this repository, not the application it describes

The licensing splits in two, and the page is explicit about both halves. This repository, the one holding the issues and the README, is licensed under the GNU AGPLv3, with third party components keeping whatever licenses their own owners provided. The Requestly API Client application is proprietary software and is not covered by that license; its terms are published separately at requestly.com/terms. Read next to the statement that the application is closed source, the copyleft grant tells you very little about the program you install. For a team running a license review, the artefacts to examine are the binary you download and the product terms, and this repository is not where either of them lives. The AGPLv3 covers the words on this page.

Interceptor issues are redirected, which is how you learn which repository you wanted

Filing in the wrong place is common enough that the page handles it in advance. If your issue concerns the HTTP Interceptor, the open source browser extension and web app, it is tracked at requestly/interceptor, and misfiled issues are redirected there automatically. The rest of the ecosystem is laid out as a table so you can aim at the right entry: the Interceptor extension for Chrome, Firefox and Edge together with its web app; the desktop proxy for Mac, Windows and Linux; an MCP server; a web SDK; and an automation repository covering Cypress, Selenium and Playwright integrations. All five are separate repositories from this one, and the API Client, which is not in that table, is the piece the README calls closed-source. So the question of where to file a problem is answered by reading that table rather than by guessing from the product name.

Platform requirements, changelog detail and response times are all absent

The gaps on this page are specific. No minimum operating system version is given for any of the four downloads, there is no Linux packaging format, and there are no install or upgrade instructions beyond the four links. Support is presented as channels rather than commitments: a community link, an X account, a YouTube channel, a contact address and a Stack Overflow tag. Pricing gets a single line, free for up to ten collaborators, with team and enterprise tiers adding advanced governance, SSO, SAML, audit logs and on-prem deployment, and the figures themselves behind requestly.com/pricing. The release history attached to this repository is a run of weekly changelog tags, changelog-2026.03.09, changelog-2026.03.16 and changelog-2026.03.23, which record that a write happened on a given day without saying what changed in the application you would install.

A 2018 code move explains the split, and names where the investment went

Two sentences near the end of the page carry the strategic story. The HTTP Interceptor is not going anywhere, and the API Client is where the investment is going next. Around them sits the README's own account of how this repository changed: for developers who have been with the project since 2018, the URL was deliberately kept as the home for the broader community, its bugs, its ideas and the people building it, after the extension source moved out to requestly/interceptor. The last push to this repository was on 2026-11-02, and the tagged releases are weekly changelog entries rather than versioned application builds, which fits a repository whose job is process rather than code. For anyone weighing up Requestly, that history is the first thing to read, because it tells you which of the repositories in the ecosystem table is the one that is changing.

Editorial conclusion

Use requestly/requestly as the place to file bugs, ask questions and read the roadmap for the Requestly API Client, and go to requestly/interceptor for anything about the browser extension. Before adopting the product, verify three things that this page does not settle: the minimum OS version and Linux packaging for the build you download, what the free tier covers beyond its stated limit of ten collaborators, and whether your existing collections carry scripts or environment variables that the one-click Postman import may not map. Teams doing a license review should note that the AGPLv3 here covers the repository, while the application itself is proprietary under separate product terms.

Frequently asked questions

what is requestly

Requestly is an API client for designing, building and testing APIs, with a REST playground, pre and post scripts, GraphQL support, import and export from cURL, Postman and OpenAPI, Git Sync for collections, and local workspaces. Its GitHub repository is a community hub for bugs, feature requests and the roadmap rather than the application source.

how to install requestly

There is nothing to build. The README links a separate download per platform and CPU under get.requestly.com, covering macOS on Apple Silicon, macOS on Intel, Windows and Linux. The product documentation at docs.requestly.com/api-client is linked alongside them, and this repository does not state minimum OS versions or a Linux package format.

is requestly open source

The API Client application is closed source and proprietary, and its terms are separate from the repository's. This repository is licensed under the GNU AGPLv3, while the open source HTTP Interceptor extension and web app live at requestly/interceptor, with a desktop proxy, an MCP server, a web SDK and automation integrations each in their own repository.

How much does Requestly cost?

The page states that the product is free for up to ten collaborators. Team and enterprise tiers add advanced governance, SSO, SAML, audit logs and on-prem deployment, with the specific figures published on requestly.com/pricing.

how to use requestly chrome extension

The Chrome, Firefox and Edge extension is the Requestly HTTP Interceptor, a separate open source repository with its own web app at requestly/interceptor. Issues about the extension are tracked and answered there, and issues filed in the API Client community hub are redirected automatically.

Official sources

  1. Issues
  2. Project website
  3. README
  4. Releases
  5. requestly/requestly on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/requestly-requestly.svg)](https://hysenlabs.com/projects/requestly-requestly)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/requestly-requestly.svg)](https://hysenlabs.com/projects/requestly-requestly)

Was this useful?