| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SuiteDataSourceInstanceId | body | Guid | Yes | Guid representing the external systems datasource information. |
| AlternateKey | body | string | Yes | The unique key that represents the object on the external system. |
| ObjectId | body | Guid | No | Guid of the object within PSTPF. If ObjectId is known, the external system may pass this instead of the alternate key. |
| RmsTableCtxId | body | Guid | No | Guid of the RmsTableCtx within PSTPF. This is used if the alternate key is provided to identify the object to update. |
| DynamicContent | body | DynamicContentModel | Yes | Dynamic Content to be added to the object. |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| DynamicContentDefinitionId | body | DynamicContentModel | Yes | Dynamic Content Definition indicating the content type. |
| ContentFormatId | body | DynamicContentModel | No | Guid indicating the content format. Not required to be passed. |
| Content | body | DynamicContentModel | Yes | Actual Content to be added to the object. |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /json/reply/SaveObjectDynamicContent HTTP/1.1
Host: production-eros-platform-apisubscription.azurewebsites.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{"AlternateKey":"String","DynamicContent":{"Content":"String"}}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}}