New in Postman: Add Types to Your Collections

Integrating APIs
,
1

TL;DR
You can now add type information directly to your Postman Collections, whether you’re generating them from an API spec or editing an existing one. This makes them easy to test, debug, and collaborate on. It’s a small change with a big impact.

Why this matters
Types in Collections help teams:

  • Enforce stricter request validation.
  • Keep collections and docs in sync with the spec.
  • Reduce back-and-forth when onboarding new teammates.
  • Get smart suggestions when working in collections.

Resources

:thread::backhand_index_pointing_down:Use this thread to share:

  • :hammer_and_wrench: Workflow tips for getting started
  • :speech_balloon: Wins your team had using types
  • :light_bulb: Lightbulb moments where typed data made a difference
  • :exploding_head: Analogies that helped it all click (even weird ones, we love those)

We’re actively iterating. Your input helps shape what’s next.

2

:japanese_symbol_for_beginner: Beginner Tip
If you’re newer to APIs or Collections, think of Types like labels on your storage bins. Instead of guessing what goes where, you get a clear map of the structure.
Try this: Open a Typed-enabled Collection > Navigate to a request > go to the “Headers” tab > Explore adding more properties to a Request Header.

:gear: Intermediate Tip
→ Open a POST request in a Type-enabled Collection, open the Schema pane, and hit the Generate from Body button and watch the magic happen :magic_wand:

:building_construction: Advanced Tip
Working across multiple teams or managing a shared API spec? Types in Collections are a great way to enforce structure and reduce back-and-forth. Teams can use it to keep their collection and specs in a two-way sync without losing any type information.