Changes to Vessel events (fishing, encounters, port visits, loitering)

Changed in 2 of the 21 revisions of this API.▲12○13

1. Aug 28, 2026560e8847c7b3▲12○1
2. Aug 8, 20264c4530760ba1○12

What changed

• Aug 28, 2026560e8847c7b3▲12○1See the full diff
  • ▲

    the response property data/count became optional for the status 200

    response-property-became-optional

  • ▲

    the response property data/date_range became optional for the status 200

    response-property-became-optional

  • ▲

    the response property data/event_type became optional for the status 200

    response-property-became-optional

  • ▲

    the response property data/events became optional for the status 200

    response-property-became-optional

  • ▲

    the response property data/total became optional for the status 200

    response-property-became-optional

  • ▲

    response property data/count list-of-types was widened by adding types null and number to media type application/json of response 200

    response-property-list-of-types-widened

  • ▲

    response property data/event_type list-of-types was widened by adding types null to media type application/json of response 200

    response-property-list-of-types-widened

  • ▲

    response property data/events list-of-types was widened by adding types null to media type application/json of response 200

    response-property-list-of-types-widened

  • ▲

    response property data/total list-of-types was widened by adding types null and number to media type application/json of response 200

    response-property-list-of-types-widened

  • ▲

    the data/date_range response's property type/format changed from object/ to / for status 200

    response-property-type-changed

  • ▲

    removed the required property data/date_range/end from the response with the 200 status

    response-required-property-removed

  • ▲

    removed the required property data/date_range/start from the response with the 200 status

    response-required-property-removed

  • ○

    added DateRange subschema #2 to the data/date_range response property anyOf list for the response status 200

    response-property-any-of-added

  This revision also has 15 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

• Aug 8, 20264c4530760ba1○12See the full diff
  • ○

    added the optional property code to the response with the 401 status

    response-optional-property-added

  • ○

    added the optional property code to the response with the 429 status

    response-optional-property-added

  • ○

    added the optional property code to the response with the 503 status

    response-optional-property-added

  • ○

    added the optional property hint to the response with the 401 status

    response-optional-property-added

  • ○

    added the optional property hint to the response with the 429 status

    response-optional-property-added

  • ○

    added the optional property hint to the response with the 503 status

    response-optional-property-added

  • ○

    added the optional property plan to the response with the 401 status

    response-optional-property-added

  • ○

    added the optional property plan to the response with the 429 status

    response-optional-property-added

  • ○

    added the optional property plan to the response with the 503 status

    response-optional-property-added

  • ○

    added the optional property reason to the response with the 401 status

    response-optional-property-added

  • ○

    added the optional property reason to the response with the 429 status

    response-optional-property-added

  • ○

    added the optional property reason to the response with the 503 status

    response-optional-property-added