| POST | /userconsent |
|---|
using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using AlbaApi.ServiceModel;
using AlbaApi.Model;
using TasSyd.Model.Base;
namespace AlbaApi.Model
{
public partial class Consent
: Entity
{
public Consent()
{
Consents = new Dictionary<string, bool>{};
}
public virtual string ConsentDefinitionId { get; set; }
public virtual Dictionary<string, bool> Consents { get; set; }
public virtual DateTime ConsentedDate { get; set; }
public virtual string Lang { get; set; }
public virtual bool Consented { get; set; }
public virtual bool Expired { get; set; }
}
}
namespace AlbaApi.ServiceModel
{
public partial class UserConsentPostReq
{
public virtual string UserId { get; set; }
public virtual Consent Consent { 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 /userconsent HTTP/1.1
Host: hcbtas-q-albamfs-api.azurewebsites.net
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
userId: String,
consent:
{
consentDefinitionId: String,
consents:
{
String: False
},
consentedDate: 0001-01-01,
lang: String,
consented: False,
expired: True,
id: String
}
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
consentDefinitionId: String,
consents:
{
String: False
},
consentedDate: 0001-01-01,
lang: String,
consented: False,
expired: True,
id: String
}