Possibly this feature exists and is not yet reflected in documentation, but the following would be very useful for our current needs (and I imagine many others making heavy use of Teams for user organization/grouping/pipeline access restriction):
The response examples are truncated as I'm not sure what the underlying schema can provide, but hopefully this will serve as a reasonable basis for a new endpoint spec.
Possibly this feature exists and is not yet reflected in documentation, but the following would be very useful for our current needs (and I imagine many others making heavy use of Teams for user organization/grouping/pipeline access restriction):
1. View all teams visible to user:
Example Request:
Example Response:
2. View pipelines of a given team:
Example Request:
Example Response:
The response examples are truncated as I'm not sure what the underlying schema can provide, but hopefully this will serve as a reasonable basis for a new endpoint spec.