Account Management API. Manage the custom subdomain for the URL used to access your Sumo Logic account. For more information, see [Manage Organization](https://help.sumologic.com/docs/manage/manage-subscription/manage-org-settings).
openapi: 3.0.0
info:
title: Sumo Logic accessKeyManagement accountManagement API
description: "# Getting Started\nWelcome to the Sumo Logic API reference. You can use these APIs to interact with the Sumo Logic platform. For information on Collector and Search Job APIs, see our [API home page](https://help.sumologic.com/docs/api).\n## API Endpoints\nSumo Logic has several deployments in different geographic locations. You'll need to use the Sumo Logic API endpoint corresponding to your geographic location. See the table below for the different API endpoints by deployment. For details determining your account's deployment, see [API endpoints](https://help.sumologic.com/?cid=3011).\n\n <table>\n <tr>\n <td> <strong>Deployment</strong> </td>\n <td> <strong>Endpoint</strong> </td>\n </tr>\n <tr>\n <td> AU </td>\n <td> https://api.au.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> CA </td>\n <td> https://api.ca.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> DE </td>\n <td> https://api.de.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> EU </td>\n <td> https://api.eu.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> FED </td>\n <td> https://api.fed.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> IN </td>\n <td> https://api.in.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> JP </td>\n <td> https://api.jp.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> KR </td>\n <td> https://api.kr.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> US1 </td>\n <td> https://api.sumologic.com/api/ </td>\n </tr>\n <tr>\n <td> US2 </td>\n <td> https://api.us2.sumologic.com/api/ </td>\n </tr>\n </table>\n\n## Authentication\nSumo Logic supports the following options for API authentication:\n- Access ID and Access Key\n- Base64 encoded Access ID and Access Key\n\nSee [Access Keys](https://help.sumologic.com/docs/manage/security/access-keys) to generate an Access Key. Make sure to copy the key you create, because it is displayed only once.\nWhen you have an Access ID and Access Key you can execute requests such as the following:\n ```bash\n curl -u \"<accessId>:<accessKey>\" -X GET https://api.<deployment>.sumologic.com/api/v1/users\n ```\n\nWhere `deployment` is either `au`, `ca`, `de`, `eu`, `fed`, `in`, `jp`, `us1`, or `us2`. See [API endpoints](#section/API-Endpoints) for details.\n\nIf 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:\n ```bash\n curl -H \"Authorization: Basic <encoded>\" -X GET https://api.<deployment>.sumologic.com/api/v1/users\n ```\n\n\nRefer to [API Authentication](https://help.sumologic.com/?cid=3012) for a Base64 example.\n\n## Status Codes\nGeneric status codes that apply to all our APIs. See the [HTTP status code registry](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) for reference.\n <table>\n <tr>\n <td> <strong>HTTP Status Code</strong> </td>\n <td> <strong>Error Code</strong> </td>\n <td> <strong>Description</strong> </td>\n </tr>\n <tr>\n <td> 301 </td>\n <td> moved </td>\n <td> The requested resource SHOULD be accessed through returned URI in Location Header. See [troubleshooting](https://help.sumologic.com/docs/api/troubleshooting/#api---301-error---moved) for details.</td>\n </tr>\n <tr>\n <td> 401 </td>\n <td> unauthorized </td>\n <td> Credential could not be verified.</td>\n </tr>\n <tr>\n <td> 403 </td>\n <td> forbidden </td>\n <td> This operation is not allowed for your account type or the user doesn't have the role capability to perform this action. See [troubleshooting](https://help.sumologic.com/docs/api/troubleshooting/#api---401-error---credential-could-not-be-verified) for details.</td>\n </tr>\n <tr>\n <td> 404 </td>\n <td> notfound </td>\n <td> Requested resource could not be found. </td>\n </tr>\n <tr>\n <td> 405 </td>\n <td> method.unsupported </td>\n <td> Unsupported method for URL. </td>\n </tr>\n <tr>\n <td> 415 </td>\n <td> contenttype.invalid </td>\n <td> Invalid content type. </td>\n </tr>\n <tr>\n <td> 429 </td>\n <td> rate.limit.exceeded </td>\n <td> The API request rate is higher than 4 request per second or inflight API requests are higher than 10 request per second. </td>\n </tr>\n <tr>\n <td> 500 </td>\n <td> internal.error </td>\n <td> Internal server error. </td>\n </tr>\n <tr>\n <td> 503 </td>\n <td> service.unavailable </td>\n <td> Service is currently unavailable. </td>\n </tr>\n </table>\n\n## Filtering\nSome 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.\n\nExample: To get user with email `john@demo.com`:\n ```bash\n api.sumologic.com/v1/users?email=john@demo.com\n ```\n\n## Sorting\nSome 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.\n\nFor example, to get 20 users sorted by their `email` in descending order:\n ```bash\n api.sumologic.com/v1/users?limit=20&sort=-email\n ```\n\n## Asynchronous Request\nAsynchronous 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.\n1. Start an asynchronous job. On success, a job identifier is returned. The job identifier uniquely identifies\n your asynchronous job.\n\n2. Once started, use the job identifier from step 1 to track the status of your asynchronous job. An asynchronous\n request will typically provide an endpoint to poll for the status of asynchronous job. A successful response\n from the status endpoint will have the following structure:\n ```json\n {\n \"status\": \"Status of asynchronous request\",\n \"statusMessage\": \"Optional message with additional information in case request succeeds\",\n \"error\": \"Error object in case request fails\"\n }\n ```\n The `status` field can have one of the following values:\n 1. `Success`: The job succeeded. The `statusMessage` field might have additional information.\n 2. `InProgress`: The job is still running.\n 3. `Failed`: The job failed. The `error` field in the response will have more information about the failure.\n\n3. Some asynchronous APIs may provide a third endpoint (like [export result](#operation/getAsyncExportResult))\n to fetch the result of an asynchronous job.\n\n\n### Example\nLet'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`.\n1. Start an export job for the folder\n ```bash\n curl -X POST -u \"<accessId>:<accessKey>\" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export\n ```\n See [authentication section](#section/Authentication) for more details about `accessId`, `accessKey`, and\n `deployment`.\n On success, you will get back a job identifier. In the response below, `C03E086C137F38B4` is the job identifier.\n ```bash\n {\n \"id\": \"C03E086C137F38B4\"\n }\n ```\n\n2. Now poll for the status of the asynchronous job with the [status](#operation/getAsyncExportStatus) endpoint.\n ```bash\n curl -X GET -u \"<accessId>:<accessKey>\" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export/C03E086C137F38B4/status\n ```\n You may get a response like\n ```json\n {\n \"status\": \"InProgress\",\n \"statusMessage\": null,\n \"error\": null\n }\n ```\n It implies the job is still in progress. Keep polling till the status is either `Success` or `Failed`.\n\n3. When the asynchronous job completes (`status != \"InProgress\"`), you can fetch the results with the\n [export result](#operation/getAsyncExportResult) endpoint.\n ```bash\n curl -X GET -u \"<accessId>:<accessKey>\" https://api.<deployment>.sumologic.com/api/v2/content/0000000006A2E86F/export/C03E086C137F38B4/result\n ```\n\n The asynchronous job may fail (`status == \"Failed\"`). You can look at the `error` field for more details.\n ```json\n {\n \"status\": \"Failed\",\n \"errors\": {\n \"code\": \"content1:too_many_items\",\n \"message\": \"Too many objects: object count(1100) was greater than limit 1000\"\n }\n }\n ```\n\n\n## Rate Limiting\n* A rate limit of four API requests per second (240 requests per minute) applies to all API calls from a user.\n* A rate limit of 10 concurrent requests to any API endpoint applies to an access key.\n\nIf a rate is exceeded, a rate limit exceeded 429 status code is returned.\n\n## Generating Clients\nYou can use [OpenAPI Generator](https://openapi-generator.tech) to generate clients from the YAML file to access the API.\n\n### Using [NPM](https://www.npmjs.com/get-npm)\n1. Install [NPM package wrapper](https://github.com/openapitools/openapi-generator-cli) globally, exposing the CLI\n on the command line:\n ```bash\n npm install @openapitools/openapi-generator-cli -g\n ```\n You can see detailed instructions [here](https://openapi-generator.tech/docs/installation#npm).\n\n2. Download the [YAML file](/docs/sumologic-api.yaml) and save it locally. Let's say the file is saved as `sumologic-api.yaml`.\n3. Use the following command to generate `python` client inside the `sumo/client/python` directory:\n ```bash\n openapi-generator generate -i sumologic-api.yaml -g python -o sumo/client/python\n ```\n\n\n### Using [Homebrew](https://brew.sh/)\n1. Install OpenAPI Generator\n ```bash\n brew install openapi-generator\n ```\n\n2. Download the [YAML file](/docs/sumologic-api.yaml) and save it locally. Let's say the file is saved as `sumologic-api.yaml`.\n3. Use the following command to generate `python` client side code inside the `sumo/client/python` directory:\n ```bash\n openapi-generator generate -i sumologic-api.yaml -g python -o sumo/client/python\n ```\n"
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.kr.sumologic.com/api/
description: KR 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.
Manage the custom subdomain for the URL used to access your Sumo Logic account. For more information, see [Manage Organization](https://help.sumologic.com/docs/manage/manage-subscription/manage-org-settings).
'
x-displayName: Account
paths:
/v1/account/accountOwner:
get:
tags:
- accountManagement
summary: Get The Owner Of An Account.
description: Returns the user identifier of the account owner.
operationId: getAccountOwner
responses:
'200':
description: User identifier of the account owner.
content:
application/json:
schema:
type: string
example: 00000000000001E7
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/account/status:
get:
tags:
- accountManagement
summary: Get Overview Of The Account Status.
description: Get information related to the account's plan, pricing model, expiration and payment status.
operationId: getStatus
responses:
'200':
description: Overview of the account.
content:
application/json:
schema:
$ref: '#/components/schemas/AccountStatusResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/account/subdomain:
get:
tags:
- accountManagement
summary: Get The Configured Subdomain.
description: Get the configured subdomain.
operationId: getSubdomain
responses:
'200':
description: The subdomain's definition.
content:
application/json:
schema:
$ref: '#/components/schemas/SubdomainDefinitionResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
put:
tags:
- accountManagement
summary: Update Account Subdomain.
description: Update a subdomain. Only the Account Owner can update the subdomain.
operationId: updateSubdomain
requestBody:
description: The new subdomain.
content:
application/json:
schema:
$ref: '#/components/schemas/ConfigureSubdomainRequest'
required: true
responses:
'200':
description: The updated subdomain's definition.
content:
application/json:
schema:
$ref: '#/components/schemas/SubdomainDefinitionResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
post:
tags:
- accountManagement
summary: Create Account Subdomain.
description: Create a subdomain. Only the Account Owner can create a subdomain.
operationId: createSubdomain
requestBody:
description: The new subdomain.
content:
application/json:
schema:
$ref: '#/components/schemas/ConfigureSubdomainRequest'
required: true
responses:
'200':
description: Created a new subdomain.
content:
application/json:
schema:
$ref: '#/components/schemas/SubdomainDefinitionResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
delete:
tags:
- accountManagement
summary: Delete The Configured Subdomain.
description: Delete the configured subdomain.
operationId: deleteSubdomain
responses:
'204':
description: The subdomain was successfully deleted.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/account/subdomain/recover:
post:
tags:
- accountManagement
summary: Recover Subdomains For A User.
description: Send an email with the subdomain information for a user with the given email address.
operationId: recoverSubdomains
parameters:
- name: email
in: query
description: Email address of the user to get subdomain information.
required: true
schema:
type: string
responses:
'204':
description: An email containing information about associated subdomains for the given email was sent.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/account/usage/report:
post:
tags:
- accountManagement
summary: Export Credits Usage Details As CSV.
description: Export the credit usage details as csv for the specific period of time given as input in the form of a start and end date with a specific grouping according to `day`, `week`, `month`, Note that this API will work only for credits plan customers.
operationId: exportUsageReport
requestBody:
description: Export Usage Report Request.
content:
application/json:
schema:
$ref: '#/components/schemas/UsageReportRequest'
required: true
responses:
'200':
description: Export Response with Job Id.
content:
application/json:
schema:
$ref: '#/components/schemas/UsageReportResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/account/usage/report/{jobId}/status:
get:
tags:
- accountManagement
summary: Get Report Generation Status.
description: Get the report download URL and status using Job Id.
operationId: getStatusForReport
parameters:
- name: jobId
in: path
description: Job Id for the report to be exported.
required: true
schema:
type: string
responses:
'200':
description: Status response containing status and downloadURL if successful.
content:
application/json:
schema:
$ref: '#/components/schemas/UsageReportStatusResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/account/usageForecast:
get:
tags:
- accountManagement
summary: Get Usage Forecast With Respect To Last Number Of Days Specified.
description: Get usage forecast with respect to last number of days specified. If nothing is provided for last number of days, the average of term period will be taken to do the forecast.
operationId: getUsageForecast
parameters:
- name: numberOfDays
in: query
description: Number of days to use for calculating average usage and forecast.
required: false
schema:
type: number
responses:
'200':
description: Usage Forecast.
content:
application/json:
schema:
$ref: '#/components/schemas/UsageForecastResponse'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
/v1/plan/pendingUpdateRequest:
get:
tags:
- accountManagement
summary: Get The Pending Plan Update Request, If Any.
description: Get the pending plan update request which will be applicable from next billing cycle.
operationId: getPendingUpdateRequest
responses:
'200':
description: Pending plan update request.
content:
application/json:
schema:
$ref: '#/components/schemas/PendingUpdateRequest'
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
delete:
tags:
- accountManagement
summary: Delete The Pending Plan Update Request, If Any.
description: Delete the pending plan update request which would be applicable from next billing cycle.
operationId: deletePendingUpdateRequest
responses:
'204':
description: Deleted the pending update request.
default:
description: Operation failed with an error.
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
components:
schemas:
SubdomainDefinitionResponse:
required:
- createdAt
- createdBy
- modifiedAt
- modifiedBy
- subdomain
- url
type: object
properties:
createdAt:
type: string
description: 'Creation timestamp in UTC in [RFC3339](https://tools.ietf.org/html/rfc3339) format.
'
format: date-time
createdBy:
type: string
description: Identifier of the user who created the resource.
modifiedAt:
type: string
description: Last modification timestamp in UTC.
format: date-time
modifiedBy:
type: string
description: Identifier of the user who last modified the resource.
subdomain:
type: string
description: The new subdomain.
example: my-company
url:
type: string
description: Login URL corresponding to the subdomain.
example: https://your-company.sumologic.com
AccountStatusResponse:
required:
- applicationUse
- canUpdatePlan
- planType
- pricingModel
type: object
properties:
pricingModel:
pattern: ^(credits|cloudflex)$
type: string
description: Whether the account is `cloudflex` or `credits`
example: credits
canUpdatePlan:
type: boolean
description: If the plan can be updated by the given user
example: true
planType:
pattern: ^(Free|Trial|Paid)$
type: string
description: Whether the account is `Free`/`Trial`/`Paid`
example: Free
planExpirationDays:
type: integer
description: The number of days in which the plan will expire
example: 20
applicationUse:
pattern: ^(ALLOWED|ALLOWED_WITH_WARNING|THROTTLED|RESTRICTED)$
type: string
description: The current usage of the application.
example: ALLOWED
accountActivated:
type: boolean
description: If the account is activated or not
example: true
totalCredits:
type: integer
description: Total amount of credits assigned to the account
example: 400
logModel:
pattern: ^(Flex|Tiered|FlexPlusTiered)$
type: string
description: The log model of the account
example: Flex
description: Information about the account's plan and payment.
ErrorResponse:
required:
- errors
- id
type: object
properties:
id:
type: string
description: An identifier for the error; this is unique to the specific API request.
example: IUUQI-DGH5I-TJ045
errors:
type: array
description: A list of one or more causes of the error.
example:
- code: auth:password_too_short
message: Your password was too short.
- code: auth:password_character_classes
message: Your password did not contain any non-alphanumeric characters
items:
$ref: '#/components/schemas/ErrorDescription'
CurrentPlan:
required:
- billingFrequency
- planCost
- productId
type: object
properties:
productId:
pattern: ^(Essentials|Trial|Free|EnterpriseOps|EnterpriseSec|EnterpriseSuite)$
type: string
description: 'Unique identifier of the product in current plan. Valid values are: 1. `Free` 2. `Trial` 3. `Essentials` 4. `EnterpriseOps` 5. `EnterpriseSec` 6. `EnterpriseSuite`
'
example: Essentials
x-pattern-message: 'must be one of the following: `Essentials`, `Trial`, `Free`, `EnterpriseOps`, `EnterpriseSec`, `EnterpriseSuite`'
planCost:
type: number
description: Cost incurred for the current plan.
format: double
example: 725.46
billingFrequency:
pattern: ^(Monthly|Annually)$
type: string
description: 'Billing frequency for the current plan. Valid values are: 1. `Monthly` 2. `Annually`
'
example: Monthly
x-pattern-message: 'must be one of the following: `Monthly` or `Annually`'
consumables:
type: array
description: Consumables in the current plan.
items:
$ref: '#/components/schemas/Consumable'
planType:
pattern: ^(Free|Trial|Paid)$
type: string
description: Whether the account is `Free`/`Trial`/`Paid`
example: Free
x-pattern-message: 'must be one of the following: `Free`, `Trial` or `Paid`'
planName:
type: string
description: The plan name for the product being used.
discountAmount:
type: integer
description: The discount offered for the given contract period.
contractPeriod:
$ref: '#/components/schemas/ContractPeriod'
currentBillingPeriod:
$ref: '#/components/schemas/CurrentBillingPeriod'
credits:
type: integer
description: Numerical value of the amount of credits
format: int64
example: 300
baselines:
$ref: '#/components/schemas/Baselines'
pendingUpdateRequest:
type: boolean
description: True if there is a pending update request
prorationDetails:
$ref: '#/components/schemas/ProrationDetails'
description: Current plan of the account.
Baselines:
type: object
properties:
continuousIngest:
maximum: 1000000
minimum: 0
type: integer
description: The amount of continuous logs ingest to allocate to the organization, in GBs.
format: int64
example: 50000
default: 0
continuousStorage:
maximum: 30
minimum: 30
type: integer
description: Number of days of continuous logs storage to allocate to the organization, in Days.
format: int64
example: 30
default: 30
frequentIngest:
maximum: 1000000
minimum: 0
type: integer
description: The amount of frequent logs ingest to allocate to the organization, in GBs.
format: int64
example: 50000
default: 0
frequentStorage:
maximum: 30
minimum: 30
type: integer
description: Number of days of frequent logs storage to allocate to the organization, in Days.
format: int64
example: 30
default: 30
infrequentIngest:
maximum: 1000000
minimum: 0
type: integer
description: The amount of infrequent logs ingest to allocate to the organization, in GBs.
format: int64
example: 50000
default: 0
infrequentStorage:
maximum: 30
minimum: 30
type: integer
description: The amount of infrequent logs storage to allocate to the organization, in Days.
format: int64
example: 30
default: 30
infrequentScan:
maximum: 1000000
minimum: 0
type: integer
description: The amount of infrequent logs scan to allocate to the organization, in GBs.
format: int64
example: 50000
default: 0
metrics:
maximum: 5000000
minimum: 0
type: integer
description: The amount of Metrics usage to allocate to the organization, in DPMs (Data Points per Minute).
format: int64
example: 50000
default: 0
cseIngest:
maximum: 1000000
minimum: 0
type: integer
description: The amount of CSE ingest to allocate to the organization, in GBs.
format: int64
example: 50000
default: 0
cseStorage:
maximum: 1000000
minimum: 0
type: integer
description: The amount of CSE storage to allocate to the organization, in GBs.
format: int64
example: 50000
default: 0
tracingIngest:
maximum: 1000000
minimum: 0
type: integer
description: The amount of tracing data ingest to allocate to the organization, in GBs.
format: int64
example: 50000
default: 0
flexIngest:
maximum: 1000000
minimum: 0
type: integer
description: The amount of flex logs ingest to allocate to the organization, in GBs.
format: int64
example: 5
default: 0
flexStorage:
maximum: 1000000
minimum: 0
type: integer
description: Number of days of flex logs storage to allocate to the organization, in Days.
format: int64
example: 30
default: 0
flexScanRatio:
maximum: 1000000
minimum: 0
type: integer
description: The amount of flex logs ingest scan ratio.
format: int64
example: 5
default: 0
aiInvestigation:
maximum: 1000000
minimum: 0
type: integer
description: The amount of AI Investigations needed to allocate to the organization.
format: int64
example: 5
default: 0
description: Details of consumable and its quantity.
UsageReportResponse:
type: object
properties:
jobId:
type: string
description: Job Id for export
example: '12345678'
description: Export Usage response containing the jobId
UsageReportRequest:
type: object
properties:
startDate:
type: string
description: Start date, without the time, of the usage data to fetch. If no value is provided startDate is used as the start of the subscription. The start date cannot be before the start of the subscription.
example: 2019-07-20
endDate:
type: string
description: End date, without the time, of usage data to fetch. If no value is provided endDate is used as the end of the subscription. The end date cannot be after the end of the subscription.
example: 2019-08-20
groupBy:
pattern: ^(day|week|month)$
type: string
description: 'Perform a groupBy operation on the usage details. If no value is provided data is grouped by `Day` - `day`: Aggregate the data by day - `week`: Aggregate the data by week. Week starts at Monday and ends at sunday night. - `month`: Aggregate the data by calendar month.'
example: day
default: day
reportType:
pattern: ^(standard|detailed|childDetailed)$
type: string
description: Specifies the type of report to be exported. Available types are `standard` and `detailed`. An additional `childDetailed` type is available for Sumo Orgs parents. Detailed report will have raw consumption along with the credits breakdown. If no value is provided Standard reports will be exported.
example: standard
default: standard
includeDeploymentCharge:
type: boolean
description: Deployment charges will be applied to the returned usages csv if this is set to true and the organization is a part of Sumo Organizations as a child or
# --- truncated at 32 KB (40 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/sumo-logic/refs/heads/main/openapi/sumo-logic-accountmanagement-api-openapi.yml