POST | /api/applications | Create an Application |
---|
using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using Hmx.Accounts.ServiceModels;
using Hmx.Accounts.Models;
namespace Hmx.Accounts.Models
{
public partial class Application
{
public virtual string Id { get; set; }
public virtual string Name { get; set; }
public virtual string Token { get; set; }
public virtual string PurchaseUrl { get; set; }
public virtual bool IsActive { get; set; }
}
}
namespace Hmx.Accounts.ServiceModels
{
public partial class CreateApplication
{
public virtual string Id { get; set; }
public virtual string Name { get; set; }
public virtual string PurchaseUrl { get; set; }
}
public partial class CreateApplicationResponse
{
public virtual string Message { get; set; }
public virtual Application Application { get; set; }
public virtual HttpStatusCode Status { get; set; }
public virtual ResponseStatus ResponseStatus { 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 /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 } } }