Developers

Biotrail API and AI connector.

Let an AI assistant or your own code read and edit a Biotrail page. Each key or connection works on one creator's own page, and only after they allow it.

Last updated 9 November 2026

Connect Claude or ChatGPT

Biotrail runs a remote MCP server at https://api.biotrail.app/mcp (Streamable HTTP). Add it as a custom connector in your AI app, sign in to Biotrail when asked and press Allow. Sign-in uses OAuth 2.1 with PKCE and dynamic client registration, so there is nothing to copy by hand.

Tools: get_page, list_item_types, get_stats, preview_link, add_link, add_item, update_item, set_item_visibility, remove_item, restore_item, reorder_items, update_profile, set_social_icons, get_design, update_design.

Apps that take a header instead of sign-in (for example Claude Code) can send a personal API key: Authorization: Bearer btk_….

API keys

Make a key in Dashboard → Integrations → API keys. A key is shown once. “Can only view” keys can use the GET routes only. Changing your password or logging out on all devices turns off every key and connected app.

curl https://api.biotrail.app/api/v1/page \
  -H "Authorization: Bearer btk_your_key"

REST routes

  • GET /api/v1/page: profile, social icons, tabs and every item in order.
  • GET /api/v1/page/block-types: the kinds of item and what their data holds.
  • GET /api/v1/page/stats?days=7|30|90: views, clicks, top items, referrers, devices.
  • GET /api/v1/page/design: the current look and every option (styles, themes, fonts, layouts, backgrounds, button styles).
  • PATCH /api/v1/page/design: { "style"?, "accent"?, "font"?, "header"?, "wallpaper"?, "buttons"?, "linkLayout"? }; only what you send changes. Photos and backgrounds are uploaded in the editor.
  • PATCH /api/v1/page/profile: { "displayName", "bio" }
  • PUT /api/v1/page/socials: { "instagram": "https://…", "x": "" } (empty removes).
  • POST /api/v1/page/items/link: { "url", "title"? }; picks the right kind of item.
  • POST /api/v1/page/items: { "type", "title", "url"?, "priceLabel"?, "data"?, "area"?, "parentId"? }
  • PATCH /api/v1/page/items/:id: only the fields you send change.
  • POST /api/v1/page/items/:id/visibility: { "visible": false }
  • DELETE /api/v1/page/items/:id: archives the item; POST …/restore brings it back.
  • PUT /api/v1/page/items/order: { "ids": [..], "area": "links" }, top first.
curl -X POST https://api.biotrail.app/api/v1/page/items/link \
  -H "Authorization: Bearer btk_your_key" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://youtu.be/dQw4w9WgXcQ"}'

Limits and rules

  • 1,200 requests per hour per key or connection.
  • The same rules as the editor apply: item limits, link checks, price formats.
  • Nothing is deleted through the API; removed items go to the archive.
  • Changes show on the public page within about a minute.
  • The API can't read email subscribers, messages, bookings or account settings.