Integrations

Requestarium connects to the tools your team already uses: Jira for bugs, Confluence for API documentation, and GitHub, GitLab, or Bitbucket for keeping collections next to your code.

Jira

Link requests and collection runs to Jira issues, and file a bug from a failed run in a few clicks.

Connect Jira (organization admins). Open Settings → Integrations → Jira and Confluence and choose one:

• Connect with Atlassian: sign in with your Atlassian account and approve access.
• API token: enter your Jira Cloud site (https://<site>.atlassian.net), the account email, and an Atlassian API token.

Everyone in the organization works through this one connection. Issues are created as the connected Atlassian account, and their description names the Requestarium user who filed them.

Use it.

• On a request or a saved run, open Jira to link existing issues by key, link, or search. Linked issues show their current summary and status.
• On a failed run, Create issue opens a form already filled in with the target, environment, branch, commit, CI link, and the failed requests. The issue links back to the run.
• Unlinking removes only the link. The Jira issue stays.

From CI, requestarium run-collection ... --jira-on-failure PROJ files an issue when a run fails, or comments on the open issue from an earlier failure of the same collection and branch. See the CLI reference.

Jira Cloud is supported. Jira Data Center is not supported yet.

Confluence

Publish a collection's documentation to a Confluence page and keep it current.

Confluence uses the same Atlassian connection as Jira. If you connected with Connect with Atlassian before Confluence was available, an admin disconnects and connects again to grant the Confluence permissions.

Publish. On a collection's Overview, click Publish to Confluence, pick a space, and optionally a parent page. The page lists every request in tree order with its folder, method, URL, docs, and headers, and, if you choose, the request bodies as examples.

• Publishing again updates the same page, so Confluence history shows each version.
• Select a folder to publish just that folder as its own page. This is how to split a large collection.
• Header values that look like credentials (Authorization, cookies, API keys, tokens) are masked before anything leaves the app, unless the value is a {{variable}}. Bodies are not masked: check them before you include them.
• Edits made in Confluence are replaced on the next publish.

From CI: requestarium publish-confluence COLLECTION --space KEY. See the CLI reference.

A page holds up to 500 requests.

Sync with Git

Keep a collection as plain YAML files in a repository folder, one file per request, so changes go through your usual review and the collection lives next to the code it tests.

1. On a collection's Overview, click Sync with Git.
2. Connect GitHub, GitLab, or Bitbucket (each member connects their own account), then pick a repository, a branch, and a folder.
3. Push commits your changes. Pull brings in your teammates' changes. When both sides changed the same request, Requestarium merges field by field and asks you only about real conflicts.

Environments are not synced unless you choose to include them, and secret values are never written to the repository: only the variable name is.

On the Team and Enterprise plans you can also sync to an S3-compatible bucket (Amazon S3, Cloudflare R2, MinIO, and others) instead of a repository.

Plans

Privacy

Integration tokens are stored encrypted, and Requestarium sends a provider only what a member asks for. Disconnecting deletes the stored token. See the Privacy Policy.