| POST | /api/applications | Create an Application |
|---|
Imports System
Imports System.Collections
Imports System.Collections.Generic
Imports System.Runtime.Serialization
Imports ServiceStack
Imports ServiceStack.DataAnnotations
Imports Hmx.Accounts.ServiceModels
Imports Hmx.Accounts.Models
Namespace Global
Namespace Hmx.Accounts.Models
Public Partial Class Application
Public Overridable Property Id As String
Public Overridable Property Name As String
Public Overridable Property Token As String
Public Overridable Property PurchaseUrl As String
Public Overridable Property IsActive As Boolean
End Class
End Namespace
Namespace Hmx.Accounts.ServiceModels
Public Partial Class CreateApplication
Public Overridable Property Id As String
Public Overridable Property Name As String
Public Overridable Property PurchaseUrl As String
End Class
Public Partial Class CreateApplicationResponse
Public Overridable Property Message As String
Public Overridable Property Application As Application
Public Overridable Property Status As HttpStatusCode
Public Overridable Property ResponseStatus As ResponseStatus
End Class
End Namespace
End Namespace
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/applications HTTP/1.1
Host: accounts.dev.healthmonix.com
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
id: String,
name: String,
purchaseUrl: String
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
message: String,
application:
{
id: String,
name: String,
token: String,
purchaseUrl: String,
isActive: False
},
status: Continue,
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}