Skip to content

VAP15-54 docs: document subsystem server credentials - #1223

Draft
jeffrey-hoekman-vapi wants to merge 2 commits into
jeffhoekman/vap15-53-webhook-credentials-withheld-caller-supplied-server-urlfrom
jeffhoekman/vap15-54-message-options-server-overrides
Draft

jeffrey-hoekman-vapi wants to merge 2 commits into
jeffhoekman/vap15-53-webhook-credentials-withheld-caller-supplied-server-urlfrom
jeffhoekman/vap15-54-message-options-server-overrides

Conversation

@jeffrey-hoekman-vapi

Copy link
Copy Markdown
Contributor

Stacked on #1221 (VAP15-53). Documents credential withholding for the subsystem server URL path — tools, knowledge bases, custom voices, dynamic handoff/transfer destinations, custom endpointing — per VAPSEC-627.

Draft, not ready to merge. The behavior this describes is VapiAI/vapi#19542, which is unreviewed with work outstanding.

Changes

  • fern/server-url/server-authentication.mdx — new #### Subsystem server URLs subsection: a table mapping each webhook to the server it is sent to, the provenance-inheritance rule, and a <Warning> on the mixed case (a saved assistant whose voice / tools / KB are replaced via assistantOverrides carries caller-authored subsystem servers).
  • fern/squads/handoff.mdx<Warning> before the dynamic-handoff examples, linking to that anchor.
  • fern/squads/handoff.mdx — added the missing Authorization header to the intelligent-routing example.

Provisional — re-verify before merge

The prose asserts one rule — a subsystem server is caller-authored exactly when the assistant carrying it is — taken from the VAPSEC-627 Scope section and the PR title, not from merged code. The ticket notes the design is still open: a per-subsystem provenance bit was considered and rejected in favor of binding at the send site.

Before merging, re-check against the merged behavior:

  • the six-row webhook table is complete and correctly attributed
  • the inheritance rule survived review, and the assistantOverrides mixed case behaves as written
  • whether the direct serverCredentialGet callers on the custom-voice path (firstMessageContext, liveCallFunctions.say) are in scope

Merge gate

Blocked by VAPSEC-627 / VapiAI/vapi#19542, which sits on top of the VAPSEC-564 stack. Merge order: 564 stack → VAP15-53 → 627 → this.

Notes

  • fern check: 0 errors, 12 pre-existing OpenAPI discriminator warnings (unrelated).
  • If a docs preview builds, it will render ENFORCEMENT_DATE_TBD from the base branch — that is VAP15-53's placeholder, tracked there, not part of this diff.

Refs VAP15-54, VAPSEC-627.

🤖 Generated with Claude Code

@github-actions

Copy link
Copy Markdown
Contributor


Some webhooks go to a URL owned by a subsystem rather than to your assistant's webhook URL - a tool, a knowledge base, a custom voice, a dynamic handoff or transfer destination, or a custom endpointing provider each carry their own `server` block:

| Webhook | Server it is sent to |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consider a one-dimensional list here, unless you feel that makes the behavior of function-call unclear

Comment thread fern/squads/handoff.mdx Outdated
"url": "https://api.example.com/intelligent-routing"
"url": "https://api.example.com/intelligent-routing",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should probably be renamed to distinguish it from the Vapi org API key. Maybe something like WEBHOOK_AUTH_SIGNATURE or OUTBOUND_PROVIDER_AUTH_KEY?

@jeffrey-hoekman-vapi
jeffrey-hoekman-vapi force-pushed the jeffhoekman/vap15-53-webhook-credentials-withheld-caller-supplied-server-url branch from 056e643 to a2c1858 Compare September 16, 2026 18:01
@jeffrey-hoekman-vapi
jeffrey-hoekman-vapi force-pushed the jeffhoekman/vap15-54-message-options-server-overrides branch from cfe3c41 to 779ae5a Compare September 16, 2026 18:22
@jeffrey-hoekman-vapi jeffrey-hoekman-vapi changed the title VAP15-54 docs(server-url): document credential withholding for subsystem server urls VAP15-54 docs: document subsystem server credentials Sep 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Extends VAP15-53 to the webhooks that go to a subsystem's own server
rather than the assistant's webhook url - tools, knowledge bases,
custom voices, dynamic handoff and transfer destinations, and custom
endpointing providers.

The rule is provenance inheritance: a subsystem server follows the
assistant carrying it. A saved assistant keeps org credentials; a
transient assistant or assistantOverrides is caller-authored and gets
none. Calls out the mixed case, a saved assistant with an overridden
voice, tools or knowledge base.

Also gives the intelligent-routing handoff example an Authorization
header. It was the only dynamic-destination example teaching a bare
unauthenticated server url, directly under one that has auth. That
content now lives in squads/handoff/destinations.mdx, which main split
out of the handoff page.

Provisional: VAPSEC-627 (#19542) is unreviewed and still changing.
Re-verify the table and the inheritance rule against the merged
behavior before this ships.

Refs VAP15-54, VAPSEC-627

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@jeffrey-hoekman-vapi
jeffrey-hoekman-vapi force-pushed the jeffhoekman/vap15-54-message-options-server-overrides branch from 779ae5a to 76b3bd2 Compare September 16, 2026 19:40
@github-actions

Copy link
Copy Markdown
Contributor

Same §9 fix Steve applied across VAP15-53: a spaced hyphen standing in
for a dash becomes a period, with the colon left to introduce the table.
Also fixes the number disagreement the dash was hiding - "a tool, a
knowledge base ... each carry" now reads as plurals throughout.

Refs VAP15-54

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants