MigrantLeap.Auth

CompleteProfile

The following routes are available for this service:
POST	/api/v1/completeprofile

using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using MigrantLeap.Auth.v1.Models;

namespace MigrantLeap.Auth.v1.Models
{
    public partial class BaseResponse
    {
        public virtual ResponseStatus ResponseStatus { get; set; }
    }

    public partial class CompleteProfile
    {
        public virtual string Email { get; set; }
        public virtual string FirstName { get; set; }
        public virtual string LastName { get; set; }
        public virtual string Country { get; set; }
        public virtual string Language { get; set; }
        public virtual DateTime? BirthDate { get; set; }
        public virtual string Address { get; set; }
        public virtual string Address2 { get; set; }
        public virtual string City { get; set; }
        public virtual string State { get; set; }
        public virtual string ZipCode { get; set; }
        public virtual string PhoneNumber { get; set; }
        public virtual string PhoneValidationToken { get; set; }
        public virtual bool UpdateHealthProfile { get; set; }
        public virtual string Password { get; set; }
    }

    public partial class CompleteProfileResponse
        : BaseResponse
    {
    }

    [DataContract]
    public partial class ResponseStatus
        : IMeta
    {
        public ResponseStatus()
        {
            Errors = new List<ResponseError>{};
            Meta = new Dictionary<string, string>{};
        }

        [DataMember(Order=1)]
        public virtual int StatusCode { get; set; }

        [DataMember(Order=2)]
        public virtual string Message { get; set; }

        [DataMember(Order=3)]
        public virtual string StackTrace { get; set; }

        [DataMember(Order=4)]
        public virtual List<ResponseError> Errors { get; set; }

        [DataMember(Order=5)]
        public virtual Dictionary<string, string> Meta { get; set; }
    }

}

C# CompleteProfile 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 /api/v1/completeprofile HTTP/1.1 
Host: auth.migrantleap.com 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"email":"String","firstName":"String","lastName":"String","country":"String","language":"String","birthDate":"\/Date(-62135596800000-0000)\/","address":"String","address2":"String","city":"String","state":"String","zipCode":"String","phoneNumber":"String","phoneValidationToken":"String","updateHealthProfile":false,"password":"String"}

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

{"responseStatus":{"statusCode":0,"message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}