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

Oracle Incident API

The Incident API from Oracle — 5 operation(s) for incident.

Oracle Incident API is one of 378 APIs that Oracle publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incident. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 7 operations across 5 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version 20181231.

Requests are made against a single base URL, http://127.0.0.1/20181231.

7 operations 5 paths 33 schemas 4 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
20181231
Base URL
https://{host}:{port}/ords/
License
Resource Areas
1

Paths & Operations 7

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

Incident 7
GET
/v2/incidents
ListIncidents
ListIncidents 15 params → 200400401403404429500default
POST
/v2/incidents
CreateIncident
CreateIncident 7 params body → 200400401403404429500default
GET
/v2/incidents/incidentResourceTypes
ListIncidentResourceTypes
ListIncidentResourceTypes 10 params → 200400401403404429500default
GET
/v2/incidents/user/validate
ValidateUser
ValidateUser 8 params → 200403
GET
/v2/incidents/{incidentKey}
GetIncident
GetIncident 10 params → 200400401403404429500default
PUT
/v2/incidents/{incidentKey}
UpdateIncident
UpdateIncident 10 params body → 200400401403404412429500
PUT
/v2/incidents/{incidentKey}/attachment
PutAttachment
PutAttachment 13 params body → 200400401404412429500default

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are Incident (15 properties), IncidentSummary (14 properties), Ticket (9 properties), ServiceCategory (9 properties). Each schema is shown below with its type and property counts.

SubCategories
object
List of subcategories under a service.
4 properties
CreateIncident
object
Details gathered during the creation of the support request.
6 properties 3 required
CreateCategoryDetails
object
Details for creating the category of the support request.
1 property
SubCategory
object
Details about the service subcategory associated with the support request.
2 properties
CreateIssueTypeDetails
object
Details for creating the issue type of the support request.
1 property
IncidentSummary
object
Details about the support request.
14 properties 2 required
CreateTicketDetails
object
Details relevant to the support request.
5 properties 3 required
ContactList
object
The list of contacts for the ticket.
1 property 1 required
Item
object
Details about the item object.
6 properties
ContextualData
object
Information collected from user context during ticket creation.
4 properties 4 required
UpdateTicketDetails
object
Details about the ticket updated.
1 property 1 required
IncidentType
object
Details about the incident type associated with the support request.
5 properties
Resource
object
Details about the ticket item object.
2 properties
TenancyInformation
object
Details about the tenancy.
1 property 1 required
UpdateItemDetails
object
Details for updating an item.
1 property
Ticket
object
Details about the ticket created.
9 properties 3 required
CreateResourceDetails
object
Details about the resource that the support request relates to.
2 properties
IncidentResourceType
object
Details about the resource associated with the support request.
8 properties 1 required
IssueType
object
Details about the issue type associated with the support request.
3 properties
Incident
object
Details about the support request.
15 properties 1 required
UpdateIncident
object
Details about the support request being updated.
2 properties 1 required
Contact
object
Contact details for the customer. Avoid entering confidential information.
5 properties
CreateItemDetails
object
Details gathered during ticket creation.
5 properties
ServiceCategory
object
Information about the support request classifier.
9 properties
Services
object
List of Service Categories of a Service for MOS Taxonomy.
3 properties
Error
object
Details about an error that occurred.
2 properties 2 required
Classifier
object
Details about the incident classifier object.
7 properties
UpdateResourceDetails
object
Details about updates to the resource.
1 property
CmosUserGroupInfo
object
Identifier and name of a user group (userGroupId and userGroupName) that the current user has access to. Note: The Customer User Administrator (CUA) can manage…
2 properties
SubComponents
object
List of subcomponents under a subcategory.
2 properties
CreateSubCategoryDetails
object
Details for creating the service subcategory of the support request.
1 property
Category
object
Details about the service category associated with the support request.
2 properties
ValidationResponse
object
The validation response returned when checking whether the requested user is valid.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oracle-incident-api-openapi.yml Raw ↑

Other APIs Oracle publishes across the network.

Oracle Database REST APIs
Oracle Integration Cloud API
Oracle Fusion Cloud Applications API
Oracle Fusion Cloud Financials REST API
Oracle Fusion Cloud HCM REST API
Oracle Fusion Cloud CX Sales and Service REST API
Oracle Fusion Cloud SCM REST API
Oracle Fusion Cloud Procurement REST API
Oracle Content Management API
OCI Generative AI API
OCI AI Vision API
OCI AI Language API
Where this information came from

This is an independent, third-party profile of Oracle Incident 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.