PBRS Report Automation API

Automate Power BI and SSRS Reporting from Your Application

Connect your application to PBRS through its REST API. Create schedules, personalize reports and trigger delivery from your own workflows—while PBRS handles report generation and distribution. Build the integration without maintaining a reporting scheduler of your own.

Create and manage report schedules from your application or customer portal.

Set filters, report parameters and email recipients programmatically.

Trigger reports when your business process finishes and monitor execution.

Build report packages across Power BI, paginated reports and SSRS.

Explore the API documentation →

The Reporting Integration Challenge

Your Application Needs Reporting. Your Team Shouldn’t Have to Build the Scheduler.

Generating a report is only part of the job. Your application also needs to manage schedules, apply the right parameters, deliver outputs and track execution. Building and maintaining that infrastructure takes time away from your core product.

Too Much Custom Code to Maintain

A simple export script grows into scheduling logic, recipient management, delivery routines and status tracking. Every new requirement adds more code for your team to build, test and support.

Reporting Requirements Keep Changing

Customers, facilities and departments need different report parameters, recipients and schedules. Those choices need to flow from your application into reporting without someone manually updating each job.

Reports Must Follow Your Workflow

A report may need to run after a batch finishes, a transaction completes or a user requests it. Your application needs a way to trigger execution and check the result, rather than relying on a fixed delivery time.

Choosing the Right Approach

When Native APIs Are Enough—and When PBRS Fits

Microsoft APIs are a sensible choice when your application needs a focused Power BI export workflow and your team is prepared to own the surrounding scheduling, delivery and operational code. PBRS is designed for applications that need a reporting automation layer across supported Power BI and SSRS environments.

Native APIs and Custom Code

A Good Fit for Focused Export Workflows

You need to export a limited set of Power BI reports from your application.

Your team will build and maintain the scheduling, delivery, retry and monitoring services around the export.

A single report source and a small set of delivery requirements meet the need.

The applicable Microsoft capacity, licensing and export requirements fit your workload.

PBRS REST API

Built for Reporting Automation in Your Application

Create, retrieve, update and manage supported report schedules through one API.

Programmatically manage report parameters, email destinations and supported output settings.

Run and monitor supported Power BI, paginated, SSRS and Power BI Report Server schedules from your workflow.

Create packages that bring supported reports and configured delivery into one reporting workflow.

PBRS runs within your reporting environment. Available API operations, report formats and delivery options depend on the report source, PBRS version and deployment configuration.

API Capabilities

Discover, Configure and Run Reporting from Your Application

The PBRS REST API gives your backend the reporting operations it needs to turn approved application choices into configured schedules, personalized outputs and completed report deliveries.

Discover Available Reporting

Find configured accounts, folders, reports, visuals and schedules so your application can work with approved reporting resources rather than hard-coded IDs.

Create and Manage Schedules

Create, retrieve, update and delete supported single-report and package schedules from your application’s own reporting workflow.

Personalize Each Delivery

Apply supported filters and parameters, manage email destinations and configure each report for the customer, department, facility or recipient your application serves.

Execute and Monitor

Start supported schedules when your business workflow requires them, then use execution status and queue information to track what happened.

Explore the PBRS API documentation →

Reporting That Follows Your Workflow

Make Report Delivery Part of Your Application

Your application determines when reporting should happen. PBRS provides the supported schedule management, execution and delivery operations behind the experience you build for users.

Run Reports When Work Is Complete

Start a supported report schedule after your batch process, transaction, import or business workflow reaches the point where the report is ready to run.

Offer Controlled Self-Service

Let users select from approved reports, schedules, recipients and output options in your application while your backend applies the reporting rules you define.

Track the Result

Store the schedule and execution identifiers returned by PBRS, then use execution status and queue information to provide visibility into your reporting workflow.

Keep PBRS credentials and privileged API calls in your application backend. Your application remains responsible for authenticating users and enforcing which reports and data each user can access.

Personalized Report Delivery

Give Every Recipient the Right Report

Use your application’s business data to control supported report parameters, recipients and delivery settings. PBRS turns those instructions into configured reporting workflows without requiring a separate schedule for every customer or department.

Apply the Right Data Scope

Set supported filters and parameters for the customer, facility, region, account or department represented by the application request.

Control Delivery from Your System

Add or update supported email destinations and recipient lists as the people, roles and reporting requirements in your application change.

Deliver Complete Report Packages

Create supported packages that coordinate Power BI, paginated, SSRS and Power BI Report Server reports in one configured delivery workflow.

Available report sources, output formats and destination settings depend on the PBRS configuration and the report source you use.

Built for Application Teams

Use PBRS Behind Your Customer Portal or Business Application

PBRS does not replace the application experience you have built. Your application owns its users, business rules and permissions. PBRS provides the reporting automation layer behind the supported workflows you expose.

Add Scheduling to a Customer Portal

Let authorized users select from approved reports, choose a schedule and nominate recipients through your portal. Your backend validates each request and creates the supported PBRS schedule.

Trigger Reporting from Operational Systems

When an import, batch run, transaction or business process completes, your application can update the required report settings, start execution and record the result.

Replace a Homegrown Reporting Scheduler

Keep the application interface and business logic your users already know while moving supported report scheduling, execution and delivery operations into PBRS.

A secure integration starts in your backend. Keep PBRS credentials and access tokens out of browser code. Your application should authenticate users, authorize their reporting choices and apply the required data scope before calling PBRS.

Configured Outputs and Delivery

Generate the Output Your Workflow Requires

PBRS can generate and deliver reports using the configured format and destination for each supported workflow. Your application controls the reporting request; PBRS performs the configured report generation and delivery.

Produce Useful Business Files

Configure supported workflows to generate report outputs such as PDF, Excel and PowerPoint, based on the report source and PBRS configuration.

Protect Sensitive Deliveries

Use supported PDF and Excel protection settings when the reporting workflow requires an additional level of control over delivered files.

Deliver to the Right Destination

PBRS can deliver completed reports through configured destinations such as email, cloud storage and network folders, according to the reporting workflow you define.

Output formats, protection settings and delivery destinations vary by report source and PBRS deployment. Confirm the supported combination for the workflow you plan to build.

Reporting Operations

Build an Integration Your Team Can Operate

A reliable reporting integration needs more than a successful API request. Your application should retain the identifiers and configuration needed to trace schedules, review executions and support users when reporting requirements change.

Retain the IDs That Matter

Store the PBRS schedule ID, destination ID and execution ID alongside the relevant application record so your team can trace each reporting workflow.

Monitor Execution

Check execution status and queue information after initiating a report run. Use the returned information to present meaningful reporting status in your application.

Test Configuration Changes

Validate changes to schedules, parameters, recipients and report settings before enabling recurring delivery for production users.

Support Users with Context

Keep your application’s request details, PBRS identifiers and execution result together so support teams can investigate a reporting issue without reconstructing the workflow.

Supported Reporting Sources

One API for Your Microsoft Reporting Environment

PBRS gives application teams a consistent way to work with supported cloud and on-premises Microsoft reporting sources. It can provide the reporting automation layer behind your Power BI report automation workflow.

Power BI Service

Work with supported Power BI reports and configured reporting accounts.

Power BI Paginated Reports

Configure supported parameter-driven paginated report workflows.

SQL Server Reporting Services

Include supported SSRS reports in schedules and report packages.

Power BI Report Server

Bring supported on-premises report-server workflows into the same reporting process.

Available API operations, output formats and authentication requirements depend on the PBRS version, report source and deployment configuration.

Build on Reporting Experience

Reporting Automation Built for Long-Term Use

ChristianSteven Software has focused on automated business reporting for more than two decades. PBRS gives your application a supported reporting automation layer while you retain ownership of your product experience and business logic.

20+

Years of Reporting Automation

Deep experience with the operational details behind recurring business reporting.

API

Documentation for Developers

Explore API reference material and implementation guides before you build.

PBRS

Support for Your Reporting Workflow

Test your use case, validate the right configuration and bring technical questions to the PBRS team.

Visit the PBRS API developer portal →

The PBRS REST API lets an application work with PBRS programmatically. It can create and manage schedules, execute report automation, manage report packages, and monitor execution activity—without requiring a person to perform each action in the PBRS interface.

Yes. Your application can call the API to start an existing PBRS schedule when its own workflow reaches the appropriate point—for example, after a transaction completes, a file is received, or another internal process finishes.

Yes. The API supports programmatic schedule management, allowing an application to create, retrieve, update, and manage schedules as reporting requirements change.

Yes. An application can use PBRS schedules and packages to support recipient-specific reporting workflows. PBRS handles the report-generation and delivery process; the application can initiate and manage that process through the API.

The API works with PBRS automation for Power BI Service, Power BI Report Server, Power BI Paginated Reports, and SSRS.

Yes. PBRS supports report packages, allowing related reports to be managed as a single automation workflow. This is useful when an application needs to produce and deliver a complete reporting set rather than one individual export.

The API provides execution and monitoring capabilities so the application can check the status of its requests and incorporate that information into its own workflow, logging, exception handling, or user notifications.

No. The API gives your application a way to control PBRS. PBRS remains the report automation layer for scheduling, generating, packaging, and delivering reports, reducing the custom infrastructure your team has to build and maintain.

The PBRS REST API uses authenticated access with bearer tokens. API clients are configured in PBRS, and access tokens are issued for authenticated requests.

Yes. The API complements the PBRS interface. Teams can use the interface for administration and operational work while applications use the API where reporting needs to be initiated, managed, or monitored programmatically.