1. You can use the changelog to identify areas you may need to update
  2. Use the Bugcrowd-Version header to try out a new version
  3. Once verified, you can upgrade the pinned version of the token here
  4. Remove use of Bugcrowd-Version header as it is no longer needed (optional)

What you can expect from each version

  • Request parameters, headers, response schema, and error messages will remain consistent for a single version
  • Rate limits will remain consistent or improve, never reduce the limits on a version
  • Most behavior and final validation will remain consistent with slight possibilities for changes to a downstream validation causing a new 422 Unprocessable Entity error to be returned.