|
2 | 2 | "openapi": "3.0.1", |
3 | 3 | "info": { |
4 | 4 | "title": "azul-indexer-dev", |
5 | | - "version": "3.3", |
| 5 | + "version": "3.4", |
6 | 6 | "description": "\nThis is the internal API for Azul's indexer component.\n\n\n## Contact us\n\nFor technical support please file an issue at\n[GitHub](https://github.com/DataBiosphere/azul/issues) or email\n`[email protected]`. To report a security concern or misconduct please email\n`[email protected]`.\n" |
7 | 7 | }, |
8 | 8 | "paths": { |
|
16 | 16 | "301": { |
17 | 17 | "description": "A redirect to the Swagger UI" |
18 | 18 | }, |
| 19 | + "429": { |
| 20 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 21 | + }, |
19 | 22 | "504": { |
20 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 23 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
21 | 24 | } |
22 | 25 | } |
23 | 26 | } |
|
32 | 35 | "200": { |
33 | 36 | "description": "The response body is an HTML page containing the Swagger UI" |
34 | 37 | }, |
| 38 | + "429": { |
| 39 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 40 | + }, |
35 | 41 | "504": { |
36 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 42 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
37 | 43 | } |
38 | 44 | } |
39 | 45 | } |
|
48 | 54 | "200": { |
49 | 55 | "description": "The response body is JavaScript used internally by the Swagger UI" |
50 | 56 | }, |
| 57 | + "429": { |
| 58 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 59 | + }, |
51 | 60 | "504": { |
52 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 61 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
53 | 62 | } |
54 | 63 | } |
55 | 64 | } |
|
78 | 87 | "404": { |
79 | 88 | "description": "The requested file does not exist" |
80 | 89 | }, |
| 90 | + "429": { |
| 91 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 92 | + }, |
81 | 93 | "504": { |
82 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 94 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
83 | 95 | } |
84 | 96 | } |
85 | 97 | } |
|
138 | 150 | } |
139 | 151 | } |
140 | 152 | }, |
| 153 | + "429": { |
| 154 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 155 | + }, |
141 | 156 | "504": { |
142 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 157 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
143 | 158 | } |
144 | 159 | }, |
145 | 160 | "tags": [ |
|
186 | 201 | } |
187 | 202 | } |
188 | 203 | }, |
| 204 | + "429": { |
| 205 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 206 | + }, |
189 | 207 | "504": { |
190 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 208 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
191 | 209 | } |
192 | 210 | } |
193 | 211 | } |
|
202 | 220 | "200": { |
203 | 221 | "description": "\nThe robots.txt resource according to\n[RFC9309](https://datatracker.ietf.org/doc/html/rfc9309)\n" |
204 | 222 | }, |
| 223 | + "429": { |
| 224 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 225 | + }, |
205 | 226 | "504": { |
206 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 227 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
207 | 228 | } |
208 | 229 | } |
209 | 230 | } |
|
301 | 322 | } |
302 | 323 | } |
303 | 324 | }, |
| 325 | + "429": { |
| 326 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 327 | + }, |
304 | 328 | "504": { |
305 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 329 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
306 | 330 | } |
307 | 331 | }, |
308 | 332 | "tags": [ |
|
393 | 417 | } |
394 | 418 | } |
395 | 419 | }, |
| 420 | + "429": { |
| 421 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 422 | + }, |
396 | 423 | "504": { |
397 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 424 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
398 | 425 | } |
399 | 426 | }, |
400 | 427 | "tags": [ |
|
491 | 518 | } |
492 | 519 | } |
493 | 520 | }, |
| 521 | + "429": { |
| 522 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 523 | + }, |
494 | 524 | "504": { |
495 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 525 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
496 | 526 | } |
497 | 527 | }, |
498 | 528 | "tags": [ |
|
589 | 619 | } |
590 | 620 | } |
591 | 621 | }, |
| 622 | + "429": { |
| 623 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 624 | + }, |
592 | 625 | "504": { |
593 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 626 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
594 | 627 | } |
595 | 628 | }, |
596 | 629 | "tags": [ |
|
712 | 745 | } |
713 | 746 | } |
714 | 747 | }, |
| 748 | + "429": { |
| 749 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 750 | + }, |
715 | 751 | "504": { |
716 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 752 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
717 | 753 | } |
718 | 754 | }, |
719 | 755 | "tags": [ |
|
824 | 860 | "401": { |
825 | 861 | "description": "Request lacked a valid HMAC header" |
826 | 862 | }, |
| 863 | + "429": { |
| 864 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 865 | + }, |
827 | 866 | "504": { |
828 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 867 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
829 | 868 | } |
830 | 869 | } |
831 | 870 | } |
|
892 | 931 | } |
893 | 932 | } |
894 | 933 | }, |
| 934 | + "429": { |
| 935 | + "description": "Too many requests. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
| 936 | + }, |
895 | 937 | "504": { |
896 | | - "description": "\nRequest timed out. When handling this response, clients\nshould wait the number of seconds specified in the\n`Retry-After` header and then retry the request.\n" |
| 938 | + "description": "Request timed out. \nWhen handling this response, clients should wait the number of\nseconds specified in the `Retry-After` header and then retry the\nrequest.\n" |
897 | 939 | } |
898 | 940 | } |
899 | 941 | } |
|
0 commit comments