Skip to main content
Question

What Beta header needs to be passed while creating stream via the http post?

  • October 20, 2025
  • 2 replies
  • 33 views
J
Seasoned ⭐️⭐️⭐️

I am stumbling through the Beta documentation. When I try to run the http post to create a Stream (as described here), I get this error:

The feature can only be used with [alpha, beta] headers

I found documentation that seemed relevant, but it seems the format of the header is this cdf-version: 20230101-beta 
https://api-docs.cognite.com/20230101/#section/API-versions/Beta-versions

How do I know what date should I put into the header to gain access to the Streams beta feature?

    2 replies

    J
    Seasoned ⭐️⭐️⭐️
    • Jan Dolejsi
    • Author
    • Seasoned ⭐️⭐️⭐️
    • October 21, 2025

    I tried with plain 
    headers={'cdf-version': 'beta'}, 
    … and ​@Richard Booth confirmed that is the right thing. Would be good if this was mentioned in the opening message of this community. I know that your time is valuable, but mine is too.

      Everton Colling
      Expert ⭐️⭐️⭐️⭐️
      Forum|alt.badge.img
      • Everton Colling
      • Expert ⭐️⭐️⭐️⭐️
      • October 21, 2025

      Hi ​@Jan Dolejsi,

      I understand your frustration, but I need to be direct: this is an invite-only private beta. By accepting the invitation, you agreed to test pre-release features with incomplete documentation, potential bugs, and evolving APIs. That's the nature of beta testing.

      The header format is cdf-version: beta as you've discovered. The documentation is being refined and will be improved before general availability.

      Your feedback on gaps in the documentation is noted and valuable. However, comments like "your time is valuable, but mine is too" aren't constructive. Everyone's time here is valuable: the engineers building these features, the people documenting them, and the community members helping each other.

      If the current state of the beta doesn't align with your timeline or expectations, you're welcome to pause your testing and return when the feature will have complete documentation and full SDK support in early 2026. There's no obligation to participate in beta testing if it's not a good fit.

      We appreciate beta testers who come ready to collaborate, ask questions, and work through the rough edges together. That's how we make the product better for everyone.

        Terms & ConditionsAccessibility statement