Sales
Denmark +45 7944 7000
Europe +45 7944 7000
North America +1 (202)-536-4165
Support
Denmark +45 7944 7002
North America +1 (202)-536-4165

RealTime Service 6 API document

Modified on Mon, 3 Mar at 7:31 PM

Introduction

RealTime Service (RTS) offers powerful API capabilities that enable seamless communication with Exchange environments and third-party applications. his guide provides a high-level understanding of the integration possibilities and business benefits for non-technical stakeholders.

What is RealTime Service API?

RealTime Service acts as a bridge between your applications and Exchange Server, allowing you to access and manipulate calendar and email data programmatically. The API collects data from Exchange Server, monitors distribution list changes, and provides an interface for client applications to communicate with Exchange effectively.

Why Integration Matters

Organizations often rely on multiple software solutions to manage their communications, scheduling, and resource booking. The RTS API ensures your applications can interact directly with Microsoft Exchange, enhancing automation and efficiency without requiring direct Exchange access configurations for each application.

Key Benefits of RealTime Service API Integration:

  • Simplified Exchange Interaction – Access calendar and email functionality without deep Exchange knowledge
  • Streamlined Calendar Management – Create, read, update, and delete appointments and meetings programmatically
  • Email Automation – Send emails through a standardized interface
  • User Availability Tracking – Check free/busy status of users and resources
  • Resource Management – Access and manage Exchange resources like rooms and equipment
  • Active Directory Integration – Retrieve user information from your organization's directory

Core Capabilities

The RTS API provides two main interfaces that enable:

1. Calendar Management

  • Create, modify, and delete appointments and meetings
  • Check user and resource availability
  • Manage recurring appointments
  • Handle meeting invitations and responses
  • Work with calendar attachments

2. Email Communication

  • Send emails on behalf of users (with proper permissions)
  • Create formatted email content
  • Add attachments to messages

3. User and Resource Information

  • Access the Global Address List
  • Retrieve user details from Active Directory
  • Get information about resources (rooms, equipment)
  • Search for specific users or resources

Common Integration Scenarios

  • Meeting Room Booking Systems – Integrate with facility management tools to automatically create calendar entries when booking resources
  • Workflow Applications – Trigger appointment creation or email notifications based on business processes
  • Custom Scheduling Tools – Build specialized scheduling interfaces tailored to specific business needs
  • Reporting Systems – Extract calendar data for analytics and reporting
  • Multi-domain Environments – Enable calendar and email functions across different organizational domains

Technical Considerations

While this document focuses on business capabilities, it's worth noting that RTS API supports:

  • Both same-domain and cross-domain scenarios
  • Secure communications using certificates
  • Multiple authentication methods
  • Access to various Exchange versions (Exchange 2013/2016/2019, Exchange Online, Office 365)

Getting Started

To leverage the RTS API in your organization:

  1. Identify your integration needs (calendar management, email automation, etc.)
  2. Consult with your IT team about implementation possibilities
  3. Ensure your RTS server is properly configured for API access
  4. Work with developers to create the integration using the provided detailed API documentation

The RTS API empowers your organization to build more connected and automated solutions around your Exchange environment, improving efficiency and creating seamless workflows between different business systems.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article