-
Notifications
You must be signed in to change notification settings - Fork 14
/
betsapi-oas.yaml
2465 lines (2413 loc) · 84.2 KB
/
betsapi-oas.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
swagger: '2.0'
info:
version: 1.0.0
title: Pinnacle - Bets API Reference
description: |
All about bets, place bets, get your bet history or current bet status.
# Authentication
Please note that API has restriction that client password can be maximum up 10 characters long.
API uses HTTP Basic access authentication. You need to send Authorization HTTP Request header:
`Authorization: Basic <Base64 value of UTF-8 encoded "username:password">`
Example:
`Authorization: Basic U03MyOT23YbzMDc6d3c3O1DQ1`
x-logo:
url: 'https://avatars2.githubusercontent.com/u/31601407?s=400&u=f3c6e1cfc8a26665e4a4df6d8da4a7ee527aeceb&v=4'
host: api.pinnacle.com
schemes:
- https
security:
- basicAuth: []
paths:
/v2/bets/straight:
post:
tags:
- Place Bets
summary: Place straight bet - v2
description: |
Place straight bet (SPREAD, MONEYLINE, TOTAL_POINTS, TEAM_TOTAL_POINTS).
Please note when the status is PENDING_ACCEPTANCE and if the live delay was applied, the response will not have betId. Client would have to call /bets by uniqueRequestId to check the status if the bet was ACCEPTED. For more details please see [How to place a bet on live events?](https://github.com/pinnacleapi/pinnacleapi-documentation/blob/master/FAQ.md#how-to-place-a-bet-on-live-events)
Make sure you handle properly the case of an unexpected error as per
[How to handle error on placing a bet?](https://github.com/pinnacleapi/pinnacleapi-documentation/blob/master/FAQ.md#how-to-handle-unexpected-error-on-placing-a-bet)
operationId: Bets_StraightV2
consumes:
- application/json
produces:
- application/json
parameters:
- in: body
name: request
description: ''
required: true
schema:
$ref: '#/definitions/PlaceBetRequest'
responses:
'200':
description: OK
schema:
$ref: '#/definitions/PlaceBetResponseV2'
'400':
description: BadRequest
schema:
$ref: '#/definitions/ErrorResponse'
'401':
description: Unauthorized
schema:
$ref: '#/definitions/ErrorResponse'
'403':
description: Forbidden
schema:
$ref: '#/definitions/ErrorResponse'
'500':
description: InternalServerError
schema:
$ref: '#/definitions/ErrorResponseWithErrorRef'
/v2/bets/parlay:
post:
tags:
- Place Bets
summary: Place parlay bet.
description: |
Make sure you handle properly the case of an unexpected error as per
[How to handle error on placing a bet?](https://github.com/pinnacleapi/pinnacleapi-documentation/blob/master/FAQ.md#how-to-handle-unexpected-error-on-placing-a-bet)
operationId: Bets_ParlayV2
consumes:
- application/json
produces:
- application/json
parameters:
- in: body
name: request
description: The Parlay request.
required: true
schema:
$ref: '#/definitions/PlaceParlayBetRequest'
responses:
'200':
description: OK
schema:
$ref: '#/definitions/PlaceParlayBetResponse'
'400':
description: BadRequest
schema:
$ref: '#/definitions/ErrorResponse'
'401':
description: Unauthorized
schema:
$ref: '#/definitions/ErrorResponse'
'403':
description: Forbidden
schema:
$ref: '#/definitions/ErrorResponse'
'500':
description: InternalServerError
schema:
$ref: '#/definitions/ErrorResponseWithErrorRef'
/v1/bets/teaser:
post:
tags:
- Place Bets
summary: Place teaser bet.
description: |
Make sure you handle properly the case of an unexpected error as per
[How to handle error on placing a bet?](https://github.com/pinnacleapi/pinnacleapi-documentation/blob/master/FAQ.md#how-to-handle-unexpected-error-on-placing-a-bet)
operationId: Bets_Teaser
consumes:
- application/json
produces:
- application/json
parameters:
- in: body
name: request
description: The PlaceTeaser request.
required: true
schema:
$ref: '#/definitions/PlaceTeaserBetRequest'
responses:
'200':
description: OK
schema:
$ref: '#/definitions/PlaceTeaserBetResponse'
'400':
description: BadRequest
schema:
$ref: '#/definitions/ErrorResponse'
'401':
description: Unauthorized
schema:
$ref: '#/definitions/ErrorResponse'
'403':
description: Forbidden
schema:
$ref: '#/definitions/ErrorResponse'
'500':
description: InternalServerError
schema:
$ref: '#/definitions/ErrorResponseWithErrorRef'
/v1/bets/special:
post:
tags:
- Place Bets
summary: Place specials bet.
description: |
Make sure you handle properly the case of an unexpected error as per
[How to handle error on placing a bet?](https://github.com/pinnacleapi/pinnacleapi-documentation/blob/master/FAQ.md#how-to-handle-unexpected-error-on-placing-a-bet)
operationId: Bets_Special
consumes:
- application/json
produces:
- application/json
parameters:
- in: body
name: request
description: The SpecialBet request.
required: true
schema:
$ref: '#/definitions/MultiBetRequest.SpecialBetRequest'
responses:
'200':
description: OK
schema:
$ref: '#/definitions/MultiBetResponse.SpecialBetResponse'
'400':
description: BadRequest
schema:
$ref: '#/definitions/ErrorResponse'
'401':
description: Unauthorized
schema:
$ref: '#/definitions/ErrorResponse'
'403':
description: Forbidden
schema:
$ref: '#/definitions/ErrorResponse'
'500':
description: InternalServerError
schema:
$ref: '#/definitions/ErrorResponseWithErrorRef'
/v3/bets:
get:
tags:
- Get Bets
summary: Get Bets - v3
description: |
Returns bets.
### Get running bets by time range:
```
https://api.pinnacle.com/v3/bets?betlist=RUNNING&fromDate=2017-11-21T00:00:00Z&toDate=2017-11-29T00:00:00Z
```
Running bets are queried by *placedAt* date time
### Get settled bets by time range:
```
https://api.pinnacle.com/v3/bets?betlist=SETTLED&fromDate=2015-12-28T00:00:00Z&toDate=2015-12-29T00:00:00Z
```
Settled bets are queried by *settledAt* date time
https://api.pinnacle.com/v3/bets?betlist=SETTLED&fromDate=2017-11-20T00:00:00Z&toDate=2017-11-23T00:00:00Z
### Get settled cancelled bets by time range:
```
https://api.pinnacle.com/v3/bets?betList=SETTLED&fromDate=2018-03-01&toDate=2018-03-28&betStatuses=CANCELLED
```
### Get bets by bet ids:
```
https://api.pinnacle.com/v3/bets?betIds=775856112,775856113,775856114
```
### Get bets by uniqueRequestIds:
```
https://api.pinnacle.com/v3/bets?uniqueRequestIds=62335222-dae4-479a-8c05-46440ccdd3bb,42335222-dae4-479a-8c05-46440ccdd3bb
```
operationId: Bets_GetBetsByTypeV3
consumes: []
produces:
- application/json
parameters:
- name: betlist
in: query
description: 'Type of bet list to return. Not needed when betids is submitted.'
required: false
type: string
enum:
- SETTLED
- RUNNING
- ALL
- name: betStatuses
in: query
description: 'Type of bet statues to return. This works only in conjustion with betlist, as additional filter.'
required: false
type: array
items:
type: string
enum:
- WON
- LOSE
- CANCELLED
- REFUNDED
- NOT_ACCEPTED
- ACCEPTED
- PENDING_ACCEPTANCE
collectionFormat: csv
- name: fromDate
in: query
description: |
Start date of the requested period. Required when betlist parameter is submitted. Start date can be up to 30 days in the past. Expected format is ISO8601 - can be set to just date or date and time.
required: false
type: string
- name: toDate
in: query
description: |
End date of the requested period. Required when betlist parameter is submitted. Expected format is ISO8601 - can be set to just date or date and time. toDate value is exclusive, meaning it cannot be equal to fromDate.
required: false
type: string
- name: sortDir
in: query
description: 'Sort direction by postedAt/settledAt. Respected only when querying by date range.'
required: false
type: string
enum:
- ASC
- DESC
default: ASC
- name: pageSize
in: query
description: 'Page size in case. Max is 1000. Respected only when querying by date range.'
required: false
type: integer
default: 1000
- name: fromRecord
in: query
description: 'Starting record (inclusive) of the result. Respected only when querying by date range. To fetch next page set it to toRecord+1 '
required: false
type: integer
default: 0
- name: betids
in: query
description: 'A comma separated list of bet ids. When betids is submitted, no other parameter is necessary. Maximum is 100 ids. Works for all non settled bets and all bets settled in the last 30 days.'
required: false
type: array
items:
type: integer
format: int64
collectionFormat: csv
- name: uniqueRequestIds
in: query
description: |
A comma separated list of `uniqueRequestId` from the place bet request. If specified, it's highest priority, all other parameters are ignored. Maximum is 10 ids. If client has bet id, preferred way is to use `betIds` query parameter, you can use `uniqueRequestIds` when you do not have bet id.
That are 2 cases when client may not have a bet id:
1. When you bet on live event with live delay, place bet response in that case does not return bet id, so client can query bet status by `uniqueRequestIds`.
2. In case of any network issues when client is not sure what happened with his place bet request. Empty response means that the bet was not placed. Please check [Deduplication section](https://www.pinnacle.com/de/api/manual#overview) for more details.
Note that there is a restriction: querying by uniqueRequestIds is supported for straight and special bets and only up to 30 min from the moment the bet was place.
required: false
type: array
items:
type: string
collectionFormat: csv
- name: betType
in: query
description: 'A comma separated list of bet types.'
required: false
type: array
items:
type: string
enum:
- SPREAD
- MONEYLINE
- TOTAL_POINTS
- TEAM_TOTAL_POINTS
- SPECIAL
- PARLAY
- TEASER
- MANUAL
responses:
'200':
description: OK
schema:
$ref: '#/definitions/GetBetsByTypeResponseV3'
'400':
description: BadRequest
schema:
$ref: '#/definitions/ErrorResponse'
'401':
description: Unauthorized
schema:
$ref: '#/definitions/ErrorResponse'
'403':
description: Forbidden
schema:
$ref: '#/definitions/ErrorResponse'
'500':
description: InternalServerError
schema:
$ref: '#/definitions/ErrorResponseWithErrorRef'
/v1/bets/betting-status:
get:
tags:
- Betting Status
summary: Get Betting Status
description: 'Returns current betting status. During maintenance windows betting could be disabled, you can call this operation to check the current betting status.'
operationId: Bets_GetBettingStatus
consumes: []
produces:
- application/json
parameters: []
responses:
'200':
description: OK
schema:
$ref: '#/definitions/BettingStatusResponse'
'400':
description: BadRequest
schema:
$ref: '#/definitions/ErrorResponse'
'401':
description: Unauthorized
schema:
$ref: '#/definitions/ErrorResponse'
'403':
description: Forbidden
schema:
$ref: '#/definitions/ErrorResponse'
'500':
description: InternalServerError
schema:
$ref: '#/definitions/ErrorResponseWithErrorRef'
securityDefinitions:
basicAuth:
type: basic
definitions:
PlaceBetRequest:
type: object
properties:
oddsFormat:
$ref: '#/definitions/OddsFormat'
uniqueRequestId:
type: string
format: uuid
example: D5CC50E4-284D-4D50-8D49-429BDC4F2A48
description: This is a Unique ID for PlaceBet requests. This is to support idempotent requests.
acceptBetterLine:
type: boolean
example: true
description: Whether or not to accept a bet when there is a line change in favor of the client.
stake:
type: number
format: double
example: 10.5
description: amount in client’s currency.
winRiskStake:
type: string
example: RISK
description: Whether the stake amount is risk or win amount.
enum:
- WIN
- RISK
lineId:
type: integer
format: int64
example: 420921914
description: Line identification.
altLineId:
type: integer
format: int64
example: null
x-nullable: true
description: Alternate line identification.
fillType:
type: string
description: |
NORMAL - bet will be placed on specified stake.
FILLANDKILL - If the stake is over the max limit, bet will be placed on max limit, otherwise it will be placed on specified stake.
FILLMAXLIMIT - bet will be places on max limit, stake amount will be ignored. Please note that maximum limits can change at any moment, which may result in risking more than anticipated. This option is replacement of isMaxStakeBet from v1/bets/place'
enum:
- NORMAL
- FILLANDKILL
- FILLMAXLIMIT
example: NORMAL
default: NORMAL
sportId:
type: integer
format: int32
example: 29
eventId:
type: integer
format: int64
example: 757504261
periodNumber:
type: integer
format: int32
example: 0
betType:
type: string
example: MONEYLINE
description: 'Bet type.'
enum:
- MONEYLINE
- TEAM_TOTAL_POINTS
- SPREAD
- TOTAL_POINTS
team:
type: string
example: TEAM1
description: 'Team type.'
enum:
- TEAM1
- TEAM2
- DRAW
side:
type: string
example: null
x-nullable: true
description: 'Side type.'
enum:
- OVER
- UNDER
description: Request to place a bet.
ErrorResponse:
type: object
properties:
code:
type: string
description: |
INVALID_REQUEST_DATA = Invalid request parameters (http status 400)
INVALID_CREDENTIALS = Authorization failed, invalid credentials (http status 401)
INVALID_AUTHORIZATION_HEADER = HTTP Authorization header is missing (http status 401)
ACCOUNT_INACTIVE = Client's account is not active (http status 403)
NO_API_ACCESS = Account not permitted to access the API (http status 403)
RESUBMIT_REQUEST = It can happen only when placing a bet (http status 400). Unable to process the request but the request itself is valid. This happens more often on the live betting in situations when there is more than one place bet request at the same on the same line. When this happens, we don't keep the place bet request on the server until we know if we can accept or reject the bet, but instead we return the error. It's also very likely that the line will change after that. To reduce a chance of getting RESUBMIT_REQUEST client should try to place a bet as fast as possible.
enum:
- INVALID_REQUEST_DATA
- INVALID_CREDENTIALS
- INVALID_AUTHORIZATION_HEADER
- ACCOUNT_INACTIVE
- NO_API_ACCESS
- RESUBMIT_REQUEST
message:
type: string
PlaceBetResponseV2:
type: object
properties:
status:
type: string
example: ACCEPTED
description: Status of the response.
enum:
- ACCEPTED
- PENDING_ACCEPTANCE
- PROCESSED_WITH_ERROR
errorCode:
type: string
example: null
x-nullable: true
description: |
If Status is PROCESSED_WITH_ERROR, errorCode will be in the response.
ALL_BETTING_CLOSED = Betting is not allowed at this moment. This may happen during system maintenance,
ALL_LIVE_BETTING_CLOSED = Live betting is not allowed at this moment. This may happen during system maintenance,
ABOVE_EVENT_MAX = Bet cannot be placed because client exceeded allowed maximum of risk on a line,
ABOVE_MAX_BET_AMOUNT = Stake is above allowed maximum amount,
BELOW_MIN_BET_AMOUNT = Stake is below allowed minimum amount,
BLOCKED_BETTING = Betting is suspended for the client,
BLOCKED_CLIENT = Client is no longer active,
INSUFFICIENT_FUNDS = Bet is submitted by a client with insufficient funds,
INVALID_COUNTRY = Client country is not allowed for betting,
INVALID_EVENT = Invalid eventid,
INVALID_ODDS_FORMAT = If a bet was submitted with the odds format that is not allowed for the client,
LINE_CHANGED = Bet is submitted on a line that has changed,
OFFLINE_EVENT = Bet is submitted on an event that is offline or the submitted line is not offered at the moment due to points/handicap change or the submitted bet type is just not offered at the moment,
PAST_CUTOFFTIME = Bet is submitted on a game after the betting cutoff time,
RED_CARDS_CHANGED = Bet is submitted on a live soccer event with changed red card count,
SCORE_CHANGED = Bet is submitted on a live soccer event with changed score,
TIME_RESTRICTION = Bet is submitted within too short of a period from the same bet previously placed by a client,
DUPLICATED_REQUEST = Request with the same uniqueRequestId was already processed. Please set the new value if you still want the request to be processed,
INCOMPLETE_CUSTOMER_BETTING_PROFILE = System configuration issue,
INVALID_CUSTOMER_PROFILE = System configuration issue,
LIMITS_CONFIGURATION_ISSUE = System configuration issue,
RESPONSIBLE_BETTING_LOSS_LIMIT_EXCEEDED = Client has reached his total loss limit,
RESPONSIBLE_BETTING_RISK_LIMIT_EXCEEDED = Client has reached his total risk limit,
SYSTEM_ERROR_3 = Unexpected error,
LICENCE_RESTRICTION_LIVE_BETTING_BLOCKED - Live betting blocked due to licence restrictions,
BETTING_SUSPENDED - Due to anomalous market circumstances bets are not currently being accepted on this line. Try again with next LineId.
enum:
- ALL_BETTING_CLOSED
- ALL_LIVE_BETTING_CLOSED
- ABOVE_EVENT_MAX
- ABOVE_MAX_BET_AMOUNT
- BELOW_MIN_BET_AMOUNT
- BLOCKED_BETTING
- BLOCKED_CLIENT
- INSUFFICIENT_FUNDS
- INVALID_COUNTRY
- INVALID_EVENT
- INVALID_ODDS_FORMAT
- LINE_CHANGED
- OFFLINE_EVENT
- PAST_CUTOFFTIME
- RED_CARDS_CHANGED
- SCORE_CHANGED
- TIME_RESTRICTION
- DUPLICATED_REQUEST
- INCOMPLETE_CUSTOMER_BETTING_PROFILE
- INVALID_CUSTOMER_PROFILE
- LIMITS_CONFIGURATION_ISSUE
- RESPONSIBLE_BETTING_LOSS_LIMIT_EXCEEDED
- RESPONSIBLE_BETTING_RISK_LIMIT_EXCEEDED
- SYSTEM_ERROR_3
- LICENCE_RESTRICTION_LIVE_BETTING_BLOCKED
- BETTING_SUSPENDED
uniqueRequestId:
type: string
example: D5CC50E4-284D-4D50-8D49-429BDC4F2A4
description: Echo of the uniqueRequestId from the request.
straightBet:
$ref: '#/definitions/StraightBet'
description: ''
StraightBet:
type: object
required:
- betId
- betStatus
- betType
- oddsFormat
- placedAt
- risk
- updateSequence
- wagerNumber
- win
properties:
betId:
type: integer
format: int64
example: 759629245
description: Bet identification
wagerNumber:
type: integer
format: int32
example: 1
description: 'Wager identification. All bets placed thru the API will have value 1. Website Classic view supports multiple contest(special) bets placement in the same bet slip in that case the bet would have appropriate wager number, as well as all round robin parlay bets.'
placedAt:
type: string
format: date-time
example: '2017-09-05T01:32:59Z'
description: Date time when the bet was placed.
betStatus:
type: string
example: ACCEPTED
description: |
Bet Status.
ACCEPTED = Bet was accepted,
CANCELLED = Bet is cancelled as per Pinnacle betting rules,
LOSE = The bet is settled as lose,
PENDING_ACCEPTANCE = This status is reserved only for live bets. If a live bet is placed during danger zone or live delay is applied, it will be in PENDING_ACCEPTANCE , otherwise in ACCEPTED status. From this status bet can go to ACCEPTED or NOT_ACCEPTED status,
REFUNDED = When an event is cancelled or when the bet is settled as push, the bet will have REFUNDED status,
NOT_ACCEPTED = Bet was not accepted. Bet can be in this status only if it was previously in PENDING_ACCEPTANCE status,
WON = The bet is settled as won
enum:
- ACCEPTED
- CANCELLED
- LOSE
- PENDING_ACCEPTANCE
- REFUNDED
- NOT_ACCEPTED
- WON
betType:
type: string
example: MONEYLINE
description: 'Bet type.'
enum:
- MONEYLINE
- TEAM_TOTAL_POINTS
- SPREAD
- TOTAL_POINTS
- SPECIAL
- PARLAY
- TEASER
- MANUAL
win:
type: number
format: double
example: 1
description: Win amount.
risk:
type: number
format: double
example: 1.5
description: Risk amount.
winLoss:
type: number
format: double
example: null
x-nullable: true
description: Win-Loss for settled bets.
oddsFormat:
$ref: '#/definitions/OddsFormat'
customerCommission:
type: number
format: double
example: null
x-nullable: true
description: Client’s commission on the bet.
cancellationReason:
$ref: '#/definitions/CancellationReason'
updateSequence:
type: integer
format: int64
example: 111548915
description: Update Sequence
sportId:
type: integer
format: int32
example: 29
description: ''
leagueId:
type: integer
format: int32
example: 2462
description: ''
eventId:
type: integer
format: int64
example: 757064557
description: ''
handicap:
type: number
format: double
example: null
x-nullable: true
description: ''
price:
type: number
format: double
example: -155
description: ''
teamName:
type: string
example: Crvena Zvezda
description: ''
side:
type: string
example: null
x-nullable: true
description: 'Side type.'
enum:
- OVER
- UNDER
team1:
type: string
example: Crvena Zvezda
description: ''
team2:
type: string
example: Partizan
description: ''
periodNumber:
type: integer
format: int32
example: 0
description: ''
team1Score:
type: number
format: double
example: null
x-nullable: true
description: 'Team 1 score on the period that the bet was placed on at the moment of placing a bet, only for live bets.'
team2Score:
type: number
format: double
example: null
x-nullable: true
description: 'Team 2 score on the period that the bet was placed on at the moment of placing a bet, only for live bets.'
ftTeam1Score:
type: number
format: double
example: null
x-nullable: true
description: 'Full time team 1 score, only for settled bets.'
ftTeam2Score:
type: number
format: double
example: null
x-nullable: true
description: 'Full time team 2 score, only for settled bets.'
pTeam1Score:
type: number
format: double
example: null
x-nullable: true
description: '.End of period team 1 score, only for settled bets. If the bet was placed on Game period (periodNumber =0) , this will be null . '
pTeam2Score:
type: number
format: double
example: null
x-nullable: true
description: 'End of period team 2 score, only for settled bets. If the bet was placed on Game period (periodNumber =0), this will be null'
isLive:
type: string
enum:
- TRUE
- FALSE
example: FALSE
description: Whether the bet is on live event
description: ''
StraightBetV3:
type: object
required:
- betId
- betStatus
- betStatus2
- betType
- oddsFormat
- placedAt
- risk
- updateSequence
- wagerNumber
- win
properties:
betId:
type: integer
format: int64
example: 759629245
description: Bet identification
wagerNumber:
type: integer
format: int32
example: 1
description: 'Wager identification. All bets placed thru the API will have value 1. Website Classic view supports multiple contest(special) bets placement in the same bet slip in that case the bet would have appropriate wager number, as well as all round robin parlay bets.'
placedAt:
type: string
format: date-time
example: '2017-09-05T01:32:59Z'
description: Date time when the bet was placed.
betStatus:
type: string
example: ACCEPTED
description: |
Bet Status.
ACCEPTED = Bet was accepted,
CANCELLED = Bet is cancelled as per Pinnacle betting rules,
LOSE = The bet is settled as lose,
PENDING_ACCEPTANCE = This status is reserved only for live bets. If a live bet is placed during danger zone or live delay is applied, it will be in PENDING_ACCEPTANCE , otherwise in ACCEPTED status. From this status bet can go to ACCEPTED or NOT_ACCEPTED status,
REFUNDED = When an event is cancelled or when the bet is settled as push, the bet will have REFUNDED status,
NOT_ACCEPTED = Bet was not accepted. Bet can be in this status only if it was previously in PENDING_ACCEPTANCE status,
WON = The bet is settled as won
enum:
- ACCEPTED
- CANCELLED
- LOSE
- PENDING_ACCEPTANCE
- REFUNDED
- NOT_ACCEPTED
- WON
betStatus2:
type: string
example: ACCEPTED
description: |
Bet Status.
ACCEPTED = Bet was accepted.
CANCELLED = Bet is cancelled as per Pinnacle betting rules.
LOST = The bet is settled as lose.
PENDING_ACCEPTANCE = This status is reserved only for live bets. If a live bet is placed during danger zone or live delay is applied, it will be in PENDING_ACCEPTANCE , otherwise in ACCEPTED status. From this status bet can go to ACCEPTED or NOT_ACCEPTED status.
REFUNDED = When an event is cancelled or when the bet is settled as push, the bet will have REFUNDED status.
NOT_ACCEPTED = Bet was not accepted. Bet can be in this status only if it was previously in PENDING_ACCEPTANCE status.
WON = The bet is settled as won.
HALF_WON_HALF_PUSHED = The bet is settled as half won half pushed. Only for asian handicap bets.
HALF_LOST_HALF_PUSHED = The bet is settled as half lost half pushed. Only for asian handicap bets.
enum:
- ACCEPTED
- CANCELLED
- LOST
- PENDING_ACCEPTANCE
- REFUNDED
- NOT_ACCEPTED
- WON
- HALF_WON_HALF_PUSHED
- HALF_LOST_HALF_PUSHED
betType:
type: string
example: MONEYLINE
description: 'Bet type.'
enum:
- MONEYLINE
- TEAM_TOTAL_POINTS
- SPREAD
- TOTAL_POINTS
- SPECIAL
- PARLAY
- TEASER
- MANUAL
win:
type: number
format: double
example: 1
description: Win amount.
risk:
type: number
format: double
example: 1.5
description: Risk amount.
winLoss:
type: number
format: double
example: null
x-nullable: true
description: Win-Loss for settled bets.
oddsFormat:
$ref: '#/definitions/OddsFormat'
customerCommission:
type: number
format: double
example: null
x-nullable: true
description: Client’s commission on the bet.
cancellationReason:
$ref: '#/definitions/CancellationReason'
updateSequence:
type: integer
format: int64
example: 111548915
description: Update Sequence
sportId:
type: integer
format: int32
example: 29
description: ''
leagueId:
type: integer
format: int32
example: 2462
description: ''
eventId:
type: integer
format: int64
example: 757064557
description: ''
handicap:
type: number
format: double
example: null
x-nullable: true
description: ''
price:
type: number
format: double
example: -155
description: ''
teamName:
type: string
example: Crvena Zvezda
description: ''
side:
type: string
example: null
x-nullable: true
description: 'Side type.'
enum:
- OVER
- UNDER
team1:
type: string
example: Crvena Zvezda
description: ''
team2:
type: string
example: Partizan
description: ''
periodNumber:
type: integer
format: int32
example: 0
description: ''
team1Score:
type: number
format: double
example: null
x-nullable: true
description: 'Team 1 on the period that the bet was placed on at the moment of placing a bet, only for live bets.'
team2Score:
type: number
format: double
example: null
x-nullable: true
description: 'Team 2 on the period that the bet was placed on at the moment of placing a bet, only for live bets.'
ftTeam1Score:
type: number
format: double
example: null
x-nullable: true
description: 'Full time team 1 score, only for settled bets.'
ftTeam2Score:
type: number
format: double
example: null
x-nullable: true
description: 'Full time team 2 score, only for settled bets.'
pTeam1Score:
type: number
format: double
example: null
x-nullable: true
description: '.End of period team 1 score, only for settled bets. If the bet was placed on Game period (periodNumber =0), this will be null . '
pTeam2Score:
type: number
format: double
example: null
x-nullable: true
description: 'End of period team 2 score, only for settled bets. If the bet was placed on Game period (periodNumber =0), this will be null'
isLive:
type: boolean
example: false
description: Whether the bet is on live event
eventStartTime:
type: string
format: date-time
example: '2017-10-05T01:32:59Z'
description: Date time when the event starts.
resultingUnit: