To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
HTTP + JSV
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /Ams/{ClientID}/Event/{EventId}/AttendeeTypeTickets HTTP/1.1
Host: ws.yourmembership.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
EventId: 0,
TypeId: 0,
Id:
[
0
],
UsingRedis: True,
AppInitTime: 2025-01-15T07:45:29.5231982-05:00,
ServerID: WS-4-27-804,
ClientID: 0,
ResponseStatus:
{
ErrorCode: String,
Message: String,
StackTrace: String,
Errors:
[
{
ErrorCode: String,
FieldName: String,
Message: String,
Meta:
{
String: String
}
}
],
Meta:
{
String: String
}
},
BypassCache: False,
DateCached: 2025-01-15T08:59:37.2789002-05:00,
Device: Desktop
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
RowsDeleted: 0,
EventAttendeeTypeTicketList:
[
{
Name: String,
EventId: 0,
TypeId: 0,
Id: 0
}
],
EventId: 0,
TypeId: 0,
Id:
[
0
],
UsingRedis: True,
AppInitTime: 2025-01-15T07:45:29.5231982-05:00,
ServerID: WS-4-27-804,
ClientID: 0,
ResponseStatus:
{
ErrorCode: String,
Message: String,
StackTrace: String,
Errors:
[
{
ErrorCode: String,
FieldName: String,
Message: String,
Meta:
{
String: String
}
}
],
Meta:
{
String: String
}
},
BypassCache: False,
DateCached: 2025-01-15T08:59:37.2945363-05:00,
Device: Desktop
}