# Fly API access

**URL:** <https://community.fly.io/t/fly-api-access/1625>\
**Category:** General\
**Created:** [June 2, 2021, 3:54am UTC](https://community.fly.io/t/fly-api-access/1625 "2021-06-02T03:54:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![michael](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/michael/32/16_2.png) [@michael](https://community.fly.io/u/michael)\
**Post date:** [June 2, 2021, 5:41am UTC](https://community.fly.io/t/fly-api-access/1625/2 "2021-06-02T05:41:46Z")

</div>

This isn’t a bad idea at all, several other customers are doing it too. We haven’t put much energy into documenting the api or making it friendly to use, but it’ll get the job done and is always improving. It’s a GraphQL api with a playground you can explore at [GraphQL Playground](https://api.fly.io/graphql).

Flyctl uses it, so checkout the [go code](https://github.com/superfly/flyctl/blob/master/api/resource_apps.go) for a reference.

Also, you’ll likely want to [isolate customer apps by putting them on different networks](https://community.fly.io/t/multi-tenant-applications/375/11), otherwise they can connect to each other. We’ll be improving support for this in the coming weeks.

---

_[View the full topic](https://community.fly.io/t/fly-api-access/1625)._