v4.101.0

Added

• You can now deactivate Payment Methods by accessing the Payment Method Delete (DELETE /account/payment-methods/{paymentMethodId}) endpoint.

• Linode APIv4 now supports adding an autoscaler configuration for Node Pools using the Linode Kubernetes Engine (LKE) endpoints listed below. Note: While adding an autoscaler config is supported by the Linode APIv4, issuing requests to these endpoints will not yet take any effect on your Node Pools. The cluster-autoscaler will be available in a subsequent Linode Kubernetes Engine release. Please refer to the LKE Changelog to learn when adding an autoscaler config for Node Pools is released.

  • Kubernetes Cluster Create (POST /lke/clusters)
  • Node Pool Create (POST /lke/clusters/{clusterId}/pools)
  • Node Pool Update (PUT /lke/clusters/{clusterId}/pools/{poolId})

v4.100.1

Added

• Linode now accepts Google Pay! You can now add google_pay type Payment Methods when accessing the Payment Method Add (POST /account/payment-methods) endpoint.

• The 202 Error code has been added to the Responses section of the specification. 202 responses are currently possible when using the following endpoints:

  • Payment Make (POST /account/payments)
  • Staged/Approved PayPal Payment Execute (POST /account/payments/paypal/execute)

• Restricted users can now be given the ability to add Firewalls by setting the add_firewalls global grant when accessing the User's Grants Update (PUT /account/users/{username}/grants) endpoint.

v4.99.0

Added

• You can now view individual Payment Method objects by accessing the Payment Method View (GET /account/payment-methods/{paymentMethodId}) endpoint.

• You can now set an existing Payment Method as the default method by accessing the Payment Method Make Default (POST /account/payment-methods/{paymentMethodId}/make-default) endpoint.

Changed

• The id property is now returned for Payment Method Objects when accessing the Payment Methods List (GET /account/payment-methods) endpoint.

v4.98.0

Added

• Null MX Domain Records can now be created when accessing the Domain Record Create (POST /domains/{domainId}/records) and Domain Record Update (PUT /domains/{domainId}/records/{recordId}) endpoints.

v4.97.2

Changed

• The Maintenance List (GET /account/maintenance) beta endpoint's "status" property has been updated as follows:
  • Maintenance objects that were formerly returned as ready are now returned as pending.
  • completed Maintenance objects are no longer returned at this endpoint.

v4.97.1

Fixed

• A bug in the API spec that prevented developers.linode.com from building was fixed.

v4.97.0

Added

• Manage your Account's payment options with the new Payment Method Add (POST /account/payment-methods) endpoint.

• Promo Codes for new signups can now be redeemed with the Promo Credit Add (POST /account/promo-codes) endpoint. Previously, Promo Codes were entered only while signing up for a new account.

• You can now delete individual LKE Nodes with the new Node Delete (DELETE /lke/clusters/{clusterId}/nodes/{nodeId}) endpoint.

Changed

• The Credit Card Add/Edit (POST /account/credit-card) has been deprecated. Please use the new Payment Method Add (POST /account/payment-methods) endpoint to manage your Account's credit card information.

• The Maintenance List (GET /account/maintenance) beta endpoint is now filterable by the when property, allowing you to filter maintenance objects based on their date.

• LKE Node Pools are now taggable when using the Node Pool Create (POST /lke/clusters/{clusterId}/pools) and Node Pool Update (PUT /lke/clusters/{clusterId}/pools/{poolId}) endpoints.

• Profile referral data, including the referral code, is now only accessible after an Account has an established payment history when using the Profile View (GET /profile) and Profile Update (PUT /profile) endpoints.

v4.96.0

Changed

• The following endpoints are now out of Beta and accessible from the "v4" path:

  • Image Upload (POST /images/upload)
  • Payment Methods List (GET /account/payment-methods)

• The Payment Methods List (GET /account/payment-methods) endpoint's method property has been changed to type, and its is_default property type has been changed to a boolean value.

v4.95.0

Changed

• Linode Disks can now be created from Account-specific ("private/") Images that a user has read_only or read_write access to with the Linode Create (POST /linode/instances) or Disk Create (POST/linode/instances/{linodeId}/disks) endpoints. Previously, only users with read_write access to an Account Image could create disks from that Image.

Fixed

• A bug has been fixed that prevented filtering the Firewalls List (GET /linode/instances/{linodeId}/firewalls) endpoint for the created, id, label, tags, and updated properties.

v4.94.0

Added

• The Payment Methods List (GET /account/payment-methods) beta endpoint is now available. Access this endpoint to view a list of the available payment methods for your account. At this time, only the primary credit card for your account is returned from this endpoint; additional payment methods will be listed as they become available.

Fixed

• The response body for the Image Upload (POST /images/upload) beta endpoint has been corrected to state that the upload_to property is returned. Previously, the specification stated that the upload_url property was returned.

• When deploying a new Linode from an Image using the Linode Create (POST /linode/instances) endpoint, the Image Disk is now created with the maximum allowed disk space (minus the size of the Swap Disk). Previously, the Image Disk was created with the minimum allowed size based on the Image, and required resizing to use the maximum available space.

• When creating a new Disk from an Image with the Disk Create (POST /linode/instances/{linodeId}/disks) endpoint, the filesystem for the Image is now used unless otherwised specified. Previously, the ext4 default filesystem was used unless otherwise specified.

• The "v4" server path has been enabled for the VLANs List (GET /networking/vlans) endpoint.

• The description for the Linode "interfaces" property has been updated to clarify that public IP addresses are still assigned but not usable without manual configuration when no public interface is configured.