forked from SumoLogic/sumologic-documentation
-
Notifications
You must be signed in to change notification settings - Fork 1
/
sumologic-api.yaml
22803 lines (22734 loc) · 777 KB
/
sumologic-api.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
openapi: 3.0.0
info:
title: Sumo Logic API
description: |
## Getting Started
Welcome to the Sumo Logic API reference. You can use these APIs to interact with the Sumo Logic platform. For API information on collectors, search, and more, see [Sumo API Docs](/docs/api).
### API Endpoints
Sumo Logic has several deployments in different geographic locations. See [API endpoints](/docs/api/getting-started#sumo-logic-endpoints-by-deployment-and-firewall-security) for full details on determining the right endpoint for your geographic location.
### Authentication
See [Sumo Logic API authentication](/docs/api/getting-started#authentication) for full details. We support the following options for API authentication:
- Access ID and Access Key
- Base64 encoded Access ID and Access Key
See [Access Keys](/docs/manage/Security/Access-Keys) to generate an Access Key. Make sure to copy the key you create, because it is displayed only once.
When you have an Access ID and Access Key you can execute requests such as the following:
```bash
curl -u "<accessId>:<accessKey>" -X GET https://api.<deployment>.sumologic.com/api/v1/users
```
Where `deployment` is either `au`, `ca`, `de`, `eu`, `fed`, `in`, `jp`, `us1`, or `us2`. See [API endpoints](#section/API-Endpoints) for details.
If you prefer to use basic access authentication, you can do a Base64 encoding of your `<accessId>:<accessKey>` to authenticate your HTTPS request. The following is an example request, replace the placeholder `<encoded>` with your encoded Access ID and Access Key string:
```bash
curl -H "Authorization: Basic <encoded>" -X GET https://api.<deployment>.sumologic.com/api/v1/users
```
Refer to [API Authentication](/docs/api/getting-started#authentication) for a Base64 example.
## Status Codes
For a list of generic status codes that apply to all our APIs, see [Sumo Logic API Status Codes](/docs/api/getting-started#status-codes). See the [HTTP status code registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) for reference.
## Filtering
Some API endpoints support filtering results on a specified set of fields. Each endpoint that supports filtering will list the fields that can be filtered. Multiple fields can be combined by using an ampersand `&` character.
For example, to get 20 users whose `firstName` is `John` and `lastName` is `Doe`:
```bash
api.sumologic.com/v1/users?limit=20&firstName=John&lastName=Doe
```
## Sorting
Some API endpoints support sorting fields by using the `sortBy` query parameter. The default sort order is ascending. Prefix the field with a minus sign `-` to sort in descending order.
For example, to get 20 users sorted by their `email` in descending order:
```bash
api.sumologic.com/v1/users?limit=20&sort=-email
```
## Asynchronous Request
Asynchronous requests do not wait for results, instead they immediately respond back with a job identifier while the job runs in the background. You can use the job identifier to track the status of the asynchronous job request. Here is a typical flow for an asynchronous request.
1. Start an asynchronous job. On success, a job identifier is returned. The job identifier uniquely identifies
your asynchronous job.
2. Once started, use the job identifier from step 1 to track the status of your asynchronous job. An asynchronous
request will typically provide an endpoint to poll for the status of asynchronous job. A successful response
from the status endpoint will have the following structure:
```json
{
"status": "Status of asynchronous request",
"statusMessage": "Optional message with additional information in case request succeeds",
"error": "Error object in case request fails"
}
```
The `status` field can have one of the following values:
1. `Success`: The job succeeded. The `statusMessage` field might have additional information.
2. `InProgress`: The job is still running.
3. `Failed`: The job failed. The `error` field in the response will have more information about the failure.
3. Some asynchronous APIs may provide a third endpoint (like [export result](#operation/getAsyncExportResult))
to fetch the result of an asynchronous job.
### Example
Let's say we want to export a folder with the identifier `0000000006A2E86F`. We will use the [async export](#operation/beginAsyncExport) API to export all the content under the folder with `id=0000000006A2E86F`.
1. Start an export job for the folder
```bash
curl -X POST -u "<accessId>:<accessKey>" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export
```
See [authentication section](#section/Authentication) for more details about `accessId`, `accessKey`, and
`deployment`.
On success, you will get back a job identifier. In the response below, `C03E086C137F38B4` is the job identifier.
```bash
{
"id": "C03E086C137F38B4"
}
```
2. Now poll for the status of the asynchronous job with the [status](#operation/getAsyncExportStatus) endpoint.
```bash
curl -X GET -u "<accessId>:<accessKey>" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export/C03E086C137F38B4/status
```
You may get a response like
```json
{
"status": "InProgress",
"statusMessage": null,
"error": null
}
```
It implies the job is still in progress. Keep polling till the status is either `Success` or `Failed`.
3. When the asynchronous job completes (`status != "InProgress"`), you can fetch the results with the
[export result](#operation/getAsyncExportResult) endpoint.
```bash
curl -X GET -u "<accessId>:<accessKey>" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export/C03E086C137F38B4/result
```
The asynchronous job may fail (`status == "Failed"`). You can look at the `error` field for more details.
```json
{
"status": "Failed",
"errors": {
"code": "content1:too_many_items",
"message": "Too many objects: object count(1100) was greater than limit 1000"
}
}
```
## Rate Limiting
* A rate limit of four API requests per second (240 requests per minute) applies to all API calls from a user.
* A rate limit of 10 concurrent requests to any API endpoint applies to an access key.
If a rate is exceeded, a rate limit exceeded 429 status code is returned.
## Generating Clients
You can use [OpenAPI Generator](https://openapi-generator.tech) to generate clients from the YAML file to access the API.
### Using [NPM](https://www.npmjs.com/get-npm)
1. Install [NPM package wrapper](https://github.com/openapitools/openapi-generator-cli) globally, exposing the CLI
on the command line:
```bash
npm install @openapitools/openapi-generator-cli -g
```
You can see detailed instructions [here](https://openapi-generator.tech/docs/installation#npm).
2. Download the [YAML file](/docs/sumologic-api.yaml) and save it locally. Let's say the file is saved as `sumologic-api.yaml`.
3. Use the following command to generate `python` client inside the `sumo/client/python` directory:
```bash
openapi-generator generate -i sumologic-api.yaml -g python -o sumo/client/python
```
### Using [Homebrew](https://brew.sh/)
1. Install OpenAPI Generator
```bash
brew install openapi-generator
```
2. Download the [YAML file](/docs/sumologic-api.yaml) and save it locally. Let's say the file is saved as `sumologic-api.yaml`.
3. Use the following command to generate `python` client side code inside the `sumo/client/python` directory:
```bash
openapi-generator generate -i sumologic-api.yaml -g python -o sumo/client/python
```
version: 1.0.0
x-logo:
url: ./sumologic_logo.png
servers:
- url: https://api.au.sumologic.com/api/
description: AU deployment API server
- url: https://api.ca.sumologic.com/api/
description: CA deployment API server
- url: https://api.de.sumologic.com/api/
description: DE deployment API server
- url: https://api.eu.sumologic.com/api/
description: EU deployment API server
- url: https://api.fed.sumologic.com/api/
description: FED deployment API server
- url: https://api.jp.sumologic.com/api/
description: JP deployment API server
- url: https://api.in.sumologic.com/api/
description: IN deployment API server
- url: https://api.sumologic.com/api/
description: US1 deployment API server
- url: https://api.us2.sumologic.com/api/
description: US2 deployment API server
security:
- basicAuth: []
tags:
- name: accountManagement
description: |
[Account Management API](docs/api/account-management.md): Manage the custom subdomain for the URL used to access your Sumo Logic account. For more information see [Manage Organization](/docs/manage/01Account_Usage/05Manage_Organization).
x-displayName: Account
- name: appManagement
description: |
App installation API.
View and install Sumo Logic Applications that deliver out-of-the-box dashboards, saved searches, and field extraction for popular data sources. For more information see [Sumo Logic Apps](/docs/integrations).
x-displayName: Apps (Beta)
- name: connectionManagement
description: |
Connection management API.
Set up connections to send alerts to other tools. For more information see [Connections and Integrations](https://help.sumologic.com/?cid=1044).
x-displayName: Connections
- name: contentManagement
description: |
[Content management API](docs/api/content-management.md): You can export, import, delete and copy content in your organization’s Library. For more information see [Library](https://help.sumologic.com/?cid=5173). You can perform the request as a Content Administrator by using the `isAdminMode` parameter. For more information see [Admin Mode](/docs/manage/Content-Sharing/Admin-Mode).
<br/> <br/>
### Example
The following example uses API endpoints in the US1 deployment. Sumo Logic has several deployments that are assigned depending on the geographic location and the date an account is created. For details determining your account's deployment see [API endpoints](https://help.sumologic.com/?cid=3011).
The [Content Import API](#operation/beginAsyncImport) can be used to create or update a Search, Scheduled Search, or Dashboard. Here is an example creating a Scheduled Search:
1. Get the identifier of your `Personal` folder.
```bash
curl -X GET -u "<accessId>:<accessKey>" https://api.sumologic.com/api/v2/content/folders/personal
```
Find the identifier of your `Personal` folder in the response.
```json
{
...
"id": "0000000006A2E86F", <----
"name": "Personal",
"itemType": "Folder",
...
}
```
You can use [getFolder](#operation/getFolder), [getAdminRecommededFolder](#operation/getAdminRecommendedFolderAsync),
or [getGlobalFolder](#operation/getGlobalFolderAsync) endpoints to traverse the content tree and find the identifier of any
folder you want to manage.
2. Use the [Content Import API](#operation/beginAsyncImport) to create a new Scheduled Search inside your
`Personal` folder.
```bash
curl -X POST -u "<accessId>:<accessKey>" -H "Content-Type: application/json" -d @search.json https://api.sumologic.com/api/v2/content/folders/0000000006A2E86F/import
```
The data file `search.json` in the above command has the following `SavedSearchWithScheduleSyncDefinition` object.
```json
// file: search.json
{
"type": "SavedSearchWithScheduleSyncDefinition",
"name": "demo-scheduled-search",
"description": "Runs every hour with timerange of 15m and sends email notifications",
"search": {
"queryText": "\"error\" and \"warn\"",
"defaultTimeRange": "-15m",
"byReceiptTime": false,
"viewName": "",
"viewStartTime": null,
"queryParameters": []
},
"searchSchedule": {
"cronExpression": "0 0/15 * * * ? *",
"displayableTimeRange": "-15m",
"parseableTimeRange": {
"from": {
"relativeTime": "-15m",
"type": "RelativeTimeRangeBoundary"
},
"to": null,
"type": "BeginBoundedTimeRange"
},
"timeZone": "America/Los_Angeles",
"threshold": null,
"notification": {
"taskType": "EmailSearchNotificationSyncDefinition",
"toList": [
"ops@acme.org"
],
"subjectTemplate": "Search Results: {{SearchName}}",
"includeQuery": true,
"includeResultSet": true,
"includeHistogram": true,
"includeCsvAttachment": false
},
"muteErrorEmails": false,
"scheduleType": "1Hour",
"parameters": []
}
}
```
The response of above request will have the job identifier that you can use to track the status of the import job.
```json
{
"id": "74DC17FA765C7443"
}
```
3. Use the job identifier from the import request to get the [status](#operation/getAsyncImportStatus) of the
import job.
```bash
curl -X GET -u "<accessId>:<accessKey>" https://api.sumologic.com/api/v2/content/folders/0000000006A2E86F/import/74DC17FA765C7443/status
```
If you are importing a large item, you might have to wait for the import job to finish. The following is an
example response from a completed job.
```json
{
"status": "Success",
"statusMessage": null,
"error": null
}
```
x-displayName: Content
- name: contentPermissions
description: |
[Content permissions API](docs/api/content-permissions.md): You can share your folders, searches, and dashboards with specific users or roles. For more information see [Share Content](https://help.sumologic.com/?cid=8675309). You can perform the request as a Content Administrator by using the `isAdminMode` parameter. For more information see [Admin Mode](/docs/manage/Content-Sharing/Admin-Mode).
x-displayName: Permissions
- name: dashboardManagement
description: |
[Dashboard (New) management API](docs/api/dashboard-new.md): Dashboard (New) allows you to analyze metric and log data on the same dashboard, in a seamless view. This gives you control over the visual display of metric and log data. Dashboard (New) streamlines dashboard configurations and on-the-fly analytic visualizations with its new templating features. For more information see [Dashboard (New)](https://help.sumologic.com/?cid=5500).
x-displayName: Dashboard (New)
- name: dynamicParsingRuleManagement
description: |
[Dynamic Parsing management API](docs/api/dynamic-parsing.md): Allows automatic field extraction from your log messages when you run a search. This allows you to view fields from logs without having to manually specify parsing logic. For more information, see [Dynamic Parsing](https://help.sumologic.com/?cid=20011).
x-displayName: Dynamic Parsing
- name: extractionRuleManagement
description: |
[Field Extraction Rule management API](docs/api/field-extraction-rules.md): Allow you to parse fields from your log messages at the time the messages are ingested eliminating the need to parse fields in your query. For more information see [Manage Field Extraction](https://help.sumologic.com/?cid=5313).
x-displayName: Field Extraction Rules
- name: fieldManagementV1
description: |
[Field management API](docs/api/fields.md): Fields allow you to reference log data based on meaningful associations. They act as metadata tags that are assigned to your logs so you can search with them. Each field contains a key-value pair, where the field name is the key. Fields may be referred to as Log Metadata Fields. For more information see [Fields](https://help.sumologic.com/?cid=10116).
x-displayName: Field Management
- name: folderManagement
description: |
[Folder management API](docs/api/folders.md): You can add folders and subfolders to the Library in order to organize your content for easy access or to share content. For more information see [Add Folders to the Library](https://help.sumologic.com/?cid=5020). You can perform the request as a Content Administrator by using the `isAdminMode` parameter. For more information see [Admin Mode](/docs/manage/Content-Sharing/Admin-Mode).
x-displayName: Folders
- name: ingestBudgetManagementV1
description: |
[Ingest Budget management API](docs/api/ingest-budget-v1.md): allow you to control the capacity of daily ingestion volume sent to Sumo Logic from Collectors. For more information see [Ingest Budgets](https://help.sumologic.com/?cid=5235).
x-displayName: Ingest Budgets
- name: ingestBudgetManagementV2
description: |
[Ingest Budget management API V2](docs/api/ingest-budget-v2.md): Ingest Budgets V2 provide you the ability to create and assign budgets to your log data by Fields instead of using a Field Value. For more information see [Metadata Ingest Budgets](https://help.sumologic.com/?cid=52352).
x-displayName: Ingest Budgets V2
- name: partitionManagement
description: |
[Partition management API](docs/api/partitions.md): Creating a Partition allows you to improve search performance by searching over a smaller number of messages. For more information see [Manage Partitions](https://help.sumologic.com/?cid=5231).
x-displayName: Partitions
- name: logsDataForwardingManagement
description: |
Logs Data Forwarding management API: allows you to forward log data from a Partition or Scheduled View to an S3 bucket. For more information see [Forwarding Data to S3](/docs/manage/Data-Forwarding/amazon-s3-bucket).
x-displayName: Logs Data Forwarding
- name: roleManagement
description: |
[Role management API](docs/api/roles.md): Roles determine the functions that users are able to perform in Sumo Logic. To manage roles, you must have an administrator role or your role must have been assigned the manage users and roles capability. For more information see [Manage Roles](https://help.sumologic.com/?cid=5234).
x-displayName: Roles
- name: lookupManagement
description: |
[Lookup Table management API](docs/api/lookup-tables.md): A Lookup Table is a table of data hosted on Sumo Logic that you can use to enrich the log and event data received by Sumo Logic. You must create a table schema before you can populate the table. For more information see [Lookup Tables](https://help.sumologic.com/?cid=10109).
x-displayName: Lookup Tables
- name: scheduledViewManagement
description: |
[Scheduled View management API](docs/api/scheduled-views.md): Scheduled Views speed the search process for small and historical subsets of your data by functioning as a pre-aggregated index. For more information see [Manage Scheduled Views](https://help.sumologic.com/?cid=5128).
x-displayName: Scheduled Views
- name: tokensLibraryManagement
description: |
[Tokens management API](docs/api/tokens.md): Tokens are associated with your organization to authorize specific operations. Currently, we support collector registration tokens, which can be used to register Installed Collectors. Managing tokens requires the Manage Tokens role capability. For more information see [Installation Tokens](https://help.sumologic.com/?cid=0100).
x-displayName: Tokens
- name: transformationRuleManagement
description: |
Transformation Rule management API: Metrics Transformation Rules allow you control how long raw metrics are retained. You can also aggregate metrics at collection time and specify a separate retention period for the aggregated metrics. For more information see [Metrics Transformation Rules](https://help.sumologic.com/?cid=10117).
x-displayName: Transformation Rules (Beta)
- name: userManagement
description: |
[User management API](docs/api/users.md): To manage users, you must have the administrator role or your role must have been assigned the manage users and roles capability. For more information see [Manage Users](https://help.sumologic.com/?cid=1006).
x-displayName: Users
- name: metricsSearchesManagement
description: |
[Metrics Search management API](docs/api/metrics.md): Save metrics searches in the content library and organize them in a folder hierarchy. Share useful queries with users in your organization. For more information see [Sharing Metric Charts](/docs/metrics/metric-charts/Share_a_Metric_Chart).
x-displayName: Metrics Searches (Beta)
- name: metricsQuery
description: |
[Metrics Query API](docs/api/metrics-query.md): The Metrics Query API allows you to execute queries on various metrics and retrieve multiple time-series (data-points) over time range(s). For more information see [Metrics - Classic](https://help.sumologic.com/?cid=1079).
x-displayName: Metrics Query
- name: accessKeyManagement
description: |
[Access Key management API](docs/api/access-keys.md): Access Keys allow you to securely register new Collectors and access Sumo Logic APIs. For more information see [Access Keys](https://help.sumologic.com/?cid=6690).
x-displayName: Access Keys
- name: samlConfigurationManagement
description: |
[SAML configuration management API](docs/api/saml.md): Organizations with Enterprise accounts can provision Security Assertion Markup Language (SAML) 2.0 to enable Single Sign-On (SSO) for user access to Sumo Logic. For more information see [SAML Configuration](https://help.sumologic.com/?cid=4016).
x-displayName: SAML Configuration
- name: serviceAllowlistManagement
description: |
[Service Allowlist management API](docs/api/service-allowlist.md): Service Allowlist Settings allow you to explicitly grant access to specific IP addresses and/or CIDR notations for logins, APIs, and dashboard access. For more information see [Service Allowlist Settings](https://help.sumologic.com/?cid=5454).
x-displayName: Service Allowlist
- name: healthEvents
description: |
[Health Events management API](docs/api/health-events.md): Health Events allow you to keep track of the health of your Collectors and Sources. You can use them to find and investigate common errors and warnings that are known to cause collection issues. For more information see [Health Events](https://help.sumologic.com/?cid=0020).
x-displayName: Health Events
- name: archiveManagement
description: |-
[Archive Ingestion Management API](docs/api/archive-ingestion.md): Archive Ingestion allows you to ingest data from Archive destinations. You can use this API to ingest data from your Archive with an existing AWS S3 Archive Source. You need the Manage or View Collectors role capability to manage or view ingestion jobs. For more information see [Archive](https://help.sumologic.com/?cid=10011).
x-displayName: Archive Ingestion Management
- name: logSearchesEstimatedUsage
description: |
Log Search Estimated Usage API: Gets the estimated volume of data that would be scanned for a given log search in the Infrequent data tier, over a particular time range. In the Infrequent Data Tier, you pay per query, based on the amount data scanned. You can use this endpoint to get an estimate of the total data that would be scanned before running a query, and refine your query to scan less data, as necessary. For more information see [Infrequent data tier](https://help.sumologic.com/?cid=11987).
x-displayName: Log Search Estimated Usage
- name: passwordPolicy
description: |
[Password Policy Management API](docs/api/password-policy.md): The password policy controls how user passwords are managed. The "Manage Password Policy" role capability is required to update the password policy. For more information see [how to set a password policy](https://help.sumologic.com/?cid=8595).
x-displayName: Password Policy
- name: policiesManagement
description: |
[Policies management API](docs/api/policies.md): Policies control the security and share settings of your organization. For more information see [Security](https://help.sumologic.com/?cid=4041).
x-displayName: Policies
- name: traces
description: |
[Traces API](docs/api/tracing.md): The Traces API allows you to browse traces collected in the system. You can execute queries to find traces matching provided search criteria as well as gather detailed information about individual traces and spans. For more information see [View and investigate traces](/docs/apm/traces/View_and_investigate_traces).
x-displayName: Traces
- name: spanAnalytics
description: |
Span Analytics API: The Span Analytics API allows you to browse spans collected in the system. You can execute queries to find individual spans matching provided search criteria as well as run aggregated span queries and retrieve their results. For more information see [Spans](/docs/apm/traces/Spans).
x-displayName: Span Analytics
- name: serviceMap
description: |
Service Map API: The Service Map API allows you to fetch a graph representation of the Service Map, which is a high-level view of your application environment, automatically derived from tracing data. For more information see [Service Map](/docs/apm/traces/Service_Map_and_Dashboards#service-map).
x-displayName: Service Map
- name: monitorsLibraryManagement
description: |
[Monitor Management API](docs/api/monitors.md): Monitors continuously query your data to monitor and send notifications when specific events occur.
For more information see [Monitors](https://help.sumologic.com/?cid=10020).
x-displayName: Monitors
- name: slosLibraryManagement
description: |
SLO Management API: SLOs are used to monitor and alert on KPIs for your most important services or user experience.
x-displayName: SLOs
paths:
/v1/apps:
get:
tags:
- appManagement
summary: List available apps.
description: Lists all available apps from the App Catalog.
operationId: listApps
responses:
"200":
description: List of all available apps.
content:
application/json:
schema:
$ref: '#/components/schemas/ListAppsResult'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/apps/{uuid}:
get:
tags:
- appManagement
summary: Get an app by UUID.
description: Gets the app with the given universally unique identifier (UUID).
operationId: getApp
parameters:
- name: uuid
in: path
description: The identifier of the app to retrieve.
required: true
schema:
type: string
format: uuid
responses:
"200":
description: The retrieved app.
content:
application/json:
schema:
$ref: '#/components/schemas/App'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/apps/{uuid}/install:
post:
tags:
- appManagement
summary: Install an app by UUID.
description: Installs the app with given UUID in the folder specified using
destinationFolderId.
operationId: installApp
parameters:
- name: uuid
in: path
description: UUID of the app to install.
required: true
schema:
type: string
format: uuid
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/AppInstallRequest'
required: true
responses:
"200":
description: App install job has been scheduled.
content:
application/json:
schema:
$ref: '#/components/schemas/BeginAsyncJobResponse'
default:
description: App installation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/apps/install/{jobId}/status:
get:
tags:
- appManagement
summary: App install job status.
description: Get the status of an asynchronous app install request for the given
job identifier.
operationId: getAsyncInstallStatus
parameters:
- name: jobId
in: path
description: The identifier of the asynchronous install job.
required: true
schema:
type: string
responses:
"200":
description: The status of the app install job.
content:
application/json:
schema:
$ref: '#/components/schemas/AsyncJobStatus'
default:
description: App installation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/connections:
get:
tags:
- connectionManagement
summary: Get a list of connections.
description: Get a list of all connections in the organization. The response
is paginated with a default limit of 100 connections per page.
operationId: listConnections
parameters:
- name: limit
in: query
description: Limit the number of connections returned in the response. The
number of connections returned may be less than the `limit`.
required: false
schema:
maximum: 1000
minimum: 1
type: integer
format: int32
default: 100
- name: token
in: query
description: Continuation token to get the next page of results. A page object
with the next continuation token is returned in the response body. Subsequent
GET requests should specify the continuation token to get the next page
of results. `token` is set to null when no more pages are left.
required: false
schema:
type: string
responses:
"200":
description: A paginated list of connections in the organization.
content:
application/json:
schema:
$ref: '#/components/schemas/ListConnectionsResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
post:
tags:
- connectionManagement
summary: Create a new connection.
description: Create a new connection in the organization.
operationId: createConnection
parameters: []
requestBody:
description: Information about the new connection.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectionDefinition'
required: true
responses:
"200":
description: The connection has been created.
content:
application/json:
schema:
$ref: '#/components/schemas/Connection'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/connections/test:
post:
tags:
- connectionManagement
summary: Test a new connection url.
description: Test a new connection url is valid and can connect.
operationId: testConnection
parameters: []
requestBody:
description: Information about the new connection.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectionDefinition'
required: true
responses:
"200":
description: The connection url has been tested.
content:
application/json:
schema:
$ref: '#/components/schemas/TestConnectionResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/connections/incidentTemplates:
post:
tags:
- connectionManagement
summary: Get incident templates for CloudSOAR connections.
description: Get incident templates for CloudSOAR connections.
operationId: getIncidentTemplates
parameters: []
requestBody:
description: Information about the new connection.
content:
application/json:
schema:
$ref: '#/components/schemas/GetIncidentTemplatesRequest'
required: false
responses:
"200":
description: A list of the incident templates for the given CloudSOAR account.
content:
application/json:
schema:
$ref: '#/components/schemas/GetIncidentTemplatesResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/connections/{id}:
get:
tags:
- connectionManagement
summary: Get a connection.
description: Get a connection with the given identifier.
operationId: getConnection
parameters:
- name: id
in: path
description: Identifier of connection to return.
required: true
schema:
type: string
- name: type
in: query
description: "Type of connection to return. Valid values are `WebhookConnection`,\
\ `ServiceNowConnection`."
required: true
schema:
type: string
default: WebhookConnection
responses:
"200":
description: Connection object that was requested.
content:
application/json:
schema:
$ref: '#/components/schemas/Connection'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
put:
tags:
- connectionManagement
summary: Update a connection.
description: Update an existing connection.
operationId: updateConnection
parameters:
- name: id
in: path
description: Identifier of the connection to update.
required: true
schema:
type: string
requestBody:
description: Information to update about the connection.
content:
application/json:
schema:
$ref: '#/components/schemas/ConnectionDefinition'
required: true
responses:
"200":
description: The connection was successfully modified.
content:
application/json:
schema:
$ref: '#/components/schemas/Connection'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
delete:
tags:
- connectionManagement
summary: Delete a connection.
description: Delete a connection with the given identifier.
operationId: deleteConnection
parameters:
- name: id
in: path
description: Identifier of the connection to delete.
required: true
schema:
type: string
- name: type
in: query
description: "Type of connection to delete. Valid values are `WebhookConnection`,\
\ `ServiceNowConnection`."
required: true
schema:
pattern: ^(WebhookConnection|ServiceNowConnection)$
type: string
x-pattern-message: must be either `WebhookConnection` or `ServiceNowConnection`
responses:
"204":
description: Connection was deleted successfully.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/scheduledViews:
get:
tags:
- scheduledViewManagement
summary: Get a list of scheduled views.
description: Get a list of all scheduled views in the organization. The response
is paginated with a default limit of 100 scheduled views per page.
operationId: listScheduledViews
parameters:
- name: limit
in: query
description: Limit the number of scheduled views returned in the response.
The number of scheduled views returned may be less than the `limit`.
required: false
schema:
maximum: 1000
minimum: 1
type: integer
format: int32
default: 100
- name: token
in: query
description: Continuation token to get the next page of results. A page object
with the next continuation token is returned in the response body. Subsequent
GET requests should specify the continuation token to get the next page
of results. `token` is set to null when no more pages are left.
required: false
schema:
type: string
responses:
"200":
description: A paginated list of scheduled views in the organization.
content:
application/json:
schema:
$ref: '#/components/schemas/ListScheduledViewsResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
post:
tags:
- scheduledViewManagement
summary: Create a new scheduled view.
description: Creates a new scheduled view in the organization.
operationId: createScheduledView
parameters: []
requestBody:
description: Information about the new scheduled view.
content:
application/json:
schema:
$ref: '#/components/schemas/CreateScheduledViewDefinition'
required: true
responses:
"200":
description: The scheduled view has been created.
content:
application/json:
schema:
$ref: '#/components/schemas/ScheduledView'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-tf-create: createScheduledView
/v1/scheduledViews/{id}:
get:
tags:
- scheduledViewManagement
summary: Get a scheduled view.
description: Get a scheduled view with the given identifier.
operationId: getScheduledView
parameters:
- name: id
in: path
description: Identifier of the scheduled view to fetch.
required: true
schema:
type: string
responses:
"200":
description: Scheduled view object that was requested.
content:
application/json:
schema:
$ref: '#/components/schemas/ScheduledView'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-tf-read: getScheduledView
put:
tags:
- scheduledViewManagement
summary: Update a scheduled view.
description: Update an existing scheduled view.
operationId: updateScheduledView
parameters:
- name: id
in: path
description: Identifier of the scheduled view to update.
required: true
schema:
type: string
requestBody:
description: Information to update about the scheduled view.
content:
application/json:
schema:
$ref: '#/components/schemas/UpdateScheduledViewDefinition'
required: true
responses:
"200":
description: The scheduled view was successfully modified.
content:
application/json:
schema:
$ref: '#/components/schemas/ScheduledView'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-tf-update: updateScheduledView
/v1/scheduledViews/{id}/disable:
delete:
tags:
- scheduledViewManagement
summary: Disable a scheduled view.
description: Disable a scheduled view with the given identifier.
operationId: disableScheduledView
parameters:
- name: id
in: path
description: Identifier of the scheduled view to disable.
required: true
schema:
type: string
responses:
"204":
description: The scheduled view was disabled successfully.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
x-tf-delete: deleteScheduledView
/v1/scheduledViews/{id}/pause:
post:
tags:
- scheduledViewManagement
summary: Pause a scheduled view.
description: Pause a scheduled view with the given identifier.
operationId: pauseScheduledView
parameters:
- name: id
in: path
description: Identifier of the scheduled view to pause.
required: true
schema:
type: string
responses:
"200":
description: The scheduled view was paused successfully.
content:
application/json:
schema:
$ref: '#/components/schemas/ScheduledView'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/scheduledViews/{id}/start:
post:
tags:
- scheduledViewManagement
summary: Start a scheduled view.
description: Start a scheduled view with the given identifier.
operationId: startScheduledView
parameters:
- name: id
in: path
description: Identifier of the scheduled view to start.
required: true
schema:
type: string
responses:
"200":
description: The scheduled view was started successfully.
content:
application/json:
schema:
$ref: '#/components/schemas/ScheduledView'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/lookupTables:
post:
tags:
- lookupManagement
summary: Create a lookup table.
description: |-
Create a new lookup table by providing a schema and specifying its configuration. Providing parentFolderId
is mandatory. Use the [getItemByPath](#operation/getItemByPath) endpoint to get content id of a path.
Please check [Content management API](#tag/contentManagement) and [Folder management API](#tag/folderManagement) for all available options.
operationId: createTable
parameters: []
requestBody:
description: The schema and configuration for the lookup table.
content:
application/json:
schema:
$ref: '#/components/schemas/LookupTableDefinition'
required: true
responses:
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
"200":
description: Lookup table created successfully.
content:
application/json:
schema:
$ref: '#/components/schemas/LookupTable'
/v1/lookupTables/{id}:
get: