Prompt
Do I need a separate portal for partner API docs?
Latest observation
Oct 4, 2026
OpenAI APIWeb search: off
Not necessarily.
If your partner API docs are:
- public or semi-public,
- relatively simple,
- and meant to be consumed alongside your main developer docs,
you can often keep them in the same portal and just create a dedicated Partner API section with:
- separate navigation,
- partner-specific auth/setup guides,
- examples and sandbox info,
- and access control if needed.
You likely want a separate portal if:
- partners need a distinct login or access model,
- the content is materially different from public developer docs,
- you need different branding or onboarding,
- or you want to manage permissions, analytics, and versioning independently.
A good rule of thumb:
- One portal if the experience can be unified cleanly.
- Separate portal if partner docs require a different audience, permissions, or lifecycle.
If you want, I can help you decide based on your audience, access model, and current doc setup.