Verint | Telligent Community
Verint | Telligent Community
  • Site
  • User
  • Site
  • Search
  • User
Verint Community 14.x
  • Verint Community
Verint Community 14.x
Developer Training REST API
  • User Documentation
  • Ask the Community
  • API Documentation
  • Manager Training
  • Developer Training
  • Tags
  • Sub-Groups
  • More
  • Cancel
  • New
  • Getting Started
  • -External Integration
    • External Authentication
    • REST API
    • Webhooks
  • +Plugins/Framework extension
  • +Automations
  • +UI Customization
  • +Notifications and Email
  • +Scripting
  • Obsolescence
  • Developer Training
  • External Integration

REST API

The REST API is is the primary method to interact with community information from an external application.  Using REST does not require anything to be deployed to the community site since it interacts with community using HTTP requests.

Combining calls to the REST API with Webhooks third party applications can tightly integrate with Verint Community inside their own applications user experience.

REST Authentication Methods 

Even though REST allows you to interact with community information outside of the community application itself the information is still secured.  REST has 2 different methods your application can use to authenticate and identify a user to obtain information securely.

Making REST Requests 

Getting information from your community requires that you make specific requests to the REST API with key pieces of information.  This topic covers how to generate these requests and to handle the data passed back to your application from the community.

REST API Documentation 

The REST API Documentation provides a detailed reference for all the REST endpoints supported by Verint Community.

REST Best Practices 

When creating a performant integration using REST, it's best to follow these recommendations.

Other Topics

  •  Extended Attributes in REST 
    • Some guidance on working with Extended Attributes in REST.
  •  Profile Fields in REST 
    • Some guidance on working with Profile Fields in REST.
  • API
  • REST
  • Created over 1 year ago
  • Updated over 1 year ago
Was this helpful?
  • Yes
  • No
  • More
  • Cancel
  • Article

    Authentication

    All REST requests must be authorized to access the REST API. When accessing the REST API from javascript in a widget through the $.telligent.evolution REST methods, no additional headers must be specified…
  • Article

    Disable Abuse Checking on REST Requests

    When creating or updating content that implements the IAbuseCheckingContentType content is detected by the individual abuse detectors that handle events applicable to their abuse detection logic and notify…
  • Article

    Disable Activity Stories on REST Requests

    When creating or updating content the content is detected by the individual activity story types that handle events applicable to their content detection logic and create activity stories. Using the REST…
  • Article

    Disable Notifications on REST Requests

    When creating or updating content the content is detected by the individual notification types that handle events applicable to their content detection logic and create notifications. Using the REST header…
  • Article

    Extended Attributes in REST

    Extended Attributes can be set and retrieved in REST as in any other of Verint Community's API spaces. General Notes on Extended Attributes Extended Attributes should not be used to store sensitive…
  • Article

    Making Requests

    The following guide is meant to provide a basic understanding of making REST requests using the Verint Community REST API. We recommend always making requests over HTTPS. To prevent authentication headers…
  • Article

    Profile Fields in REST

    Profile Fields can be set and retrieved in REST as in any other of Verint Community's API spaces. General Notes on Profile Fields To set a profile field, you must first define the profile field in…
  • Article

    REST Authorization using PKCE (Proof Key Code Exchange)

    PKCE, or Proof Key Code Exchange, is an extension of the authorization code flow in OAuth 2.0 that solves the "public" client issue. Public OAuth clients, or clients that cannot reliably or practically…
  • Article

    REST Best Practices for Performance

    REST is a powerful tool for integrating external applications with your community. There are aspects to REST that can effect your application performance if you are not conscious of them from the beginning…
  • Verint
  • Professional Services
  • Submit a Support Ticket
  • Become a Partner
  • Request a Demo
  • Contact Us

About
Privacy Policy
Terms of use
Copyright 2026 Verint, Inc.
Powered by Verint Community