docs(blog): add WebRTC blog post link

[Sameerlite]

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem
• I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Mar 13, 2026 0:27am

[greptile-apps]

Greptile Summary

This PR updates litellm/blog_posts.json to replace the previously featured blog post (SERVER_ROOT_PATH regression incident report, dated 2026-02-21) with a new entry for "Realtime WebRTC HTTP Endpoints" (dated 2026-03-12). The file serves as a local fallback for the GetBlogPosts utility when the remote GitHub raw URL is unreachable, and as a seed for the in-process cache.

• The JSON structure is valid and matches the expected BlogPost schema (title, description, date, url).
• The posts array correctly contains one entry, consistent with the file's historical pattern of tracking the latest/featured post.
• No code logic, tests, or configuration files are affected by this change.

Confidence Score: 5/5

• This PR is safe to merge — it is a single-file documentation update with no code or logic changes.
• The change is limited to updating a JSON blog post entry in a data file used only as a local fallback. The JSON is valid, the schema is correct, and there are no functional code changes.
• No files require special attention.

Important Files Changed

Filename	Overview
litellm/blog_posts.json	Replaces the previous featured blog post (SERVER_ROOT_PATH incident report) with a new post about Realtime WebRTC HTTP Endpoints; valid JSON, correct schema structure.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[get_blog_posts called] --> B{LITELLM_LOCAL_BLOG_POSTS=true?}
    B -- Yes --> C[Load blog_posts.json\nlocal fallback]
    B -- No --> D{In-process cache\nvalid within 1hr?}
    D -- Yes --> E[Return cached posts]
    D -- No --> F[Fetch remote JSON\nfrom blog_posts_url]
    F -- Success --> G{Validate response\nnon-empty posts list?}
    G -- Valid --> H[Cache & return posts]
    G -- Invalid --> C
    F -- Failure --> C
    C --> I[Return posts from\nblog_posts.json]

Loading

_{Last reviewed commit: 8f769ef}