New token deprecation warning for the legacy (v3) API

Previously an authentication token with a date-based default version could be used to access the Legacy (v3) API. On Wednesday November 24th (in 7 days) this will no longer be possible. Attempting to access the Legacy (v3) API with a token that uses a date-based version will return a 404 error with a specific message about the token’s version. To prevent this please downgrade the default version of your token to Legacy to continue using the Legacy (v3) API here.

You can still use the new API with a Legacy API token, but you will need to ensure to pass the Bugcrowd-Version parameter when using the new API in addition to specifying v4 in the Accept header as mentioned here.

  • The legacy (v3) API will now 404 if used with a new auth token