Get Site Permissions

get

/sites/management/api/v1/sites/{id}/permissions

RELATION

Read the permissions the authenticated user or client application has for a site. The permissions list the actions that can be performed on a site and resources related to the site, such as conversations, share links, members and annotations.

Introduced in release 22.7.2.

Authorization

To invoke this operation, the authenticated user or client application must have been shared with the resource and have one of the following sharing roles:

  • Owner
  • Manager
  • Contributor
  • Downloader
  • Viewer

Path Alternative Identifiers

The default identifier for a Site resource is the Site Identifier. The Site resource supports alternative identifiers.

nameSite Name

Instead of the site identifier, the site name can be used to uniquely identify a site in the resource path. The default resource path parameter for a site is the site identifier, but when working with sites the human-readable site name is sometimes easier.

http://api.example.com/sites/management/api/v1/sites/name:MyNewProduct/permissions

Introduced in release 19.4.1.

Successful Response Examples

This operation responds with the following success (2xx) responses. For a full list of response HTTP status codes and example bodies, consult the Response section of this operation.

200OK - Site Permissions

Returns the site permissions for the authenticated user or client application.

Request

GET https://api.example.com/sites/management/api/v1/sites/{id}/permissions

Response Body

{
  "self": [
      "preview",
      "read",
      "write",
      "update"
  ],
  "file": [
      "preview",
      "read",
      "write",
      "update"
  ],
  "members": [
      "read"
  ],
  "shareLink": [
      "read",
      "create",
      "update",
      "delete"
  ],
  "annotation": [
      "read",
      "write",
      "update",
      "delete"
  ],
  "conversation": [
      "read",
      "write",
      "update",
      "delete"
  ]
}
Introduced in release 22.7.2.

Client Error Response Examples

This operation responds with following client error (4xx) responses with exception details in the response body. For a full list of response HTTP status codes and example bodies, consult the Response section of this operation.

404Not Found - Site Not Found

The site does not exist or has been deleted, or the authenticated user or client application does not have access to the site.

Error Code

OCE-SITEMGMT-009003

Resolution - Check Identifier

Check that the site identifier is valid.

Resolution - Check Membership

Check that the authenticated user is a member of the site or a site administrator.

Exception Detail Fields

This error type includes the following fields/values in the response:

Field NameDescription
siteSite that does not exist or is not visible to the authenticated user.

For detailed information about this exception detail type, consult the SiteNotFoundExceptionDetail schema in the definitions section of the swagger document.

Example Response Body
{
  "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
  "title": "Site Not Found",
  "status": "404",
  "detail": "Site does not exist or has been deleted, or the authenticated user or client application does not have access to the site.",
  "o:errorCode": "OCE-SITEMGMT-009003",
  "site": {
    "id": "FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
  }
}

404Not Found - Relationship Not Found

An attempt to read a relationship has failed because the relationship does not exist. Reading a relationship can fail if the relationship no longer exists or the authenticated identity is not authorized to read the relationship details.

Error Code

PAAS-005027

Example Response Body
{
  "type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
  "title": "Relationship Not Found",
  "status": "404",
  "detail": "Relationship resource not found. There is a relationship to a resource, but the resource at the end of the relationship does not exist, or the authenticated identity cannot see the resource.",
  "o:errorCode": "PAAS-005027"
}

This resource represents the relationship between a Site and Site Permissions resource. If the Site Permissions has been deleted or the authenticated user is not authorized to read the resource then the response status code will be 404 Not Found and a Relationship Not Found error will be returned in the response body.

Request

Path Parameters
Query Parameters
  • Comma-delimited string of field names that should not be included in the response.

  • Comma-separated list of link relation names to exclude from the response.

  • Comma-delimited string of field names to include in the response. Nested fields can be identified using a dot to separate the field names. Field names are case-sensitive. Field names are ignored if the field does not exist.

  • Resources that have been marked for deletion can be read, modified, and support extended operations as long this query parameter is set to true. When the includeDeleted query parameter is not sent then the response to read, modification, and extended operations will be identical to that which would be returned if the resource was permanently deleted.

  • Comma-separated list of link relation names to include in the response. By default, all links are returned.

    The following links are provided by this resource:

    Link RelationshipDescription
    parentDescribes where the parent resource can be read. Equivalent to an up link, this link provides the link to the parent resource, such as the collection resource that contains a singular resource.
    selfDescribes the current returned representation of the resource. Used for links that represent the resource itself. For example, if a resource is returned as part of a collection, the self link will provide the URL path for the individual resource.
    canonicalDescribes the preferred representation of the requested resource. Used for links that represent the canonical form of the resource. For example, if a resource is returned as part of a collection, the canonical link will provide the URL path for the canonical form of the individual resource.
    describedByDescribes the schema resource providing metadata information about the resource. Used on collection, singular and relation resources to indicate where the schema resource is that describes the resource.
  • Specify the resource representation that should be used to control the response fields and links. If no representation is specified, the client-defined representation is returned, based on the values of the fields, excludeFields, links, excludeLinks and expand query parameters.

    The following representations are supported with the return query parameter:

    RepresentationDescription
    representationFull resource representation includes all properties and links and expands most relationships.
    defaultDefault resource representation includes most properties and links.
    basicBasic resource representation includes some properties and some links.
    minimalMinimal resource representation, includes essential properties and no links.
Back to Top

Response

Supported Media Types

200 Response

OK
Headers
Body ()
Root Schema : schema
Type: object
Show Source
  • annotation

    Set of annotation permissions the user has.

    Valid values are:

    • read - Read annotation
    • write - Write an annotation
    • update - Update annotation
    • delete - Delete annotation

    Introduced in release 22.7.2.
  • conversation

    Set of conversation permissions the user has.

    Valid values are:

    • read - Read a conversation
    • write - Write to a conversation
    • update - Update a conversation
    • delete - Delete a conversation

    Introduced in release 22.7.2.
  • file

    Set of file level permissions the user has.

    Valid values are:

    • preview - Preview file
    • read - Read file
    • write - Write to file
    • update - Update file
    • delete - Delete file

    Introduced in release 22.7.2.
  • links
  • members

    Set of members permissions the user has.

    Valid values are:

    • read - Read and list members
    • add - Add to members
    • update - Update members
    • remove - Remove members

    Introduced in release 22.7.2.
  • self

    Set of folder level permissions the user has.

    Valid values are:

    • preview - Preview folder
    • read - Read folder
    • write - Write to folder
    • update - Update folder
    • delete - Delete folder

    Introduced in release 22.7.2.
  • shareLink
Nested Schema : annotation
Type: array

Set of annotation permissions the user has.

Valid values are:

  • read - Read annotation
  • write - Write an annotation
  • update - Update annotation
  • delete - Delete annotation

Introduced in release 22.7.2.
Show Source
Nested Schema : conversation
Type: array

Set of conversation permissions the user has.

Valid values are:

  • read - Read a conversation
  • write - Write to a conversation
  • update - Update a conversation
  • delete - Delete a conversation

Introduced in release 22.7.2.
Show Source
Nested Schema : file
Type: array

Set of file level permissions the user has.

Valid values are:

  • preview - Preview file
  • read - Read file
  • write - Write to file
  • update - Update file
  • delete - Delete file

Introduced in release 22.7.2.
Show Source
Nested Schema : members
Type: array

Set of members permissions the user has.

Valid values are:

  • read - Read and list members
  • add - Add to members
  • update - Update members
  • remove - Remove members

Introduced in release 22.7.2.
Show Source
Nested Schema : self
Type: array

Set of folder level permissions the user has.

Valid values are:

  • preview - Preview folder
  • read - Read folder
  • write - Write to folder
  • update - Update folder
  • delete - Delete folder

Introduced in release 22.7.2.
Show Source
Example Response (Site Permissions)
{
    "self":[
        "preview",
        "read",
        "write",
        "update"
    ],
    "file":[
        "preview",
        "read",
        "write",
        "update"
    ],
    "members":[
        "read"
    ],
    "shareLink":[
        "read",
        "create",
        "update",
        "delete"
    ],
    "annotation":[
        "read",
        "write",
        "update",
        "delete"
    ],
    "conversation":[
        "read",
        "write",
        "update",
        "delete"
    ]
}

400 Response

Bad Request

401 Response

Unauthorized

403 Response

Forbidden

404 Response

Not Found
Headers
Body ()
Root Schema : schema
Match All
Show Source
Nested Schema : SiteNotFoundExceptionDetail
Match All
Show Source
Nested Schema : ExceptionDetail
Type: object

In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.

Show Source
Nested Schema : SiteNotFoundExceptionDetail-allOf[1]
Type: object
Show Source
Nested Schema : o:errorDetails
Type: array

Multiple errors can be organized in a hierarchical structure.

Show Source
Nested Schema : items
Match All
Show Source
  • ExceptionDetail

    In addition to HTTP error code and error messages, it is often desirable to provide additional information to the client when a request fails. In such cases, the additional information will be included in the response body.

Example Response (Site Not Found)
{
    "type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
    "title":"Site Not Found",
    "status":"404",
    "detail":"Site does not exist or has been deleted, or the authenticated user or client application does not have access to the site.",
    "o:errorCode":"OCE-SITEMGMT-009003",
    "site":{
        "id":"FCA9C0E5CDCB549A19FFB85987A2352778961003B8A0"
    }
}
Example Response (Relationship Not Found)
{
    "type":"http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1",
    "title":"Relationship Not Found",
    "status":"404",
    "detail":"Relationship resource not found. There is a relationship to a resource, but the resource at the end of the relationship does not exist, or the authenticated identity cannot see the resource.",
    "o:errorCode":"PAAS-005027"
}

406 Response

Not Acceptable

416 Response

Range Not Satisfiable

429 Response

Too Many Requests

500 Response

Internal Server Error

501 Response

Not Implemented

502 Response

Bad Gateway

503 Response

Service Unavailable

504 Response

Gateway Timeout
Back to Top