https://blog.baifan.site/en/tags/api/ Recent content in API on ByF (BaiFan) · Daily Deep Think Hugo -- gohugo.io en blog@baifan.site (ByF (BaiFan)) blog@baifan.site (ByF (BaiFan)) CC BY-NC 4.0 Tue, 14 Apr 2026 14:00:00 +0800 https://blog.baifan.site/en/ai-api-suffixes-explained/ Tue, 14 Apr 2026 14:00:00 +0800 blog@baifan.site (ByF (BaiFan)) https://blog.baifan.site/en/ai-api-suffixes-explained/ <p>We often see URLs like these:</p> <div class="highlight-wrapper"><div class="highlight"><div class="chroma"> <table class="lntable"><tr><td class="lntd"> <pre tabindex="0" class="chroma"><code><span class="lnt">1 </span><span class="lnt">2 </span><span class="lnt">3 </span></code></pre></td> <td class="lntd"> <pre tabindex="0" class="chroma"><code class="language-plaintext" data-lang="plaintext"><span class="line"><span class="cl">/v1/chat/completions </span></span><span class="line"><span class="cl">/v1/messages </span></span><span class="line"><span class="cl">/v1/responses</span></span></code></pre></td></tr></table> </div> </div></div> <p>These suffixes are not decoration — they define a complete request and response data structure. Pick the wrong one and your code either errors out or silently loses data.</p> <!-- more --> <p>This article starts at <code>/v1/completions</code> and works its way to <code>/v1/responses</code>, explaining what each suffix stands for, why it was designed that way, and where the common pitfalls are.</p>