AlbaApi

UserConsentPostReq

The following routes are available for this service:
POST	/userconsent


export class Entity implements IEntity
{
    public id?: string;

    public constructor(init?: Partial<Entity>) { (Object as any).assign(this, init); }
}

export class Consent extends Entity
{
    public consentDefinitionId?: string;
    public consents?: { [index: string]: boolean; };
    public consentedDate?: string;
    public lang?: string;
    public consented?: boolean;
    public expired?: boolean;

    public constructor(init?: Partial<Consent>) { super(init); (Object as any).assign(this, init); }
}

export class UserConsentPostReq
{
    public userId?: string;
    public consent?: Consent;

    public constructor(init?: Partial<UserConsentPostReq>) { (Object as any).assign(this, init); }
}

TypeScript UserConsentPostReq DTOs

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

HTTP + JSON

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: application/json
Content-Type: application/json
Content-Length: length

{"userId":"String","consent":{"consentDefinitionId":"String","consents":{"String":false},"consentedDate":"0001-01-01T00:00:00.0000000","lang":"String","consented":false,"expired":true,"id":"String"}}

HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"consentDefinitionId":"String","consents":{"String":false},"consentedDate":"0001-01-01T00:00:00.0000000","lang":"String","consented":false,"expired":true,"id":"String"}