Versioning
Recommended upgrade path
- You can use the changelog to identify areas you may need to update
- Create a new API token for the new version or update your current API token to the new version and verify that it is working fine
- Once verified, you can upgrade the pinned version of the token here or use the new API token created
- 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