| POST,PUT | /content/element |
|---|
using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using AlbaApi.ServiceModel;
using TasSyd.Model;
using TasSyd.Model.Base;
namespace AlbaApi.ServiceModel
{
public partial class ContentElementSaveReq
{
public virtual string Country { get; set; }
public virtual string Lang { get; set; }
public virtual string Section { get; set; }
public virtual string Element { get; set; }
public virtual string ItemId { get; set; }
public virtual string Content { get; set; }
public virtual string Status { get; set; }
}
}
namespace TasSyd.Model
{
public partial class Content
: Entity
{
public Content()
{
Elements = new Dictionary<string, string>{};
}
public virtual string Section { get; set; }
public virtual string ItemId { get; set; }
public virtual string ItemCode { get; set; }
public virtual string Country { get; set; }
public virtual string Lang { get; set; }
public virtual string App { get; set; }
public virtual string CompanyId { get; set; }
public virtual string Company { get; set; }
public virtual Dictionary<string, string> Elements { get; set; }
}
}
namespace TasSyd.Model.Base
{
public partial class Entity
: IEntity
{
public virtual string Id { get; set; }
}
}
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 /content/element HTTP/1.1
Host: hcbtas-q-albamfs-api.azurewebsites.net
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
country: String,
lang: String,
section: String,
element: String,
itemId: String,
content: String,
status: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
section: String,
itemId: String,
itemCode: String,
country: String,
lang: String,
app: String,
companyId: String,
company: String,
elements:
{
String: String
},
id: String
}