Packs for developers
Make packs, add to them and see who opened them from your own code, Zapier, Make or a CRM. The API sends and receives JSON over HTTPS and works on every plan. Plan limits apply, as in the app.
Using Claude or ChatGPT? Connect the Packs connector instead, at https://packs.co/mcp. Steps are in Settings, AI assistants.
Address
https://packs.co/api/v1Every call needs Authorization: Bearer <access token>. Send JSON bodies with Content-Type: application/json, up to 1 MB.
Signing in
Packs uses OAuth 2.1 with PKCE. The person whose packs you work with signs in to Packs and chooses Allow. Your code then acts as them, with the same access they have in the app. They can disconnect your app at any time in Settings, AI assistants.
- Register your app once. Send its name and redirect address to the registration endpoint and keep the
client_idyou get back. - Send the person to the authorize endpoint with your
client_id,redirect_uri,response_type=code, a PKCEcode_challenge(S256) andresource=https://packs.co/api/v1. - They sign in to Packs and choose Allow. We send them back with a code.
- Swap the code at the token endpoint for an access token (valid for an hour) and a refresh token. Use the refresh token for new access tokens.
Endpoints are listed at https://packs.co/.well-known/oauth-authorization-server.
# 1. Register your app
curl -X POST https://eyikeqfupzzrwmtkuhlc.supabase.co/auth/v1/oauth/clients/register \
-H "Content-Type: application/json" \
-d '{"client_name":"My app","redirect_uris":["https://example.com/callback"],
"token_endpoint_auth_method":"none","grant_types":["authorization_code","refresh_token"]}'
# 2. Send the person here
https://eyikeqfupzzrwmtkuhlc.supabase.co/auth/v1/oauth/authorize?client_id=CLIENT_ID&redirect_uri=https%3A%2F%2Fexample.com%2Fcallback
&response_type=code&code_challenge=CHALLENGE&code_challenge_method=S256
&resource=https%3A%2F%2Fpacks.co%2Fapi%2Fv1
# 4. Swap the code for tokens
curl -X POST https://eyikeqfupzzrwmtkuhlc.supabase.co/auth/v1/oauth/token \
-d grant_type=authorization_code -d code=CODE -d client_id=CLIENT_ID \
-d redirect_uri=https://example.com/callback -d code_verifier=VERIFIEREndpoints
{pack} is the pack's id or the code at the end of its link.
GET/me
Who the token belongs to, their plan and pack limit. A good first call.
GET/packs
Packs newest first, yours and team packs you can see, with links and open counts. Optional search and limit (1 to 100, 20 if left out).
POST/packs
Make a pack from a title, an optional heading and summary, and sections. Returns the new pack.
GET/packs/{pack}
One pack with its sections and items.
PATCH/packs/{pack}
Change the title, heading or summary, or send online: false to take the pack offline and online: true to put it back. An empty heading or summary removes it.
POST/packs/{pack}/sections
Add sections to the end of a pack. Nothing already there changes.
GET/packs/{pack}/stats
Opens, readers and questions waiting. On Pro and up, also who opened it, visits and time spent.
Make a pack
A pack has sections, and each section has items. An item is one of five kinds: text (simple HTML), steps (a timeline or process), quote, person (a contact card) or link. Links get their title and picture automatically. Up to 8 sections, 8 items each, 30 items in all.
curl -X POST https://packs.co/api/v1/packs \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"title": "Proposal for Northwind",
"heading": "Demand forecasting pilot",
"summary": "Start with the summary, then pricing.",
"sections": [
{ "title": "Summary", "items": [
{ "kind": "text", "html": "<p>An <strong>8-week pilot</strong> in 40 stores.</p>" }
]},
{ "title": "How it runs", "items": [
{ "kind": "steps", "steps": [
{ "name": "Set-up", "when": "Week 1" },
{ "name": "Results", "when": "Week 8", "detail": "Review against targets." }
]}
]},
{ "title": "Next steps", "items": [
{ "kind": "link", "url": "https://cal.com/maya/30min", "context": "Book a call" },
{ "kind": "person", "person": { "name": "Maya Patel", "role": "Account director",
"email": "maya@example.com" } }
]}
]
}'The pack is live at its link straight away, with the account's usual access setting. The reply includes link to share and edit_link for pictures, files, branding and passwords, which are set in the Packs editor.
Who opened it
curl https://packs.co/api/v1/packs/abc123/stats -H "Authorization: Bearer $TOKEN"
{
"pack": { "id": "…", "title": "Proposal for Northwind" },
"opens": 5, "readers": 3, "assistant_reads": 0,
"last_opened_at": "2026-11-17T09:12:00Z", "questions_waiting": 1,
"detail": "full",
"readers_detail": [
{ "email": "sarah@northwind.example", "visits": 2, "seconds": 360, … }
],
"questions": [ { "question": "Does the pilot need IT time?", … } ]
}On Free, detail is counts and the people and questions lists are null.
Errors
{ "error": { "code": "not_found", "message": "No pack found that you can see." } }- 400bad_requestThe body or the pack reference isn't right. The message says what to fix.
- 401unauthorizedNo token, or it has expired or been disconnected. Refresh it or sign in again.
- 402plan_limitThe account is at its plan's pack limit.
- 403forbiddenYou can read this pack but not change it.
- 404not_foundNo pack found that this person can see.
- 413too_largeThe body is over 1 MB.
- 500server_errorSomething went wrong on our side. Try again in a moment.
Fair use
The API can't delete packs, change who can open them, upload files or send anything to readers. Those stay in the app. Keep calls to a sensible rate. We may slow down or block apps that put the service at risk. Questions or ideas: hello@packs.co.