Class ReportsControllerConfiguration

Provides static methods for registering Telerik Reporting Web API routes in ASP.NET Web API applications.

Inheritance
System.Object
ReportsControllerConfiguration
Namespace: Telerik.Reporting.Services.WebApi
Assembly: Telerik.Reporting.Services.WebApi.dll

Syntax

public class ReportsControllerConfiguration
Remarks

This class handles the automatic registration of all necessary routes for the Telerik Reporting REST service endpoints. Use this class during application startup to configure routing for report viewing, document generation, and client management.

Constructors

ReportsControllerConfiguration()

Declaration
public ReportsControllerConfiguration()

Methods

RegisterRoutes(HttpConfiguration)

Registers all necessary Telerik Reporting Web API routes using the default "api" path prefix.

Declaration
public static void RegisterRoutes(HttpConfiguration config)
Parameters
System.Web.Http.HttpConfiguration config

The HTTP configuration object to register the routes with.
Remarks

This method registers routes with the standard "api/{controller}" pattern commonly used in Web API applications. All Telerik Reporting service endpoints will be accessible under the "/api/reports" path by default. Call this method during application startup, typically in the WebApiConfig.Register method.

RegisterRoutes(HttpConfiguration, String)

Registers all necessary Telerik Reporting Web API routes with a custom path prefix to avoid routing conflicts.

Declaration
public static void RegisterRoutes(HttpConfiguration config, string firstPathSegment)
Parameters
System.Web.Http.HttpConfiguration config

The HTTP configuration object to register the routes with.
System.String firstPathSegment

The custom path segment to use as the first part of all route templates. For example, "reportingapi" would create routes like "/reportingapi/reports/clients".
Remarks

Use this overload when you need to avoid routing conflicts with other Web API services in your application. When using a custom path segment, ensure that your client-side report viewer is configured to use the corresponding service URL. For example, if you use "reportingapi" as the path segment, configure the report viewer's serviceUrl to "/reportingapi/reportviewer". This method registers all endpoints needed for report viewing, document generation, client session management, and AI integration.