# Where is the API reference for Pack endpoints?

**URL:** <https://connect.superhuman.com/t/where-is-the-api-reference-for-pack-endpoints/49006>\
**Category:** Making Packs\
**Created:** [May 28, 2024, 5:48pm UTC](https://connect.superhuman.com/t/where-is-the-api-reference-for-pack-endpoints/49006 "2024-05-28T17:48:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tobias\_Feistmantl](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/tobias_feistmantl/32/34315_2.png) [@Tobias\_Feistmantl](https://connect.superhuman.com/u/Tobias_Feistmantl)\
**Post date:** [May 28, 2024, 5:48pm UTC](https://connect.superhuman.com/t/where-is-the-api-reference-for-pack-endpoints/49006/1 "2024-05-28T17:48:17Z")

</div>

Is there an API reference for the pack endpoints?

They aren’t in the official [API reference](https://coda.io/developers/apis/v1).

Some endpoints I know exist:

- /packs
- /packs/{packId}
- /packs/{packId}/releases

---

<div class="post-metadata">

**Author:** ![Troy\_Larson](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/troy_larson/32/29176_2.png) [@Troy\_Larson](https://connect.superhuman.com/u/Troy_Larson)\
**Post date:** [May 28, 2024, 7:46pm UTC](https://connect.superhuman.com/t/where-is-the-api-reference-for-pack-endpoints/49006/2 "2024-05-28T19:46:10Z")

</div>

You’ll need to reference the [API source code in Github](https://github.com/coda/packs-sdk/blob/412b33742c6087ff5e5638fcfddea51a1c23016d/helpers/external-api/coda.ts).

Also there are a couple packs that help you (the second is mine 🙂 ).

Both rely on the SDK.

> **[Packs Metadata Pack, extend Coda with Packs... - Coda](https://coda.io/packs/packs-metadata-16745)**
>
> It's a Pack with a sync table called "Packs" that lists all of the Packs, including itself.
> 
> There's also a formula called "Pack" and a column format called "Pa

> **[Packs Magic Pack, extend Coda with Packs Magic - Coda](https://coda.io/packs/packs-magic-27905)**
>
> 🔧🚀 Packs Magic - Your Ultimate Pack Development Dashboard! 🎛️✨
> 
> Introducing the Packs Magic pack, the all-in-one toolkit that revolutionizes the way you deve

---

<div class="post-metadata">

**Author:** ![Eric\_Koleda](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/eric_koleda/32/50286_2.png) [@Eric\_Koleda](https://connect.superhuman.com/u/Eric_Koleda)\
**Post date:** [May 30, 2024, 7:55pm UTC](https://connect.superhuman.com/t/where-is-the-api-reference-for-pack-endpoints/49006/3 "2024-05-30T19:55:15Z")

</div>

Just to clarify - Those API endpoints for managing Packs are not officially supported and can change without warning. Use at your own risk!

---

<div class="post-metadata">

**Author:** ![Tobias\_Feistmantl](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/tobias_feistmantl/32/34315_2.png) [@Tobias\_Feistmantl](https://connect.superhuman.com/u/Tobias_Feistmantl)\
**Post date:** [June 1, 2024, 3:44pm UTC](https://connect.superhuman.com/t/where-is-the-api-reference-for-pack-endpoints/49006/4 "2024-06-01T15:44:13Z")

</div>

@Troy_Larson Awesome! I’ll check that out. Thanks!

I’ve also found the endpoints in the OpenAPI spec.

@Eric_Koleda why are they not standardized and documented? I mean they are used by the SDK, multiple packs, etc. A change in the API would break a lot of stuff.

---

<div class="post-metadata">

**Author:** ![Eric\_Koleda](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/eric_koleda/32/50286_2.png) [@Eric\_Koleda](https://connect.superhuman.com/u/Eric_Koleda)\
**Post date:** [June 11, 2024, 3:04pm UTC](https://connect.superhuman.com/t/where-is-the-api-reference-for-pack-endpoints/49006/5 "2024-06-11T15:04:17Z")

</div>

@Tobias_Feistmantl - The API endpoints were added to the API originally to support the Packs CLI and some other features in the product, but they weren’t officially released since we weren’t sure breaking changes would be needed as the platform settled into place. You are correct that other Packs use these endpoints as well, but all with the same caveats that it’s not completely safe to do so. While I think it’s unlikely we’ll make sweeping breaking changes at this point, that’s the risk you’ll have to accept if you want to use them.
