Skip to content

History / TelegramBotClient

Revisions

  • Prefer PAIR_LOGGER_TELEGRAM_BOT_TOKEN for logger Introduce PAIR_LOGGER_TELEGRAM_BOT_TOKEN as the preferred env var for Pair logger Telegram notifications and update docs and examples accordingly. Changed references in Configuration-file.md, Logger.md, and TelegramBotClient.md; updated example env and the Logger usage to read Env::get('PAIR_LOGGER_TELEGRAM_BOT_TOKEN'). TELEGRAM_BOT_TOKEN remains supported as a legacy fallback and as the generic token for direct TelegramBotClient instances.

    @viames viames committed Jun 8, 2026
  • Docs: expand API & Aircall docs, add Google pages Large documentation updates and additions: expanded the API, ApiController and ApiResponse guides with clearer lifecycle, middleware, idempotency and JSON handling examples; clarified ActiveRecord behavior, forms and pagination notes; refactored Aircall integration docs into an AircallAPI cookbook and enriched AircallClient reference with usage examples, error-handling guidance, and production patterns; added Google-related pages (GoogleAddress, GoogleGeocoder, GoogleMaps, GoogleMapsClient, GooglePlacesService). Various examples and small clarifications added across many markdown pages to improve developer guidance.

    @viames viames committed Mar 26, 2026