TicketUserServices

FanSyncFollowsRequest

**Requires Authentication**
Required role:	Admin

The following routes are available for this service:
POST	/FanSync/Follows

import Foundation
import ServiceStack

public class FanSyncFollowsRequest : Codable
{
    public var runId:String?
    public var chunk:Int?
    public var final:Bool?
    public var rows:[FanSyncFollowRow] = []

    required public init(){}
}

public class FanSyncFollowRow : Codable
{
    public var phone:String?
    public var teamNumber:String?
    public var followedAt:String?

    required public init(){}
}

public class FanSyncFollowsResult : Codable
{
    public var runId:String?
    public var received:Int?
    public var kept:Int?
    public var droppedNoOwner:Int?
    public var droppedNotFanPhone:Int?
    public var deduped:Int?
    public var swapped:Bool?
    public var liveRows:Int?
    public var statusCode:Int?
    public var message:String?

    required public init(){}
}

Swift FanSyncFollowsRequest 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 /FanSync/Follows HTTP/1.1 
Host: stubbur-app.azurewebsites.net 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"runId":"String","chunk":0,"final":false,"rows":[{"phone":"String","teamNumber":"String","followedAt":"String"}]}

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

{"runId":"String","received":0,"kept":0,"droppedNoOwner":0,"droppedNotFanPhone":0,"deduped":0,"swapped":false,"liveRows":0,"statusCode":0,"message":"String"}