Appear docs
HomepageGitHubAPI toolkitSign inGet demo
  • Getting Started
    • Welcome to Appear
    • How Appear works
    • Who is Appear for?
    • Get In Touch
    • Installation
  • Installation
    • Javascript / Typescript
    • Framework specific installations
      • NestJS
      • NextJS
      • Custom integrations
  • Explanations
    • Branches and environments
  • Connections
  • Managing your APIs
    • Creating a service
    • Add service via URL
    • Grouping & filtering
    • Editing your APIs
    • Overriding/updating a service
  • OpenAPI spec version
  • Tagging services
  • Service Resources
    • Resource map
  • Managing your organisation
    • Managing team members
    • Adding verified domains
  • Resources
    • FAQs
    • Product Map
    • Open-source
Powered by GitBook
On this page
  • Tagging overview
  • Tagging a service
  • Tagging concepts
  • Tagging FAQs

Was this helpful?

Tagging services

PreviousOpenAPI spec versionNextResource map

Last updated 19 days ago

Was this helpful?

Tagging overview

Tagging services in Appear is a flexible and useful way to represent relationships across your systems, teams, and organisational structure.

Tags are added directly from the Service Details view in the Catalog. You can apply them however you see fit — whether to represent environments, teams, business domains, or deployment regions.

Tagging a service

To tag a service, navigate to a service detail view and enter a new line in the editable section at the top half of the column.

From there, invoke the block editor by typing '/' (forward-slash) and select Tags.

Begin typing your tag, or select an existing one. You can add as many or as few as you like.

Use tags to organise, navigate, and assess your API ecosystem in a way that aligns with how your team or organisation works.

Tagging concepts

Tags in Appear are not standalone objects in the database — they only exist in relation to services. This means the list of available tags is simply an aggregate of all tags used across all services.

When adding a tag to a service, we show tags from all environments and versions to encourage consistency and reuse across your system.

However, when grouping or filtering by tags, we scope them to the current branch or environment. This ensures the results are relevant to the specific context you're viewing — like filtering only by tags used in your staging environment

Tagging FAQs

Can my team see my tags?

Yes, tags are shared across your team and organisation.

Can I delete or edit my tags?

No, there is no central way to delete or manage tags once created. This facility is coming soon. If you need help with this, please .

If you have any queries or require support with the above instructions, please with us.

get in touch
get in touch