# Machines OpenAPI spec omissions

**URL:** <https://community.fly.io/t/machines-openapi-spec-omissions/27255>\
**Category:** General\
**Tags:** wishlist, docs, machines, certificates\
**Created:** [February 28, 2026, 5:54pm UTC](https://community.fly.io/t/machines-openapi-spec-omissions/27255 "2026-02-28T17:54:05Z")\
**Posts on this page:** 1\
**Showing post:** 30

<div class="post-metadata">

**Author:** ![praneetloke](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/praneetloke/32/14758_2.png) [@praneetloke](https://community.fly.io/u/praneetloke)\
**Post date:** [October 3, 2026, 4:24am UTC](https://community.fly.io/t/machines-openapi-spec-omissions/27255/30 "2026-10-03T04:24:49Z")

</div>

I have been testing the Pulumi provider. It mostly works. The following are a few of the observations I made.

### Network Policies

[Network policies API](https://docs.fly.io/machines/guides-examples/network-policies#api-summary) is listed in the docs here but it’s missing in the spec. I don’t see any other way to manage them.

Moreover, `POST /v1/apps/<app_name>/network_policies` is used for both create _and_ update. It would be great if there was a separate endpoint for updating a policy similar to the [DELETE endpoint](https://docs.fly.io/machines/guides-examples/network-policies#delete-a-policy): `DELETE /v1/apps/<app_name>/network_policies/<policy_id>`.

There is also no endpoint to fetch a single network policy by its id.

### Storage Objects

I am curious if there is any plan to add APIs to manage the following resources:

- [Fly.io](http://Fly.io) Storage (Tigris) Buckets to the Machines API?
- Fly Kubernetes Service

I realize it’s _Machines_ API, so maybe a separate “platform” API group?

### Rate Limits

The rate limit is easily triggered by the metadata endpoints. Trying to mutate (add/update/delete) multiple metadata keys for a machine will result in 429s. I can work around this by slowing-down the metadata requests for a machine but I wanted to mention it in case there is any room for easing the limits for certain endpoints. The alternate, of course, is that a user manages metadata as part of the machine config rather than using the dedicated `/metadata/{key}` endpoint. I am going to do more testing and part of it is to port something off Render.

---

_[View the full topic](https://community.fly.io/t/machines-openapi-spec-omissions/27255)._