Channels

Public threads, grouped by where they are happening. Pick a place to read its topics.

HackerOne API Changelog

HackerOne · the whole ledger

Standing
read here
Read as
rss
Publishes
news
How this address is known
observed_link_candidate
Found through
declared by https://api.hackerone.com/ in its own markup
First listed
2026-09-18T19:16:55Z
Last looked at
2026-10-26T21:02:21Z
Address
https://api.hackerone.com/changelog.rss

What this estate kept from it

  1. Action may be required. Severity is now required by default for eligible new programs. Eligible existing programs switch to this default on September 21; their requirement settings remain unchanged until then. Entry-level VDPs and CVSS-only programs are excluded from that backfill. Integrations calling create report must send severity_rating when the destination program requires severity. Omitting it returns 422 identifying severity_rating; this validation previously surfaced as 500 on the Customer API. For programs accepting manual ratings, none is valid but distinct from a blank rating. Programs can disable the requirement in their submission settings.storykept 2026-09-18T20:04:08Z
  2. The send messages to hackers endpoint now returns a descriptive error when the Hacker Messaging feature is not enabled for the program. The status is unchanged (403 Forbidden); previously the response body carried no detail. The 403 response is now also documented in the API reference.storykept 2026-09-18T20:04:08Z
  3. Added the workaround attribute to cve_request objects and the create a CVE request endpoint. This optional string captures mitigations or workarounds to apply when a fix isn't available, and is published with the CVE.storykept 2026-09-18T20:04:08Z
  4. Clarified recipient handling on the send email endpoint. The email field may contain multiple addresses separated by ; or ,, and each address is now validated independently against the organization / verified-domain permission rule. Addresses that do not meet the rule are dropped and the email is sent only to the permitted recipients (the response message lists any dropped recipients); if no address meets the rule the request fails with a 400 Bad Request.storykept 2026-09-18T20:04:08Z
  5. Added the attachment_ids attribute to the create report endpoint. Pass the IDs of attachments previously uploaded via the attachments endpoint to associate them with the new report. To display an attachment inline in the vulnerability information, include its ID in the markdown using the {F<id>} syntax (for example, {F1337}).storykept 2026-09-18T20:04:08Z
  6. Added the first_to_agree attribute to the activity-agreed-on-going-public object. This nullable boolean indicates whether the actor was the first party (reporter or program) to agree to public disclosure.storykept 2026-09-18T20:04:08Z
  7. Documented the submitted_at attribute on report objects. This field has been present in customer API responses and is now formally documented. It contains the date and time the report was formally submitted to the program, corresponding to the \"Reported on\" date in the HackerOne UI. For reports submitted without drafting, submitted_at equals created_at. Also added submitted_at to hacker API report responses for parity.storykept 2026-09-18T20:04:08Z
  8. Added activity-report-prioritised-normal object. This activity is the normal-priority counterpart to activity-report-prioritised and fires when HAI evaluates a report and determines it does not warrant high-priority handling. It exposes the same high_priority and high_priority_reason attributes (with high_priority always false).storykept 2026-09-18T20:04:08Z
  9. 401 Unauthorized responses now include a detail explaining the denial when the cause is safe to disclosestorykept 2026-09-18T20:04:08Z
  10. Added activity-triage-intake-exited object. This activity fires when the triage intake process for a report ends without proceeding to validation (e.g. closed, needs more info, or aborted).storykept 2026-09-18T20:04:08Z
  11. Added view reports endpoint to retrieve findings matching a view's query configuration. This completes the findings API with support for executing saved view queries with pagination and sort order.storykept 2026-09-18T20:04:08Z
  12. Fixed multi-field sorting support for Reports and Activities endpoints. Both endpoints now accept comma-separated sort fields as documented. Reports endpoint supports per-field direction control with - prefix (e.g., sort=reports.swag_awarded_at,-reports.bounty_awarded_at). Activities endpoint accepts multiple sort fields with a single direction applied to all fields.storykept 2026-09-18T20:04:08Z
  13. Added REST API endpoints for managing findings workboard views. This includes endpoints to list views, create view, get view, update view, and delete view. Views provide filtered perspectives of findings with custom query strings, sort orders, and column configurations.storykept 2026-09-18T20:04:08Z
  14. Added REST API endpoints for managing findings workboards. This includes endpoints to list workboards, create workboard, get workboard, update workboard, and delete workboard. Workboards organize vulnerability findings into manageable boards.storykept 2026-09-18T20:04:08Z
  15. Added REST API endpoints for managing scope exclusions on programs. This includes endpoints to list scope exclusions, create a scope exclusion, update a scope exclusion, and delete a scope exclusion. These endpoints allow program managers to programmatically manage report categories excluded from rewards.storykept 2026-09-18T20:04:08Z
  16. Implemented rate limiting of 10 requests per minute for the billing transactions endpoint.storykept 2026-09-18T20:04:08Z
  17. Added severity_calculation_methods attribute to the Get Program endpoint. This field returns which severity calculation methods are currently accepted by the program (e.g. cvss_4_0, manual).storykept 2026-09-18T20:04:08Z
  18. Fixed the analytics endpoint returning empty results for SQL-driven dashboard keys (e.g. submission-signal) despite data being available. The organization_id parameter is now required and the endpoint returns a 400 error when it is missing or when the user does not have access to the specified organization.storykept 2026-09-18T20:04:08Z
  19. Added REST API endpoints for campaign management. This includes endpoints to list all campaigns, get campaign details, create a campaign, update a campaign, launch a campaign, and end a campaign prematurely. These endpoints allow program managers to programmatically manage bounty multiplier campaigns.storykept 2026-09-18T20:04:08Z
  20. Added REST API endpoint to get the bounty table for a program. This endpoint returns the active bounty table with severity-based reward amounts per row.storykept 2026-09-18T20:04:08Z
  21. Removed documentation of the obsolete endpoints to create, update and archive structured scopes on the program level. Assets are managed via the organization asset management endpoints.storykept 2026-09-18T20:04:08Z
  22. Added activity-report-triage-summary-updated object.storykept 2026-09-18T20:04:08Z
  23. Added REST API endpoints to approve a retest and reject a retest for a report.storykept 2026-09-18T20:04:08Z
  24. Added REST API endpoints to create an automation and update an automation for organizations. These endpoints enable programmatic automation lifecycle management — including code, configuration, events, and enabled state — making it possible to manage automation definitions as code via CI/CD pipelines.storykept 2026-09-18T20:04:08Z

A channel's standing is what this estate has done with it, never a judgement of what it publishes. What was kept is what this estate read at a time, not a claim that the channel still publishes it.

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.