| All Verbs | /api/customcontentviews |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| RmsTableCtxId | query | Guid | Yes | The RmsTableCtxId representing the type of views we are retrieving. |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Views | form | List<CustomContentViewModel> | No | |
| ResponseStatus | form | ResponseStatus | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ContentViewId | query | Guid | No | Id of the Custom Content View. |
| Name | query | string | No | Name of the Custom Content View. |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /api/customcontentviews HTTP/1.1
Host: pfapi.pstpf.com.au
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
Views:
[
{
Name: String
}
],
ResponseStatus:
{
ErrorCode: String,
Message: String,
StackTrace: String,
Errors:
[
{
ErrorCode: String,
FieldName: String,
Message: String,
Meta:
{
String: String
}
}
],
Meta:
{
String: String
}
}
}