Changes to List Incident Updates

Changed in 6 of the 30 revisions of this API.▲15●6○9

1. Aug 25, 202696314e3ca8ef○2
2. Jul 25, 2026e653c575dc15○2
3. Jul 13, 2026408fd86def03○2
4. Jul 10, 20264e4308be5bcf▲9●6○2
5. Aug 15, 20255b3f1f21cf76○1
6. Jun 2, 20259ad32c73fe39▲6

What changed

• Aug 25, 202696314e3ca8ef○2See the full diff
  • ○

    added the optional property included/items/anyOf[subschema #1: Incident]/relationships/tags to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property included/items/anyOf[subschema #2: Schedule]/relationships/tags to the response with the 200 status

    response-optional-property-added

• Jul 25, 2026e653c575dc15○2See the full diff
  • ○

    added the required property included/items/anyOf[subschema #1: Incident]/attributes/published to the response with the 200 status

    response-required-property-added

  • ○

    added the required property included/items/anyOf[subschema #2: Schedule]/attributes/published to the response with the 200 status

    response-required-property-added

• Jul 13, 2026408fd86def03○2See the full diff
  • ○

    added the optional property included/items/anyOf[subschema #1: Incident]/attributes/meta to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property included/items/anyOf[subschema #2: Schedule]/attributes/meta to the response with the 200 status

    response-optional-property-added

• Jul 10, 20264e4308be5bcf▲9●6○2See the full diff
  • ▲

    for the query request parameter include, the type/format was changed from string/ to array/

    request-parameter-type-changed

  • ▲

    for the query request parameter sort, the type/format was changed from string/ to array/

    request-parameter-type-changed

  • ▲

    the response property data/items/attributes/created/human became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/attributes/created/string became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/attributes/status/human became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/attributes/status/value became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/attributes/updated/human became nullable for the status 200

    response-property-became-nullable

  • ▲

    the response property data/items/attributes/updated/string became nullable for the status 200

    response-property-became-nullable

  • ▲

    the data/items/attributes/status/value response's property type/format changed from string/ to integer null/ for status 200

    response-property-type-changed

  • ●

    added the new Fixed enum value to the data/items/attributes/status/human response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new Identified enum value to the data/items/attributes/status/human response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new Investigating enum value to the data/items/attributes/status/human response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new Reported enum value to the data/items/attributes/status/human response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new Watching enum value to the data/items/attributes/status/human response property for the response status 200

    response-property-enum-value-added

  • ●

    added the new undefined enum value to the data/items/attributes/status/human response property for the response status 200

    response-property-enum-value-added

  • ○

    added the optional property data/items/relationships to the response with the 200 status

    response-optional-property-added

  • ○

    added the optional property included to the response with the 200 status

    response-optional-property-added

• Aug 15, 20255b3f1f21cf76○1See the full diff
  • ○

    media type application/json was changed to a more specific media type application/vnd.api+json for the response status 200

    response-media-type-name-specialized

• Jun 2, 20259ad32c73fe39▲6See the full diff
  • ▲

    the response property links/first became optional for the status 200

    response-property-became-optional

  • ▲

    the response property links/last became optional for the status 200

    response-property-became-optional

  • ▲

    the response property links/next became optional for the status 200

    response-property-became-optional

  • ▲

    the response property links/prev became optional for the status 200

    response-property-became-optional

  • ▲

    the data/items/attributes/id response's property type/format changed from string/ to integer/ for status 200

    response-property-type-changed

  • ▲

    the data/items/attributes/updateable_id response's property type/format changed from string/ to integer/ for status 200

    response-property-type-changed