API

Collaboration APIs

POST collaboration/emails/{emailId}/object-references

Adds an object reference to email

HTTP method POST
URI https://api.rambase.net/collaboration/emails/{emailId}/object-references
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {emailId} Email identifier
Integer, minimum 100000
Successful HTTP status code 200
API resource identifier 3807, version 3

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
<ObjectReference>
2
     <Object>
3
          <Database
Database

Company code/database the object belongs to

This field is optional.

>{String}</Database>
4
          <ObjectId
ObjectId

Required/mandatory field

Identifier of the object

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

Required/mandatory field

Type of object

>{String}</ObjectType>
6
          <ItemId
ItemId

Item-number of the object

This field is optional.

>{Integer}</ItemId>
7
          <ItemType
ItemType

Type of item

This field is optional.

>{String}</ItemType>
8
     </Object>
9
</ObjectReference>
1
{
2
     "objectReference": {
3
          "object": {
4
               "database
Database

Company code/database the object belongs to

This field is optional.

": "{String}",
5
               "objectId
ObjectId

Required/mandatory field

Identifier of the object

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

Required/mandatory field

Type of object

": "{String}",
7
               "itemId
ItemId

Item-number of the object

This field is optional.

": "{Integer}",
8
               "itemType
ItemType

Type of item

This field is optional.

": "{String}"
9
          }
10
     }
11
}

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.

$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
$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.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]

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.

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

Format:
1
1

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 100050 HTTP 403 No admittance as customer {0}
Error 100053 HTTP 403 You have only admittance to your own suppliers