Integrate Typely and Claude

Typely ships an AI-friendly API. Point Claude at it and it can edit your Markdown site directly — no more copy-pasting drafts between chat and dashboard.

Here's the workflow we recommend when you first hook the two together.

1. Give Claude an API key

In your dashboard: Account → API Keys → Create a new API key. Name it something like Claude, set it to Read and write, allow the modules you want it to touch (page, theme, blogs, integrations is a good starting set), and pick an expiry.

Copy the key when it appears — you'll only see it once. Paste it into your Claude MCP config, or into an environment variable the skill you're using reads.

2. Let Claude scan your integrations first

Before Claude edits anything, ask it what's already connected:

Before we start, list my Typely integrations.

Under the hood Claude calls GET /api/v1/sites/<site_id>/integrations, which returns only integrations you've actually connected — plus the exact shortcode syntax it can safely emit for each. If Dropbox isn't in the list, gallery shortcodes will render as nothing. Fix that before you ask Claude to place images.

3. Connect Dropbox once

Go to Integrations → Dropbox Gallery → Connect. Pick a folder — for example /typely-site — and Typely will sync it. From then on, anything you drop into that folder in Dropbox lands on your Typely CDN within a minute or two.

Your Dropbox folder becomes your image library. Your desktop, your phone, your camera roll — all of them push straight into the site.

4. The image workflow

Ask Claude something like:

I just added three product photos to my Dropbox at /typely-site/products. Add them to my homepage under a new "Products" section.

Claude will:

1. Read your current page — GET /api/v1/sites/<site_id>/page
2. Add a new section with [dropbox-gallery](/products) — the shortcode that renders every image in that Dropbox subfolder
3. Save the result as a draft — PUT /api/v1/sites/<site_id>/draft

The images are already on Typely (Dropbox synced them). Claude never touches binary — it just tells your page which folder to render.

5. Review before publishing

Don't let Claude publish blind. Open the dashboard, go to Page, and you'll see the draft it saved. If it's right, hit Publish. If not, roll it back:

• DELETE /api/v1/sites/<site_id>/draft — discard
• POST /api/v1/sites/<site_id>/draft/publish — ship it

6. Anything the dashboard does, the API does

Blogs, theme colours, SEO metadata, site basics — all of them live under /api/v1. The full endpoint list is at hellotypely.io/api. The rule is: if it's a button in the dashboard, there's an endpoint that mirrors it.

What Claude is deliberately not allowed to do

Even a read+write key can't:

• Rotate OAuth credentials (Dropbox, Kinde). You connect integrations yourself from the dashboard.
• Read Stripe keys, Dropbox app secrets, or anything else the backend keeps to itself.
• Bill you. Site creation and upgrades work over the API, but the actual payment goes through a Stripe Checkout link Claude hands back to you.

That's on purpose. The API gives Claude a sharp scalpel for content and configuration, and a very blunt one for anything financial or credential-shaped.

TL;DR

1. Create a Typely API key, scoped to what you actually want Claude to touch.
2. GET /integrations first — Claude should only ever use shortcodes that are actually connected.
3. Drop images in Dropbox; Claude edits the shortcodes that point at them.
4. Save as a draft, review, publish.

Was it helpful?

Let us know how you're using Claude with Typely — what worked, what didn't, and what you'd like the API to do next. We fold the good stuff back into the docs.