How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Sumo Logic extractionRuleManagement API

Field Extraction Rule management API.Field Extraction Rules 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).

Sumo Logic extractionRuleManagement API is one of 61 APIs that Sumo Logic publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 5 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 10 base URLs: https://api.au.sumologic.com/api/, https://api.ca.sumologic.com/api/, https://api.de.sumologic.com/api/, https://api.eu.sumologic.com/api/, https://api.fed.sumologic.com/api/, https://api.jp.sumologic.com/api/, https://api.kr.sumologic.com/api/, https://api.in.sumologic.com/api/, https://api.sumologic.com/api/, https://api.us2.sumologic.com/api/.

5 operations 2 paths 8 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.sumologic.com/api
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Sumo Logic extractionRuleManagement API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

extractionRuleManagement 5

Field Extraction Rule management API. Field Extraction Rules allow you to parse fields from your log messages at the time the messages are ingested eliminating the need to parse f…

GET
/v1/extractionRules
Get A List Of Field Extraction Rules.
listExtractionRules 2 params → 200default
POST
/v1/extractionRules
Create A New Field Extraction Rule.
createExtractionRule body → 200default
GET
/v1/extractionRules/{id}
Get A Field Extraction Rule.
getExtractionRule 1 param → 200default
PUT
/v1/extractionRules/{id}
Update A Field Extraction Rule.
updateExtractionRule 1 param body → 200default
DELETE
/v1/extractionRules/{id}
Delete A Field Extraction Rule.
deleteExtractionRule 1 param → 204default

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are ErrorDescription (4 properties), MetadataModel (4 properties), BaseExtractionRuleDefinition (3 properties), ListExtractionRulesResponse (2 properties). Each schema is shown below with its type and property counts.

MetadataModel
object
4 properties 4 required
ExtractionRule
object
ErrorResponse
object
2 properties 2 required
ErrorDescription
object
4 properties 2 required
BaseExtractionRuleDefinition
object
3 properties 3 required
ExtractionRuleDefinition
ListExtractionRulesResponse
object
2 properties 1 required
UpdateExtractionRuleDefinition

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sumo-logic-extractionrulemanagement-api-openapi.yml Raw ↑

Other APIs Sumo Logic publishes across the network.

Sumo Logic accessKeyManagement API
Sumo Logic accountManagement API
Sumo Logic appManagement API
Sumo Logic appManagementV2 API
Sumo Logic archiveManagement API
Sumo Logic budgetManagement API
Sumo Logic connectionManagement API
Sumo Logic contentManagement API
Sumo Logic contentPermissions API
Sumo Logic dashboardManagement API
Sumo Logic dataDeletionRules API
Sumo Logic dataMaskingManagement API
Where this information came from

This is an independent, third-party profile of Sumo Logic extractionRuleManagement API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.