Retrieves all tags associated to a iTwin or iTwin/iModel combination.
Authentication
Requires Authorization header with valid Bearer token for scope itwin-platform.
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
Request parameters
Request headers
OAuth access token with itwin-platform scope
Setting to application/vnd.bentley.itwin-platform.v1+json is recommended.
Response 200 OK
List of all available tags for the iTwin and iModel.
{ "tags": [{ "id": "ACZbDmWhULVChRcDRkoPdLaNv7DGPQORQpkxmyDyE1ERZS7bsqUkWEmr9ZGmC5TopQ", "displayName": "Test Name", "_links": { "iTwin": { "href": "https://api.bentley.com/path1/path2/id" }, "imodel": { "href": "https://api.bentley.com/path1/path2/id" }, "creator": { "href": "https://api.bentley.com/path1/path2/id" } } }], "_links": { "self": { "href": "https://api.bentley.com/path1/path2/id" } } }
Response 401 Unauthorized
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
{ "error": { "code": "HeaderNotFound", "message": "Header Authorization was not found in the request. Access denied." } }
Response 404 Not Found
Requested tag is not available.
{ "error": { "code": "TagNotFound", "message": "Requested tag is not available." } }
Response 429 Too many requests
This response indicates that the user has sent too many requests in a given amount of time.
{ "error": { "code": "TooManyRequests", "message": "More requests were received than the subscription rate-limit allows." } }
Response headers
The number of requests exceeds the rate-limit for the client subscription.
Link
Http reference
TagLinks
Tag
TagListLinks
TagListResponse
Error
Contains error information.
One of a server-defined set of error codes.
A human-readable representation of the error.
The target of the error.
Error Response
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.