Find all

get

/km/api/v1/incidents

This method returns a list of Incident objects from the Oracle Knowledge Repository.

This resource supports the orderBy request parameter. You can use this parameter with the HTTP service request to sort the returned list.

You must get the schema and catalog of the resource for additional values that you can use with the orderBy parameter. To get the schema and catalog of the resource, you must use the GET method with the mediaType value as 'application/schema+json' in the HTTP request.

The example URI to get the schema and catalog of the resource is as follows:

  • http://<IM_REST_API_HOST>/km/api/latest/metadata-catalog/incidents

Example URIs

The example URIs for this method are as follows:

  • http://<IM_REST_API_HOST>/km/api/latest/incidents

    The request returns a paginated list of Incident objects in FULL mode. Objects in the list are sorted by recordId parameter value in ascending order.

  • http://<IM_REST_API_HOST>/km/api/latest/incidents?mode=KEY

    The request returns a paginated list of Incident objects in KEY mode. Objects in the list are sorted by recordId parameter value in ascending order

  • http://<IM_REST_API_HOST>/km/api/latest/incidents?mode=KEY&limit=10&offset=0&orderBy=incidentId

    The request returns a paginated list of at most 10 Incident objects in KEY mode. The list starts with the Incident object at position 0. Objects in the list are sorted by incidentId parameter value.

Response Error

The possible error response for this method is as follows:

  • OK-GEN0013

    The error is displayed when you specify the mode parameter value as DATA with the HTTP service request.




Find by query

Supported Media Types: 'application/json', 'application/xml'



This method returns a list of Incident objects that match the specified criteria.

This resource supports the orderBy request parameter. You can use this parameter with the HTTP service request to sort the returned list.

You can find the different values to use with the orderBy parameter in the schema and catalog information of the resource. To get the schema and catalog information, use the GET method with the mediaType value as 'application/schema+json' in the HTTP request.

The example URI to get the schema and catalog of the resource is as follows:

  • http://<IM_REST_API_HOST>/km/api/latest/metadata-catalog/incidents

Example URIs

The example URIs for this method are as follows:

  • http://<IM_REST_API_HOST>/km/api/latest/incidents?q=dateAdded after '2015-01-01'&orderBy=dateAdded:desc

    The request returns a paginated list of Incident objects in FULL mode that were added after January 1, 2015. Objects in the list are sorted by the most recent date.

  • http://<IM_REST_API_HOST>/km/api/latest/incidents?q=incidentId in ('150731-000085','150731-000086','150731-000087')

    The request returns a paginated list of Incident objects in FULL mode that have any of the following incidentId values: 150731-000085, 150731-000086, 150731-000087. Objects in the list are sorted by date in ascending order.

  • http://<IM_REST_API_HOST>/km/api/latest/incidents?q=description likeAny ('*Oracle Knowledge*')

    The request returns a paginated list of Incident objects having the term 'Oracle Knowledge' in the description. Objects in the list are sorted by date in ascending order.

Response Error

The possible error response for this method is as follows:

  • OK-GEN0013

    The error is displayed when you specify the mode parameter value as DATA with the HTTP service request.

Query Parameters

The following table describes the query parameters for this resource.

ParameterQueryableSortableTypeDescription
recordIdYY'type' : 'string'

The record Id of the Incident object.

incidentIdYY'type' : 'string'

The identifier of the Incident. This is also referred to as the case number.

dateAddedYY'type' : 'string', 'format' : 'date-time'

The date when the Incident object was created.

dateModifiedYY'type' : 'string', 'format' : 'date-time'

The date when the Incident object was last modified.

descriptionYY'type' : 'string'

The description of the Incident.

Request

Query Parameters
  • This parameter restricts the number of resources returned inside the resource collection. If the limit exceeds the resource count then the framework will only return the available resources.
  • This parameter defines amount of information to be included in the returned resources - KEY is the one that has least information (and hence performs better) and FULL is the one that has most information.
    Allowed Values: [ "KEY", "DATA", "EXTENDED", "FULL" ]
  • Used to define the starting position of the resource collection. If offset exceeds the resource count then no resources are returned. Default value is 0.
  • This parameter orders a resource collection based on the specified attributes. The parameter value is a comma-separated string of attribute names, each optionally followed by a colon and 'asc' or 'desc'. Specify 'asc' for ascending and 'desc' for descending. The default value is 'asc'. For example, ?orderBy=field1:asc,field2:desc.
  • Value for this parameter should be Oracle Knowledge Q query - see the 'Getting Started' documentation ('Querying' page) of this operation and documentation for Q query.
Back to Top

Response

Supported Media Types

200 Response

OK.
Body ()
Root Schema : ResultList Incident
Type: object
Title: ResultList Incident
Match All
Show Source
Nested Schema : Collection Paging Resource
Title: Collection Paging Resource
Oracle base collection resource schema definition.
Match All
Show Source
Nested Schema : Base Collection Resource
Title: Base Collection Resource
Oracle base collection resource schema definition.
Match All
Show Source
Nested Schema : Singular Resource
Type: object
Title: Singular Resource
Oracle base singular resource schema definition.
Show Source
Nested Schema : Base Collection Resource-allOf[1]
Type: object
Show Source
Nested Schema : Collection Paging Resource-allOf[1]
Type: object
Show Source
Nested Schema : ResultList Incident-allOf[1]
Type: object
Show Source
Nested Schema : items
Type: array
Show Source
Nested Schema : items
Type: object
Nested Schema : items
Type: array
Show Source
Nested Schema : Incident
Match All
Show Source
Nested Schema : IncidentKey
Match All
Show Source
Nested Schema : IncidentKey-allOf[1]
Type: object
Show Source
Nested Schema : Incident-allOf[1]
Type: object
Show Source
Back to Top

Examples

The following example shows how to find all Incident objects from Oracle Knowledge repository by submitting a get request on the REST resource using cURL.

cURL Command

curl -X "GET" "http://<IM_REST_API_HOST>/km/api/latest/incidents"

Example of Request Header

The following shows an example of the request header.

-H "kmauthtoken: {\"siteName\":\"ORACLE_KNOWLEDGE\",\"integrationUserToken\":\"\"+eCJYkxKwj5HUaIiJYun0/TpatwT1LmtcsF05W33xnEojifV/AsLDj9RpN0lKuorTMNKeSE1tgC7svVL+BzntqDON4KiM1HFlpxvXEUCB0P2w0Xrs75McygqxdVaDSE9"}" \
-H "Accept: application/json"

Example of Response Body

The following shows an example of the response body in JSON format.

{
  "items" : [ {
    "dateAdded" : "2013-11-05T13:48:51EST",
    "dateModified" : "2013-11-05T13:48:51EST",
    "description" : "There is a problem identifying the meaning of key words for Oracle Knowledge",
    "recordId" : "2LKAJDFO8234OIJ3O24P18439837409819",
    "incidentId" : "140005-14895892",
    "links" : [ {
      "rel" : "canonical",
      "href" : "http://<IM_REST_API_HOST>/km/api/{version}/{resourceURI}",
      "mediaType" : "application/json, application/xml",
      "templated" : true,
      "method" : "GET",
      "profile" : "http://<IM_REST_API_HOST>/km/api/{version}/metadata-catalog/{resourceName}"
    } ]
  } ],
  "hasMore" : false,
  "limit" : 20,
  "offset" : 0,
  "links" : [ {
    "rel" : "canonical",
    "href" : "http://<IM_REST_API_HOST>/km/api/{version}/incidents?limit=20&offset=0",
    "mediaType" : "application/json, application/xml",
    "method" : "GET"
  } ],
  "count" : 1
}
Back to Top