Bravely Link API

Paste from a chat

No agent and no key. Give this prompt to ChatGPT or any chat AI. It asks about you and your links, then answers with your whole page as one block of text.

I want you to build my Bravely Link page, a single page that holds all my links. Ask me what you need, one question at a time: my name or brand, a one-line bio, and each link I want with a short label. Suggest a handle (3 to 30 lowercase letters, numbers or dashes). When I say I'm done, reply with only one JSON code block in exactly this format and nothing else:

```json
{
  "bravely_link": 1,
  "handle": "samrivera",
  "title": "Sam Rivera",
  "bio": "Trail runner. Photos from the long way round.",
  "theme": "classic-dark",
  "link_style": "classic",
  "links": [
    {
      "type": "header",
      "label": "Start here"
    },
    {
      "label": "My newsletter",
      "url": "https://example.com/news",
      "subtitle": "Every Sunday"
    },
    {
      "label": "Instagram",
      "url": "https://instagram.com/samrivera"
    }
  ]
}
```

Rules: every link needs a "label" and a full "url" starting with https://. A row with "type": "header" has only a label. "subtitle" is optional, at most 100 characters. "theme" is one of: classic-dark, paper-light, sunset, mono, ocean, ember, aurora, forest, blush, sky. "link_style" is one of: classic, pill, tall, outline. The title is at most 120 characters and the bio at most 500. Leave out "avatar_url" unless I give you the address of a picture. Keep labels short. Never invent a link I did not give you.

Then open the builder, choose Import and paste the whole answer. You see the page before anything is made, it opens as a draft, and publishing stays your click.

Open the builder

Quick start

For an agent, or a script, that can make web requests.

1. Make a key

   Sign in at https://link.bravely.dev/ and make a key under API keys. A key is shown once and works only on its owner's pages.

2. Create your page

   Put your key in place of YOUR_KEY and the handle you want in place of your-handle, in the address and in the document.

   curl -X PUT https://link.bravely.dev/api/v1/pages/your-handle \
     -H "Authorization: Bearer YOUR_KEY" \
     -H "Content-Type: application/json" \
     -d '{
       "bravely_link": 1,
       "handle": "your-handle",
       "title": "Sam Rivera",
       "bio": "Trail runner. Photos from the long way round.",
       "theme": "classic-dark",
       "link_style": "classic",
       "links": [
         {
           "type": "header",
           "label": "Start here"
         },
         {
           "label": "My newsletter",
           "url": "https://example.com/news",
           "subtitle": "Every Sunday"
         },
         {
           "label": "Instagram",
           "url": "https://instagram.com/samrivera"
         }
       ]
     }'

   The answer is the page as it was stored, with a warning for anything it changed. Nothing is public yet.

3. Publish it

   curl -X POST https://link.bravely.dev/api/v1/pages/your-handle/publish \
     -H "Authorization: Bearer YOUR_KEY"

   Now it is live at bravely.link/your-handle. To change it later, read the page, edit the document, send it back and publish again. Keep each link’s id and its click counts stay with it.

Or hand your agent one address. It describes every call, field and limit on this page:

https://link.bravely.dev/api/v1

The page document

A page is one JSON document. The importer and the API read the same one, so what a chat AI writes and what an agent sends are the same thing.

{
  "bravely_link": 1,
  "handle": "samrivera",
  "title": "Sam Rivera",
  "bio": "Trail runner. Photos from the long way round.",
  "avatar_url": "https://example.com/sam.jpg",
  "theme": "classic-dark",
  "link_style": "classic",
  "links": [
    {
      "type": "header",
      "label": "Start here"
    },
    {
      "label": "My newsletter",
      "url": "https://example.com/news",
      "subtitle": "Every Sunday"
    },
    {
      "label": "Instagram",
      "url": "https://instagram.com/samrivera"
    }
  ]
}

The calls

Every call is at https://link.bravely.dev and answers JSON. Where a call needs a key, send it as a header: Authorization: Bearer YOUR_KEY.

Limits and errors

A field’s own limits are in the page document. Images are uploaded, never fetched: a link's image_url must be an address a media upload returned.

When a call is refused

The answer is JSON with one field, { "error": "one or more plain sentences" }. Every error names the field and the fix. When a document has several problems, the one string lists them all. A 429 carries a Retry-After header in seconds.