Sign in

Changes to Create a backup

POST /organizations/{organization}/databases/{database}/branches/{branch}/backups

Every recorded change to this endpoint, newest first. Back to the operation

Changed in 4 of the 24 revisions of this API.2113

  1. fa19f33052411
  2. 72506953f367181
  3. d710019068fb1
  4. 5e881928d77a211

What changed

  • fa19f33052411See the full diff
    • ○

      added the required property uncompressed_size to the response with the 201 status

      response-required-property-added

  • 72506953f367181See the full diff
    • ▲

      the response property actor became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property backup_policy became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property backup_policy/last_ran_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property backup_policy/next_run_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property backup_policy/schedule_day became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property backup_policy/schedule_week became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property completed_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property database_branch became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property database_branch/deleted_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property deleted_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property expires_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property restored_branches/items/deleted_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property schema_snapshot became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property schema_snapshot/linted_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property started_at became nullable for the status 201

      response-property-became-nullable

    • ▲

      the response property backup_policy became optional for the status 201

      response-property-became-optional

    • ▲

      the response property database_branch became optional for the status 201

      response-property-became-optional

    • ▲

      the response property schema_snapshot became optional for the status 201

      response-property-became-optional

    • ○

      added the required property backup_policy/display_name to the response with the 201 status

      response-required-property-added

  • d710019068fb1See the full diff
    • ▲

      the retention_value request property type/format changed from number/ to integer/

      request-property-type-changed

  • 5e881928d77a211See the full diff
    • ▲

      the backup_policy/schedule_day response's property type/format changed from string/ to number/ for status 201

      response-property-type-changed

    • ▲

      the backup_policy/schedule_week response's property type/format changed from string/ to number/ for status 201

      response-property-type-changed

    • ○

      removed the 0.00 enum value from the backup_policy/schedule_day response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 0.00 enum value from the backup_policy/schedule_week response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 1.00 enum value from the backup_policy/schedule_day response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 1.00 enum value from the backup_policy/schedule_week response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 2.00 enum value from the backup_policy/schedule_day response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 2.00 enum value from the backup_policy/schedule_week response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 3.00 enum value from the backup_policy/schedule_day response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 3.00 enum value from the backup_policy/schedule_week response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 4.00 enum value from the backup_policy/schedule_day response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 5.00 enum value from the backup_policy/schedule_day response property for the response status 201

      response-property-enum-value-removed

    • ○

      removed the 6.00 enum value from the backup_policy/schedule_day response property for the response status 201

      response-property-enum-value-removed

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