-
Notifications
You must be signed in to change notification settings - Fork 0
/
swagger.yaml
365 lines (362 loc) · 12 KB
/
swagger.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
openapi: 3.0.0
info:
title: Stocks API
description: This API has been created to support assignment work in the QUT Web Computing units for 2020. It exposes a small number of REST endpoints which implement CRUD operations on a database containing a snapshot of publicly available stock price data. The database includes entries - over a limited time frame - for a selected number of companies listed on our example Stock Exchange. There are three Query endpoints - `GET`s to allow you to retrieve data from the database - and two `POST` endpoints to manager User registration and login. Each of these endpoints is fairly straight forward and their usage is documented below. Note that the `/stocks` and `/stocks/authed` endpoints are similar in principle, but the latter endpoint offers additional functionality - the ability to select data based on a date range - that is available only to authenticated users. **_Note:_** All non-path query parameters are _optional_ and _must_ be lower case.
version: 1.0.0
components:
securitySchemes:
bearerAuth: # arbitrary name for the security scheme
type: http
scheme: bearer
bearerFormat: JWT
servers:
- url: http://131.181.190.87:3000
paths:
/stocks/symbols:
get:
summary: Returns all available stocks, optionally filtered by industry sector.
tags: [Queries]
parameters:
- in: query
name: industry
required: false
schema:
type: string
description: Sector or part thereof e.g. Information or mation will match Information Technology
responses:
"200":
description: A JSON array of stock listing objects comprising name, symbol and industry sector
content:
application/json:
schema:
type: array
items:
type: object
properties:
name:
type: string
example: Agilent Technologies Inc
symbol:
type: string
example: A
industry:
type: string
example: Health Care
"400":
description: Invalid query parameter
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: Invalid query parameter: only 'industry' is permitted
"404":
description: Industry sector not found
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: Industry sector not found
/stocks/{symbol}:
get:
summary: Returns the latest entry for a particular stock searched by symbol (1-5 upper case letters).
tags: [Queries]
parameters:
- in: path
name: symbol
required: true
description: The exchange symbol of the stock
schema:
type: string
example: AAL
responses:
"200":
description: A stock object
content:
application/json:
schema:
type: object
properties:
timestamp:
type: string
example: 2020-03-22T14:00:00.000Z
symbol:
type: string
example: AAL
name:
type: string
example: American Airlines Group
industry:
type: string
example: Industrials
open:
type: number
example: 10.9
high:
type: number
example: 11.36
low:
type: number
example: 10.01
close:
type: number
example: 10.25
volumes:
type: number
example: 55491000
"400":
description: Invalid query parameter(s)
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: Date parameters only available on authenticated route /stocks/authed
"404":
description: No entry for the symbol found in the stocks database.
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: No entry for symbol in stocks database
/stocks/authed/{symbol}:
get:
security:
- bearerAuth: []
summary: Return entries of stock searched by symbol, optionally filtered by date.
tags: [Queries]
parameters:
- in: path
name: symbol
required: true
description: The exchange symbol of the stock
schema:
type: string
example: AAL
- in: query
name: from
description: Starting date of entries. Needs to be a string parsable for Date.Parse()
schema:
type: string
example: 2020-03-15
- in: query
name: to
description: Finishing date of entries. Needs to be a string parsable for Date.Parse()
schema:
type: string
example: 2020-03-20
responses:
"200":
description: One or more stock entries that meet the search criteria. By default, the response will be a single object. It at least one valid to or from query is supplied with a valid date then the response will be an array of stock objects.
content:
application/json:
schema:
type: object
properties:
timestamp:
type: string
example: 2020-03-22T14:00:00.000Z
symbol:
type: string
example: AAL
name:
type: string
example: American Airlines Group
industry:
type: string
example: Industrials
open:
type: number
example: 10.9
high:
type: number
example: 11.36
low:
type: number
example: 10.01
close:
type: number
example: 10.25
volumes:
type: number
example: 55491000
"400":
description: Invalid query parameter or date format
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: Parameters allowed are 'from' and 'to', example: /stocks/authed/AAL?from=2020-03-15
"403":
description: Access denied
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: Authorization header not found
"404":
description: Queried data not found
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: No entries available for query symbol for supplied date range
/user/register:
post:
summary: Create a new user account
tags: [Users]
requestBody:
description: User object to be registered
required: true
content:
application/json:
schema:
type: object
properties:
email:
type: string
example: [email protected]
password:
type: string
example: asdlkfj1
responses:
"201":
description: User created
content:
application/json:
schema:
type: object
properties:
success:
type: boolean
example: true
message:
type: string
example: User created
"400":
description: Bad request
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: Request body incomplete - email and password needed
"409":
description: User already exists
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: User already exists!
/user/login:
post:
summary: Log in to existing account
tags: [Users]
requestBody:
description: User object used to log in
required: true
content:
application/json:
schema:
type: object
properties:
email:
type: string
example: [email protected]
password:
type: string
example: asdlkfj1
responses:
"200":
description: Log in successful
content:
application/json:
schema:
type: object
properties:
token:
type: string
example: afakejsonwebtoken
token_type:
type: string
example: Bearer
expires:
type: number
example: 86400
"401":
description: Log in failed
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: Incorrect email or password
"400":
description: Invalid log in request
content:
application/json:
schema:
type: object
properties:
error:
type: boolean
example: true
message:
type: string
example: Request body invalid - email and password are required