Outlook Calendar API Integration: Microsoft Graph for Your Website

Note: when a clinic website lets patients book a doctor's appointment while the doctor's Outlook slot remains free—trouble starts. Manual cross-checking takes hours and leads to double bookings. The solution is to connect the website with Outlook calendars via the Microsoft Graph API. In 3–4 days we implement automatic event creation and availability checks. Updates happen in real time with less than 2 seconds delay. Below are the technical details of the integration.

Without the Outlook API, developers commonly face three issues: duplicate bookings due to lack of atomicity in scheduling, time inconsistencies from manual event transfers, and erroneous slots from unaccounted meeting series. The Graph API eliminates these risks but requires proper authentication configuration and handling of findMeetingTimes. We configure OAuth 2.0 with delegated permissions so the app works without access to the admin's mailbox.

Beyond basic scenarios, we solve complex tasks: syncing multiple calendars in one tenant, handling recurring events, and supporting time zones. Thanks to delta queries, updates arrive instantly without extra API calls. Average request speed is about 200 ms—3 times faster than the legacy EWS.

How to Set Up Authentication for Outlook Calendar?

The first step is registering an app in Azure AD. We create a client certificate for secure token exchange and grant the app Calendars.ReadWrite.All and User.Read permissions. This allows working with any user's calendar in the tenant. Then we obtain an access token via the OAuth 2.0 On-Behalf-Of flow—the system can act on behalf of an authorized admin. The whole process takes about an hour and is documented in a Postman collection. To work with all users' calendars, the Calendars.ReadWrite.All permission is needed. If only one calendar is required, Calendars.ReadWrite suffices. Permissions are assigned in Azure AD through the app. We help select the minimal necessary rights.

How to Integrate Outlook Calendar via Microsoft Graph?

The primary scenario is reading events for the upcoming week:

import { Client } from '@microsoft/microsoft-graph-client';

const client = Client.initWithMiddleware({ authProvider: tokenCredentialAuthProvider });

async function getCalendarEvents(userId: string): Promise<Event[]> {
  const response = await client
    .api(`/users/${userId}/calendarView`)
    .query({
      startDateTime: new Date().toISOString(),
      endDateTime:   new Date(Date.now() + 7 * 86400000).toISOString(),
    })
    .select('subject,start,end,location,isAllDay')
    .orderby('start/dateTime')
    .get();

  return response.value.map((e: any) => ({
    id:       e.id,
    title:    e.subject,
    start:    e.start.dateTime,
    end:      e.end.dateTime,
    location: e.location?.displayName,
    allDay:   e.isAllDay,
  }));
}

Creating an event requires binding to a specific user's calendar:

async function createEvent(userId: string, booking: Booking): Promise<string> {
  const event = await client.api(`/users/${userId}/events`).post({
    subject:  booking.serviceName,
    start:    { dateTime: booking.startsAt, timeZone: 'Russian Standard Time' },
    end:      { dateTime: booking.endsAt,   timeZone: 'Russian Standard Time' },
    body: {
      contentType: 'HTML',
      content:     `<p>Client: ${booking.customerName}</p><p>Phone: ${booking.phone}</p>`,
    },
    attendees: [{ emailAddress: { address: booking.customerEmail }, type: 'required' }],
    isReminderOn:       true,
    reminderMinutesBeforeStart: 60,
  });
  return event.id;
}

Error handling is critical: we account for rate limits (10,000 requests per hour per app) and retry calls with exponential backoff on status 429. We also check that the new event does not conflict with existing ones via findMeetingTimes.

Why Graph API over EWS?

EWS (Exchange Web Services) falls short on all metrics: it is slower—TTFB is 3 times higher (200 ms vs. 600 ms), requires certificate setup, and does not support delta queries. Graph API is a modern REST solution built on OAuth2 with excellent documentation. Here's a comparison:

Additional Graph API capabilities:

• Working with Teams meetings (onlineMeetingProvider, joinWebUrl)
• Attachment support (up to 150 MB per event)
• Reminder and room availability management

Moreover, Graph API is cheaper to maintain—no certificate renewal needed, and it supports modern scenarios like collaborative calendar management via webhook notifications. Over the last 5 years, we have delivered more than 30 projects integrating corporate calendars for clinics, rental services, and HR platforms.

Common Errors When Working with Graph API

What's Included in the Work

• App registration in Azure AD and generation of client certificates
• Implementation of REST endpoints for reading, creating, and updating events
• Setting up change notifications (webhook) for real-time synchronization
• Integration with CMS (WordPress, Drupal, Strapi, etc.)
• Integration documentation (Postman collection, DB schema)
• Testing with consideration of N+1 queries and API limits
• Error monitoring and alerts on authorization failures

Process Steps

1. Analysis: clarify scenarios—booking, synchronization, public slots.
2. Design: choose between delegated and application permissions.
3. Implementation: write service layer on Node.js/Nest.js, connect Redis cache.
4. Testing: cover with unit tests, check edge cases (timezone, meeting series).
5. Deployment: set up CI/CD, add health endpoints.

Estimated Timeline

Basic integration (read + create) takes 3–4 business days. With webhook synchronization—up to 7 days. The cost is calculated individually after analyzing your booking schema. Time saved on manual cross-checking reaches up to 60%, which pays off in 2–3 months. Average savings on operational expenses are around 20,000 RUB per month.

We have 5+ years of experience integrating corporate calendars—delivered over 30 projects for clinics, rental services, and HR platforms. Contact us to get a consultation on optimizing Core Web Vitals and managing Graph API rate limits. Order the integration, and we'll show you examples of working solutions.

API Development with REST, GraphQL, WebSocket, and tRPC

A client comes to us with a Postman collection of 200 endpoints and says: 'Everything works, but the frontend is slow.' We open the Network tab — 47 sequential requests to load one dashboard page. Each one waits for the previous. This is not a server speed issue — it's an API architecture problem. With 10 years on the market, we've redesigned dozens of such integrations, and we guarantee: the right protocol and contract solve the problem at its root.

When REST stops being enough

REST works well for simple CRUD operations. But as soon as a mobile app appears alongside the web interface, over-fetching begins: the mobile app requests /api/users/123 and gets a 4KB object, but only needs name and avatar. Multiply that by a list of 50 users — 200KB traffic instead of 8KB.

GraphQL solves this with selection sets. The client describes exactly the fields it needs, and the server returns only those. On a project with React Native + Next.js, we migrated from REST to Apollo Server: payload size on the main screen dropped from 340KB to 28KB — a 92% traffic savings. Our certified engineers confirm: the typical pain when adopting GraphQL is N+1 query. A resolver for the author field on a post calls SELECT * FROM users WHERE id = ? for each post in the list. On a page with 20 posts — 21 database queries. Solved with DataLoader — it batches queries and turns them into one SELECT * FROM users WHERE id IN (...).

What is tRPC and how is it better than REST/GraphQL?

If the entire stack is TypeScript (Next.js + Node/Bun), tRPC removes a whole layer of problems. You define a procedure on the server — the client gets full type-safety automatically, without code generation and without Swagger. Renamed a field in the Zod schema — TypeScript highlights all places on the frontend where it's used. tRPC reduces code by 2 times compared to REST + Swagger + openapi-typescript: no need to maintain a separate specification and generate types — everything is inferred from runtime validators. However, tRPC is not suitable if the API is consumed by third-party clients or mobile apps in other languages — in such cases we use GraphQL or REST with OpenAPI specification.

WebSocket and real-time: when SSE, when WS?

HTTP polling every 5 seconds is an illusion of real-time with up to 5 seconds delay and useless server load. For chats, live notifications, collaborative editing — WebSocket or Server-Sent Events. SSE is a one-way stream from server to client, works over ordinary HTTP, automatically reconnects. Suitable for notifications, data streaming, progress bars. WebSocket is bidirectional, needed for chats and collaborative features. Experience shows: 80% of 'real-time' tasks are solved with SSE, not WebSocket — fewer infrastructure complexities.

A typical mistake: opening a WebSocket connection for each page component. On one project, the dashboard opened 12 parallel WS connections. The correct approach is one connection manager at the application level, subscriptions through it. In our work results, we always transfer the connection scheme and a ready solution.

Swagger / OpenAPI as a contract

Documentation written after the fact becomes outdated the day after release. We write the OpenAPI 3.1 specification before development starts; it becomes the contract between frontend and backend. The frontend generates types via openapi-typescript, the backend validates incoming data using generated schemas. Contract deviation from implementation is caught on CI, not during review. For Laravel — l5-swagger or dedoc/scramble. For Node.js — @fastify/swagger or Zod + zod-to-openapi.

How to properly authenticate an API?

JWT with long-lived access tokens without rotation is a source of problems when compromised. The correct scheme: access token for 15 minutes, refresh token for 30 days with rotation on each use. Refresh token stored in an httpOnly cookie, access token in memory (not in localStorage). For inter-service communication — API Keys with scope limitations or mTLS. OAuth 2.0 with PKCE for public clients (SPA, mobile).

How to handle versioning and backward compatibility?

Breaking changes in an API without versioning break clients. Three approaches we use in projects:

We guarantee backward compatibility through automated checks (oasdiff) on CI.

How we develop APIs: step-by-step plan

1. Analysis — audit of current integrations, data schema compilation, protocol selection (REST/GraphQL/tRPC/WebSocket).
2. Contract design — OpenAPI or SDL (GraphQL) before the first line of code.
3. Development — implementation per contract, unit tests for each endpoint.
4. Load testing — k6: 500 virtual users, 10 minutes, p95 latency ≤ 200ms.
5. Deployment — CI/CD with backward compatibility check, automatic documentation publication.
6. Team training — handover of Postman collection or Playground, connection instructions.

What is included (deliverables)

• OpenAPI 3.1 specification (or SDL for GraphQL).
• Generated client types for TypeScript / Dart / Kotlin.
• Set of automated tests covering all endpoints (unit + integration).
• Load tests (k6) and report (p50/p95/p99 latency, RPS).
• Documentation in Swagger UI / Redoc / GraphiQL.
• Team training (2–4 hour workshop).
• Support for 30 days after delivery (per contract).

Our experience

• 10+ years in the API development market.
• 200+ completed projects (REST, GraphQL, WebSocket, tRPC).
• 50+ certified engineers (AWS, Kubernetes, API Design).
• Traffic savings averaging 85% when migrating from REST to GraphQL for mobile apps.
• 100% backward compatibility — not a single broken client in the last 3 years.

Timeline

API development for a typical SaaS project with 30–50 endpoints: from 3 to 8 weeks depending on business logic complexity and number of external integrations. Migration of an existing REST API to GraphQL: from 2 to 6 weeks. Adding a WebSocket layer to an existing backend: from 1 to 3 weeks. Cost is calculated individually after an audit. Get a consultation — contact us to discuss your project.