Skip to content
Rival Docs

Deprecating vs Deleting

Two ways to remove a tool

Rival gives you two distinct mechanisms for taking a tool or version out of active use:

  • Deprecate - hide it from marketplace search while keeping it fully functional. Existing integrations keep working. There is a 30-day grace period before it’s removed entirely.
  • Delete - remove it permanently. Cannot be undone.

Both actions can be applied at two levels:

  • Tool level - affects the entire tool and every version of it.
  • Version level - affects a single version; other versions remain available.

Where these actions live

Open the tool in the Tool Editor (or from My Tools → Built by you). The tool-level actions are in the tool’s menu; version-level actions are in the version history list - each row has its own deprecate / delete option.

Deprecating

Deprecation is the safe option for tools or versions that are already public and may be in active use by callers. Instead of pulling the rug, deprecation hides the tool from marketplace search but keeps it callable, giving anyone who depends on it time to migrate.

When you deprecate:

  • The tool or version is immediately removed from marketplace search.
  • Existing integrations keep working - the API endpoint stays live and continues returning the same results.
  • A 30-day grace period begins. At the end of that window, Rival automatically removes the tool/version entirely.
  • The user who deprecated it gets a confirmation email. Workspaces that previously ran the tool are notified so they can migrate.

Tool-level deprecation

All published versions are marked deprecated together. The tool exits marketplace search immediately and is auto-deleted after 30 days. While deprecated, no new versions can be published.

Version-level deprecation

Only the selected version is hidden and scheduled for removal. Other versions of the same tool keep behaving normally. Useful for retiring an old or problematic version while keeping the newer ones live.

Deleting

Deletion is permanent and immediate. There is no grace period and it cannot be undone.

Because deletion can break callers without warning, it’s restricted by visibility and usage:

  • Private tools and private versions can be deleted instantly - they’re not exposed to external users.
  • Public versions cannot be deleted directly. Deprecate them first, then they’ll be removed automatically at the end of the 30-day window (or you can delete them once they’re no longer public).
  • Tool-level delete is only allowed when the tool has no public versions. If any version is public, deprecate the tool instead.

Tool-level deletion

Removes the entire tool and every version of it. Only available when no version is public.

Version-level deletion

Removes a single version. Other versions remain unaffected. Useful for cleaning up experimental or unused private versions.

Which to choose

  • If the tool or version has ever been public or used by an external caller, deprecate. It gives users time to migrate and avoids breaking integrations.
  • If the tool is private, experimental, or an unused draft, delete.

Next steps