Collections need conversion or alignment with OpenAPI.
Provider migration
Migrate from Postman docs to Bloom
Postman collections are useful for collaboration and exploration, but public developer docs and generated SDKs need source control, migration reports, and release readiness.
Checks
What to check
Examples and auth settings need docs-safe rendering.
Generated SDKs need package metadata and runtime checks.
Public docs URLs need a redirect and SEO plan.
Checks
Migration checklist
Export source docs, OpenAPI files, theme settings, redirects, and custom domains.
Decide which content remains hand-authored and which references are generated.
Generate a preview before touching production DNS.
Run SDK and docs checks before publishing packages or indexing new pages.
Details
Why Bloom fits
Bloom is OpenAPI-first.
The migration report shows the SDK, docs, and launch work before anything goes live.
SDKs, docs preview, sitemap, and llms.txt live in the same workflow.
The dashboard shows what is generated, ready, and waiting on review.
Related pages