TicketUserServices

FanSyncClubsRequest

**Requires Authentication**
Required role:	Admin

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

import datetime
import decimal
from marshmallow.fields import *
from servicestack import *
from typing import *
from dataclasses import dataclass, field
from dataclasses_json import dataclass_json, LetterCase, Undefined, config
from enum import Enum, IntEnum


@dataclass_json(letter_case=LetterCase.CAMEL, undefined=Undefined.EXCLUDE)
@dataclass
class FanSyncClubsResult:
    mapped: Optional[int] = None
    unmapped: Optional[int] = None
    status_code: Optional[int] = None
    message: Optional[str] = None


@dataclass_json(letter_case=LetterCase.CAMEL, undefined=Undefined.EXCLUDE)
@dataclass
class FanSyncTeam:
    team_number: Optional[str] = None
    name: Optional[str] = None
    club_team_number: Optional[str] = None
    club_name: Optional[str] = None


@dataclass_json(letter_case=LetterCase.CAMEL, undefined=Undefined.EXCLUDE)
@dataclass
class FanSyncClubsRequest:
    teams: Optional[List[FanSyncTeam]] = None

Python FanSyncClubsRequest 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/Clubs HTTP/1.1 
Host: stubbur-app.azurewebsites.net 
Accept: application/json
Content-Type: application/json
Content-Length: length

{"teams":[{"teamNumber":"String","name":"String","clubTeamNumber":"String","clubName":"String"}]}

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

{"mapped":0,"unmapped":0,"statusCode":0,"message":"String"}