API

Collaboration APIs

GET collaboration/files/{fileId}/file-permissions/{filePermissionId}

File permission details for provided identifier

HTTP method GET
URI https://api.rambase.net/collaboration/files/{fileId}/file-permissions/{filePermissionId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {fileId} File identifier
Integer, minimum 100000
- URI parameter {filePermissionId} Full id reference and object name to this permission
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 4012, version 2

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
1

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]
$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json"
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$select String, optional Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<FilePermission>
2
     <FilePermissionId
FilePermissionId

Uniqe identificator for a file type permission.

>
{Integer}</FilePermissionId>
3
     <EntityDescription
EntityDescription

Descriptive name for the permission entity

>
{String}</EntityDescription>
4
     <Entity
Entity

The entity holding the permission. Can be either role (ROT) or user (USR).

>
5
          <ObjectId
ObjectId

Identifier of the object

>
{Integer}</ObjectId>
6
          <ObjectType
ObjectType

Type of object

Possible domain values can be found here

>
{String}</ObjectType>
7
          <ObjectLink
ObjectLink

API reference to the object

>
{String}</ObjectLink>
8
     </Entity>
9
     <CanRead
CanRead

Permission to view the contents of a file. This permission does not inhibit accessibility to see metadata for a file, such as filename, searchtags etc.

>
{Boolean}</CanRead>
10
     <CanWrite
CanWrite

Permission to make a new version of a file. This permission deos not inhibit a user from updating a files metadata such as filename and searhtags etc

>
{Boolean}</CanWrite>
11
     <CanDetach
CanDetach

Permission to detach a file from its RamBase Object.

>
{Boolean}</CanDetach>
12
     <FilePermissionLink
FilePermissionLink

Full id reference and object name to this permission

>
{String}</FilePermissionLink>
13
</FilePermission>
1
{
2
     "filePermission": {
3
          "filePermissionId
FilePermissionId

Uniqe identificator for a file type permission.

":
"{Integer}",
4
          "entityDescription
EntityDescription

Descriptive name for the permission entity

":
"{String}",
5
          "entity
Entity

The entity holding the permission. Can be either role (ROT) or user (USR).

":
{
6
               "objectId
ObjectId

Identifier of the object

":
"{Integer}",
7
               "objectType
ObjectType

Type of object

Possible domain values can be found here

":
"{String}",
8
               "objectLink
ObjectLink

API reference to the object

":
"{String}"
9
          },
10
          "canRead
CanRead

Permission to view the contents of a file. This permission does not inhibit accessibility to see metadata for a file, such as filename, searchtags etc.

":
"{Boolean}",
11
          "canWrite
CanWrite

Permission to make a new version of a file. This permission deos not inhibit a user from updating a files metadata such as filename and searhtags etc

":
"{Boolean}",
12
          "canDetach
CanDetach

Permission to detach a file from its RamBase Object.

":
"{Boolean}",
13
          "filePermissionLink
FilePermissionLink

Full id reference and object name to this permission

":
"{String}"
14
     }
15
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 101015 HTTP 404 Permission not found
Error 105030 HTTP 400 Permission not found