Get all knowledge articles

get

/search

This method returns a list of knowledge articles from the Oracle Knowledge repository.

Request

Query Parameters

There's no request body for this operation.

Back to Top

Response

Supported Media Types

200 Response

OK
Body ()
Root Schema : SearchResultList
Type: object
Show Source
Nested Schema : Facets
Type: object
Title: Facets
Additional Properties Allowed
Show Source
Map of list of SearchFacetBO by name.
Show Source
  • Title: Facet
    The key is either product or category or any string
Nested Schema : Items
Type: array
Title: Items
The collection of of the requested resources meeting your criteria.
Show Source
Nested Schema : SearchFacetBO
Type: object
Show Source
Nested Schema : Organization Id
Type: object
Title: Organization Id
The organization ID of the product.
Nested Schema : Category Hierarchy
Type: object
Title: Category Hierarchy
Category hierarchy with the delimiter of >
Nested Schema : SearchResultItem
Type: object
Documentation for BO mode: SearchResultItemBO
Show Source
Nested Schema : articleStatus
Match All

The article status.

    The service response matches any Content object (PUBLISHED by default) with article status specified in the request if you pass the articleStatus.refKey parameter.

    Example URIs for the articleStatus parameter are as follows:

  • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatus.referenceKey+eq+'DRAFT'
  • OR

  • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatus.referenceKey+in+('DRAFT', 'WORK_IN_PROGRESS')

  • The following example URIs returns Content objects whose contentState is LATEST:

  • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatus.referenceKey+eq+'DRAFT' and contentState eq 'LATEST'

  • The following example URI returns Content objects with no article status assigned:

  • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatusRefKey+eq+'IM_NULL_ARTICLE_STATUS'

  • The following example URI returns Content objects with no article status assigned and Content objects with the Draft article status assigned:

  • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatusRefKey+in+('IM_NULL_ARTICLE_STATUS', 'DRAFT')

  • If there is no Content object that matches specified articleStatus query, response will include status of 200 OK with no records.


    If there is no Content object that matches specified articleStatus query, response will include status of 200 OK with no records.

Show Source
  • ArticleStatusKeyBO
    Documentation for BO mode: ArticleStatusKeyBO
  • Title: Article Status

    The article status.

      The service response matches any Content object (PUBLISHED by default) with article status specified in the request if you pass the articleStatus.refKey parameter.

      Example URIs for the articleStatus parameter are as follows:

    • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatus.referenceKey+eq+'DRAFT'
    • OR

    • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatus.referenceKey+in+('DRAFT', 'WORK_IN_PROGRESS')

    • The following example URIs returns Content objects whose contentState is LATEST:

    • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatus.referenceKey+eq+'DRAFT' and contentState eq 'LATEST'

    • The following example URI returns Content objects with no article status assigned:

    • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatusRefKey+eq+'IM_NULL_ARTICLE_STATUS'

    • The following example URI returns Content objects with no article status assigned and Content objects with the Draft article status assigned:

    • http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=articleStatusRefKey+in+('IM_NULL_ARTICLE_STATUS', 'DRAFT')

    • If there is no Content object that matches specified articleStatus query, response will include status of 200 OK with no records.


      If there is no Content object that matches specified articleStatus query, response will include status of 200 OK with no records.

Nested Schema : basedLocale
Match All
The source locale used to create the localized version of the document. This field is seen only if the content has a localized version.
Show Source
  • LocaleKeyBO
    Documentation for BO mode: LocaleKeyBO:

    Localized Name of the Locale is currently NOT provided (i.e. The word Japanese is always in Japanese and never localized in say Arabic.)

  • Title: Based Locale
    The source locale used to create the localized version of the document. This field is seen only if the content has a localized version.
Nested Schema : Categories
Type: array
Title: Categories
The list of categories associated with the article.
Show Source
Nested Schema : checkedOutBy
Match All

The user or author who performed the last content checkout. The following are the subfields that can be used with checkedOutBy query parameter:

  • checkedOutBy.recordId : The unique identifier of the checkedOutBy object. For example, to request an article with unique id, submit a call using the URI:
    http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=checkedOutBy.recordId eq '{id}'
  • checkedOutBy.email : User's email.
  • checkedOutBy.firstName : User's firstName.
  • checkedOutBy.lastName : User's lastName.
  • checkedOutBy.login : User's login.
Show Source
  • UserKeyBO
    Documentation for BO mode: UserKeyBO
  • Title: Checked Out By
    Read Only: true

    The user or author who performed the last content checkout. The following are the subfields that can be used with checkedOutBy query parameter:

    • checkedOutBy.recordId : The unique identifier of the checkedOutBy object. For example, to request an article with unique id, submit a call using the URI:
      http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=checkedOutBy.recordId eq '{id}'
    • checkedOutBy.email : User's email.
    • checkedOutBy.firstName : User's firstName.
    • checkedOutBy.lastName : User's lastName.
    • checkedOutBy.login : User's login.
Nested Schema : contentType
Match All

The channel to which the content is categorized and saved. The following are the subfields that can be used with contentType query parameter:

  • contentType.recordId : The unique identifier of the ContentType object.
  • contentType.referenceKey : The reference key for the ContentType object. ContentType objects support multiple languages. This field can be used to identify the associated objects for all languages. For Example to request articles for content type FAQ, submit a call using the URI:
    http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=contentType.referenceKey eq 'FAQ'
  • contentType.allowRecommendations : The flag indicates whether the content type allows end users to create recommendations for its contents. This also indicates whether you can associate the recommended content with a content type.
Show Source
  • ContentTypeKeyBO
    Documentation for BO mode: ContentTypeKeyBO
  • Title: Content Type

    The channel to which the content is categorized and saved. The following are the subfields that can be used with contentType query parameter:

    • contentType.recordId : The unique identifier of the ContentType object.
    • contentType.referenceKey : The reference key for the ContentType object. ContentType objects support multiple languages. This field can be used to identify the associated objects for all languages. For Example to request articles for content type FAQ, submit a call using the URI:
      http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=contentType.referenceKey eq 'FAQ'
    • contentType.allowRecommendations : The flag indicates whether the content type allows end users to create recommendations for its contents. This also indicates whether you can associate the recommended content with a content type.
Nested Schema : creator
Match All

The user who originally authored or created the document. The following are the subfields that can be used with creator query parameter:

  • creator.recordId : The unique identifier of the creator object. For example, to request an article with unique id, submit a call using the URI:
    http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=creator.recordId eq '{id}'
  • creator.email : User's email.
  • creator.firstName : User's firstName.
  • creator.lastName : User's lastName.
  • creator.login : User's login.
Show Source
  • UserKeyBO
    Documentation for BO mode: UserKeyBO
  • Title: Creator
    Read Only: true

    The user who originally authored or created the document. The following are the subfields that can be used with creator query parameter:

    • creator.recordId : The unique identifier of the creator object. For example, to request an article with unique id, submit a call using the URI:
      http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=creator.recordId eq '{id}'
    • creator.email : User's email.
    • creator.firstName : User's firstName.
    • creator.lastName : User's lastName.
    • creator.login : User's login.
Nested Schema : Highlighting
Type: object
Title: Highlighting
Additional Properties Allowed
Show Source
An excerpt of an article's content.
Nested Schema : lastModifier
Match All

The user or author who performed the last content modification. The following are the subfields that can be used with lastModifier query parameter:

  • lastModifier.recordId : The unique identifier of the lastModifier object. For example, to request an article with unique id, submit a call using the URI:
    http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=lastModifier.recordId eq '{id}'
  • lastModifier.email : User's email.
  • lastModifier.firstName : User's firstName.
  • lastModifier.lastName : User's lastName.
  • lastModifier.login : User's login.
Show Source
  • UserKeyBO
    Documentation for BO mode: UserKeyBO
  • Title: Last Modifier
    Read Only: true

    The user or author who performed the last content modification. The following are the subfields that can be used with lastModifier query parameter:

    • lastModifier.recordId : The unique identifier of the lastModifier object. For example, to request an article with unique id, submit a call using the URI:
      http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=lastModifier.recordId eq '{id}'
    • lastModifier.email : User's email.
    • lastModifier.firstName : User's firstName.
    • lastModifier.lastName : User's lastName.
    • lastModifier.login : User's login.
Nested Schema : locale
Match All

The locale of the version of the document. The locale code represents the language and country associated with the Locale object. The following subfield can be used with locale query parameter:

  • locale.recordId : The unique identifier of the Locale object. For example, to request an article in the Spanish-Spain locale, submit a call using the URI:
    http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=locale.recordId eq 'es_ES'
Show Source
  • LocaleKeyBO
    Documentation for BO mode: LocaleKeyBO:

    Localized Name of the Locale is currently NOT provided (i.e. The word Japanese is always in Japanese and never localized in say Arabic.)

  • Title: Locale

    The locale of the version of the document. The locale code represents the language and country associated with the Locale object. The following subfield can be used with locale query parameter:

    • locale.recordId : The unique identifier of the Locale object. For example, to request an article in the Spanish-Spain locale, submit a call using the URI:
      http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=locale.recordId eq 'es_ES'
Nested Schema : owner
Match All

The user or author who owns or is responsible for the document. The following are the subfields that can be used with owner query parameter:

  • owner.recordId : The unique identifier of the owner object. For example, to request an article with unique id, submit a call using the URI:
    http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=owner.recordId eq '{id}'
  • owner.email : User's email.
  • owner.firstName : User's firstName.
  • owner.lastName : User's lastName.
  • owner.login : User's login.
Show Source
  • UserKeyBO
    Documentation for BO mode: UserKeyBO
  • Title: Owner
    Read Only: true

    The user or author who owns or is responsible for the document. The following are the subfields that can be used with owner query parameter:

    • owner.recordId : The unique identifier of the owner object. For example, to request an article with unique id, submit a call using the URI:
      http://${pageContext.request.serverName}:${pageContext.request.serverPort}${pageContext.request.contextPath}/api/content?q=owner.recordId eq '{id}'
    • owner.email : User's email.
    • owner.firstName : User's firstName.
    • owner.lastName : User's lastName.
    • owner.login : User's login.
Nested Schema : Products
Type: array
Title: Products
The list of products associated with the article.
Show Source
Nested Schema : User Groups
Type: array
Title: User Groups
The user groups assigned to the content. Only the members of the assigned user group will have access to the content. Default value is Everyone.
Show Source
Nested Schema : Views
Type: array
Title: Views
Read Only: true
The views assigned to the content. The user who has the view assigned to the content or the content type in which the content is saved can only access the content.
Show Source
Nested Schema : workflowStep
Match All
The step of the workflow in which the document version currently exist.
Show Source
  • WorkflowStepDataBO
    Documentation for BO mode: WorkflowStepDataBO
  • Title: Workflow Step
    Read Only: true
    The step of the workflow in which the document version currently exist.
Nested Schema : ArticleStatusKeyBO
Type: object
Documentation for BO mode: ArticleStatusKeyBO
Show Source
  • Links
  • Title: Name
    Read Only: true
    Minimum Length: 1
    Maximum Length: 255
    The localized name of the ArticleStatus object. The name field can only be used for sorting.
  • Title: Record Id
    The unique identifier of the ArticleStatus object.
  • Title: Reference Key
    Maximum Length: 255
    The reference key for the ArticleStatus object. ArticleStatus objects support multiple languages. This field can be used to identify the associated objects for all languages.
Nested Schema : LocaleKeyBO
Type: object
Documentation for BO mode: LocaleKeyBO:

Localized Name of the Locale is currently NOT provided (i.e. The word Japanese is always in Japanese and never localized in say Arabic.)

Show Source
  • Links
  • Title: Locale Desc
    Read Only: true
    Maximum Length: 100
    The description about the language and country that the Locale object represents.
  • Title: Record Id
    The unique identifier of the Locale object.
Nested Schema : Catalog
Type: object
Documentation for BO mode: CategoryBO
Show Source
Nested Schema : UserKeyBO
Type: object
Documentation for BO mode: UserKeyBO
Show Source
Nested Schema : Content Type Privileges
Type: array
Title: Content Type Privileges
This field will return list of all contenttype privileges user have
Show Source
Nested Schema : Functional Privileges of user
Type: object
Title: Functional Privileges of user
Additional Properties Allowed
Show Source
This field will return list of all fucntional privileges user have
Nested Schema : CompositeContentTypeBO
Type: object
Composite of ContentTypeBO and its flattened relation. Keep in mind we can add more stuff down the line
Show Source
Nested Schema : WorkflowSteps Composite BO
Type: array
Title: WorkflowSteps Composite BO
WorkflowSteps mapped to this content type and user privileges on that
Show Source
Nested Schema : contentTypeKeyBO
Match All
ContentBO object being created or updated
Show Source
  • ContentTypeKeyBO
    Documentation for BO mode: ContentTypeKeyBO
  • Title: Content Type Key BO
    ContentBO object being created or updated
Nested Schema : List Of Privilege
Type: array
Title: List Of Privilege
List of Privileges for the ContentType
Show Source
Nested Schema : CompositeWorkflowStepBO
Type: object
Composite of WorkflowStepBO with user privileges on this step.
Show Source
Nested Schema : List Of Privilege
Type: array
Title: List Of Privilege
List of Privileges for the WorkflowStep
Show Source
Nested Schema : WorkflowStepKeyBO
Match All
WorkflowStep object being fetched
Show Source
  • WorkflowStepKeyBO
    Documentation for BO mode: WorkflowStepKeyBO
  • Title: WorkflowStep Key BO
    WorkflowStep object being fetched
Nested Schema : WorkflowStepKeyBO
Type: object
Documentation for BO mode: WorkflowStepKeyBO
Show Source
Nested Schema : ContentTypeKeyBO
Type: object
Documentation for BO mode: ContentTypeKeyBO
Show Source
  • Title: Description
    Maximum Length: 255
    The description for the ContentType object. Content Types support multiple languages. This field identifies the object associated with the language specified by the user.
  • Links
  • Title: Name
    Minimum Length: 1
    Maximum Length: 255
    The name for the ContentType object. The name field can only be used for sorting. Content Types support multiple languages. This field identifies the object associated with the language specified by the user.
  • Title: Record Id
    Read Only: true
    The unique identifier of the ContentType object.
  • Title: Reference Key
    Minimum Length: 1
    Maximum Length: 255
    The reference key for the ContentType object. ContentType objects support multiple languages. This field can be used to identify the associated objects for all languages.
  • Title: Stripe Cd
    Maximum Length: 30
    Lookup code that indicates the stripe code.
  • Title: Usage Code
    Read Only: true
    Maximum Length: 30
    Lookup code that indicates the product usage code.
  • workflow
Nested Schema : workflow
Match All
The workflow definition that the author can use while content authoring in a content type.
Show Source
  • WorkflowKeyBO
  • Title: Workflow
    The workflow definition that the author can use while content authoring in a content type.
Nested Schema : WorkflowKeyBO
Type: object
Show Source
Nested Schema : additionalProperties
Type: array
Show Source
Nested Schema : CatalogProduct
Type: object
Documentation for BO mode: CatalogProductBO
Show Source
Nested Schema : UserGroupKeyBO
Type: object
Documentation for BO mode: UserGroupKeyBO
Show Source
  • Links
  • Title: Name
    Read Only: true
    Maximum Length: 255
    The localized name of the user group. The name field can only be used for sorting.
  • Title: Record Id
    The unique identifier from the TAG table that represent a userGroups resource
  • Title: Reference Key
    Maximum Length: 255
    The non localized name of the user group
  • Title: Stripe CD
    Read Only: true
    Maximum Length: 30
    Stripe for UserGroup
Nested Schema : ViewKeyBO
Type: object
Documentation for BO mode: ViewKeyBO
Show Source
Nested Schema : WorkflowStepDataBO
Type: object
Documentation for BO mode: WorkflowStepDataBO
Show Source
Back to Top