Skip to main content
Sumo Logic

Developer Release Notes

August 27, 2019


Update - Steps for generating clients now use OpenAPI Generator instead of Swagger Codegen. Using Swagger Codegen will generate a backward incompatible client. For more details, see

August 7, 2019


New - Content, Folder, and Permissions Management APIs allow you to manage content in your organization’s Library from HTTP endpoints.

June 26, 2019


Update - The Collector Management API can return Collectors by name and manage offline Collectors with the aliveBeforeDays parameter.

June 17, 2019


New - The Ingest Budget Management API allows you to manage ingest budgets from HTTP endpoints.

May 15, 2019


Update - Added hostname as a Collector environment variable in our Docker image.

March 22, 2019 


Update - The security services of our API framework has been upgraded. API requests with multiple forward slashes (//) will receive a "500 Internal Server Error" response.

February 13, 2019 


New - User and Role APIs allow administrators to programmatically create and manage users and roles, making it easy to integrate Sumo into existing onboarding/offboarding business workflows.

November 20, 2018 

API Beta 

New - As part of our new API-centric development approach, we have several Sumo Logic APIs now available. Contact your sales rep to sign up to be one of our Beta Customers for the following APIs:

  • Connections
  • Content
  • Field Extraction Rules
  • Ingest Budgets
  • Partitions
  • Roles
  • Scheduled Views
  • Users

And the following APIs are coming soon:

  • Dashboards
  • Metrics Monitors

September 11, 2018

Search Job API 

New -  Receipt time is now available for scheduled searches, share links for searches, pinned searches, and Search Job API queries. To support receipt time, the Search Job API has a new parameter, byReceiptTime.

July 6, 2018

Search Job API  

Techniques that manage load, like rate limiting and throttling, help keep the Sumo platform reliable and stable. Towards that end, a new Search Job API throttling limit was introduced today. Until now, search jobs were subject only to the global rate limit: each user is limited to four API requests/second. Now, to improve reliability Sumo is limiting the number of active search jobs for a given account to 200. To manage the number of active search jobs you can manually clear completed searches. For more information, see Search Job API throttling.