• Documentation
  • Blog
  • Pricing
  • FAQ
  • Contact
Sign InSign Up

Learn how tDoc's AI-driven, human-supported receptionists can elevate your practice.

ยฉ Copyright 2025 tDoc.io. All Rights Reserved.

About
  • Blog
  • Contact
  • Community
Product
  • Documentation
  • Quick Start Guide
  • Support
Legal
  • Privacy Policy
  • Terms of Service
  • Security & Compliance
  • Cookie Policy
  • Community
  • Changelog
  • Status
  • Pricing
  • Enterprise Plan
    • Quick Start Guide
    • Introduction
    • Platform Overview
    • Basic Concepts

API Keys

Learn how to manage API Keys to access tDoc's programmatic interfaces and integrations.

๐Ÿ”‘ API Keys Overview

โš ๏ธ Beta Feature: API Keys functionality is currently in beta and will be fully released in the future. This documentation provides a preview of planned capabilities.

tDoc will provide secure API access through developer-managed API keys, allowing programmatic interaction with the platform:

๐Ÿ” Types of API Keys

tDoc will support multiple API key types to address different security and access requirements:

  • Read-Only Keys: Limited access for data retrieval operations
  • Write Keys: Permissions to modify and create resources
  • Full Access Keys: Complete API access for advanced integrations
  • Scoped Keys: Custom-defined access limited to specific resources or operations

//: # (/images/docs/api/api-keys-management.png - API Keys Management Interface))

๐Ÿ”„ Key Lifecycle Management

Once released, you'll be able to manage the complete lifecycle of your API keys:

๐Ÿ†• Creating API Keys

  • Purpose-Defined: Label each key with its intended use
  • Expiration Settings: Set automatic expiration dates for enhanced security
  • Access Scoping: Limit each key to specific operations and resources
  • Environment Targeting: Create separate keys for development and production

๐Ÿ” Monitoring Usage

  • Activity Logs: Track all operations performed with each key
  • Usage Metrics: Monitor rate limits and consumption patterns
  • Anomaly Detection: Receive alerts for unusual access patterns

๐Ÿงช API Implementation

๐Ÿ“‹ Standard Authentication Flow

When implemented, the API authentication will follow industry-standard practices:

  • Bearer Authentication: Include your API key in request headers
  • JWT Support: Time-limited tokens for enhanced security

๐Ÿ›ก๏ธ Security Best Practices

tDoc's API system is being designed with security as a priority:

  • IP Restrictions: Limit API access to specific IP addresses or ranges
  • Rate Limiting: Protect against abuse with intelligent rate limiting
  • Audit Logging: Comprehensive records of all API operations

๐Ÿš€ Planned API Capabilities

The upcoming API release will support these key operations:

  • Event Management: Programmatically manage users and permissions
  • Task Automation: Trigger and monitor automated workflows
  • Integration Hooks: Connect with third-party services and tools

๐Ÿ’ป API Documentation

When released, comprehensive documentation will be available including:

  • Interactive API Reference: Try API calls directly from documentation
  • Code Samples: Ready-to-use examples in multiple languages
  • Tutorials: Step-by-step guides for common integration scenarios

Next Steps

While API Keys are in development, explore these related features:

  • Current Integration Options
  • Webhook Configuration
  • Third-Party Authentication
  1. ๐Ÿ”‘ API Keys Overview
    1. ๐Ÿ” Types of API Keys
    2. ๐Ÿ”„ Key Lifecycle Management
    3. ๐Ÿงช API Implementation
    4. ๐Ÿš€ Planned API Capabilities
    5. ๐Ÿ’ป API Documentation
    6. Next Steps
    • Personal Account
    • Team and Personal Workspace
    • Navigation
    • API Keys
    • Billing