API v4.2.3

Added

• Linode’s new Mumbai data center is now an available region (GET /regions).

• Added a new account cancellation endpoint: POST /account/cancel. This endpoint accepts an optional comments field and responds with a link to Linode’s exit survey.

• Added a new profile_update event action to the List Events endpoint (GET /account/events) and View Event endpoint (GET /account/events/{eventId}).

  This event will be issued when making requests to the PUT /profile and PUT /profile/preferences endpoints.

• Added User event actions to the List Events endpoint (GET /account/events) and View Event endpoint (GET /account/events/{eventId}).

  • user_create - This event will be issued when making requests to the POST /account/users endpoint.

  • user_update - This event will be issued when making requests to the PUT /account/users/{username} and PUT /account/users/{username}/grants endpoints.

  • user_delete - This event will be issued when making requests to the DELETE /account/users/{username} endpoint.

Changed

• Changed behavior of the configs parameter for the POST /linode/instances/{linodeId}/clone endpoint. When an empty array is passed to the configs parameter, no configuration profiles will be cloned from the source Linode.

  Previously, all configuration profiles would be cloned. All behaviors of the disks and configs parameters for this endpoint are now more extensively documented in the API reference.

Fixed

• When updating the email of an account (PUT /account) or of a user (PUT /profile), Linode will now send an email notification to the previous email address that describes this change.

• Fixed an issue where a user could not set permissions on a domain that contained errors.

• Fixed a malformed URL in the response for the Enable Managed Service endpoint (POST /managed/services/{serviceId}/enable).

• Fixed an issue in which SRV records could only be assigned a port number below 32767. Any port number is now accepted.

• Fixed a login error that could appear after a user’s session had expired, if the user also had two-factor authentication enabled.

• Reduced response time for the GET /support/tickets endpoint.