Resources are like blueprints for your actual API request. They contain actual requests and store information about the HTTP method, the path where the actual resource is located and when it concerns a SOAP request, also holds the SOAPAction. For more information about what a SOAPAction is, please visit https://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383528.
You can add tags to resources. Adding tags will help you get a clear overview of your resources, as each resource will be grouped by their tag group. If a resource doesn’t have any tags, it will be grouped in the no-tags group. If an imported service definition also holds tags per resource, they will be applied to the resources and grouped accordingly.