/* Linkup docs — rebrand custom overrides * * Only the "Get Started" navbar CTA is squared off. * Everything else (including "Try It", cards, code blocks, callouts, * banner, search, nav pills) keeps Mintlify's default rounded corners. */ /* * "Get Started" — top navbar primary CTA * * docs.json -> navbar.primary -> { * type: "button", * label: "Get Started", * href: "https://app.linkup.so/sign-up" * } * * Targeted by exact href so we don't depend on Mintlify's class names. */ a[href="https://app.linkup.so/sign-up"], a[href*="app.linkup.so/sign-up"], a[href$="/sign-up"] { border-radius: 0 !important; } /* * Sidebar group headers — "Get Started", "Endpoints", "Platform", etc. * * Without this rule they share the same weight as the page links underneath * them, which collapses the visual hierarchy. Bolding them separates section * labels from individual page entries. * * `sidebar-group-header` is Mintlify's documented element selector for the * group label (https://mintlify.mintlify.dev/docs/customize/custom-scripts). * `#sidebar-content h5` is included as a backup since Mintlify currently * renders the label as an h5 inside the stable #sidebar-content scope. */ sidebar-group-header, #sidebar-content h5 { font-weight: 700 !important; } /* * Nested sidebar groups — Search, Fetch, Research, Tasks (and Account in API * Reference). When a nested group is expanded, its child links get a thin * vertical rail running down their left edge. The active link's segment of * the rail is highlighted in the brand green from docs.json. * * Inspired by Exa's docs sidebar. * * `sidebar-group` is Mintlify's documented element selector. A *nested* * group is a sidebar-group inside another sidebar-group; the descendant * combinator selects only those inner ones. We put the rail on the children * list rather than the group itself so it doesn't extend up alongside the * group's own header row. */ #sidebar-content sidebar-group sidebar-group ul, #sidebar-content sidebar-group sidebar-group ol, #sidebar-content sidebar-group sidebar-group .pages, #sidebar-content sidebar-group sidebar-group [class*="space-y"] { border-left: 1px solid rgba(124, 169, 148, 0.25); } @media (prefers-color-scheme: dark) { #sidebar-content sidebar-group sidebar-group ul, #sidebar-content sidebar-group sidebar-group ol, #sidebar-content sidebar-group sidebar-group .pages, #sidebar-content sidebar-group sidebar-group [class*="space-y"] { border-left-color: rgba(255, 255, 255, 0.12); } } #sidebar-content sidebar-group sidebar-group li[data-active] > a, #sidebar-content sidebar-group sidebar-group [data-active] { box-shadow: inset 2px 0 0 0 #7CA994; } @media (prefers-color-scheme: dark) { #sidebar-content sidebar-group sidebar-group li[data-active] > a, #sidebar-content sidebar-group sidebar-group [data-active] { box-shadow: inset 2px 0 0 0 #5A8775; } } /* * Top tab strip — "Documentation", "API Reference", "SDKs", etc. * * Mintlify ships these as ``. The default weight is * regular, which makes the tab strip read like inline links. Bolding makes * the tabs stand out as primary navigation. * * `.nav-tabs-item` is the documented class selector * (https://mintlify.mintlify.dev/docs/customize/custom-scripts). The * [role="tab"] fallback covers any tab that doesn't carry the class. */ .nav-tabs-item, nav-tabs-item, nav-tabs [role="tab"], #navbar [role="tab"] { font-weight: 500 !important; } /* * Page-header eyebrow — the section label rendered above the page title * (e.g. "Get Started" above "Introduction"). Mintlify renders this as *

* Tailwind's `font-semibold` is 600; bumping to 700 makes the label * read as bold and matches the bolded sidebar group headers above. */ .eyebrow { font-weight: 700 !important; } /* * Inline code — increase contrast in both light and dark mode. * * Mintlify's default inline-code styling has very low contrast on its * light background (visible on tokens like `/research` inside body copy). * We give inline code a subtle brand-green tint and a darker monospace * foreground in light mode, and a neutral white-tinted background with a * near-white foreground in dark mode. * * `:not(pre) > code` only targets inline `

` — code inside fenced
 * blocks (``) keeps Mintlify's syntax-highlighting styles.
 *
 * Dark mode targets `html.dark` (Mintlify's in-page theme toggle, which
 * is what users actually click) AND `prefers-color-scheme: dark` (system
 * preference fallback for users who haven't manually toggled). Without
 * the `.dark` selector, a user on a light-OS who toggles the docs to
 * dark mode would still see the light-mode rule (low-contrast green-on-
 * green chips against the dark page background).
 */
:not(pre) > code {
  background-color: rgba(16, 24, 40, 0.06) !important;    /* #101828 @ 6% */
  color: #101828 !important;
  border: 1px solid rgba(16, 24, 40, 0.10) !important;
  padding: 0.2em 0.1em !important;
  border-radius: 4px !important;
  font-size: 0.81em !important;
}

html.dark :not(pre) > code,
.dark :not(pre) > code {
  background-color: rgba(255, 255, 255, 0.08) !important;
  color: #E8F0EB !important;
  border-color: rgba(255, 255, 255, 0.12) !important;
}

@media (prefers-color-scheme: dark) {
  html:not(.light) :not(pre) > code {
    background-color: rgba(255, 255, 255, 0.08) !important;
    color: #E8F0EB !important;
    border-color: rgba(255, 255, 255, 0.12) !important;
  }
}

/*
 *  component — make the card visible.
 *
 * Mintlify's  ships with `bg-stone-50` (`#FAFAF9`) on a
 * `#F8F8F8` page background — effectively the same color, so the card
 * disappears into the page. We tint it with a brand-sage wash and a
 * darker sage border so it reads as its own surface, while leaving the
 * "Copy prompt" button alone (Mintlify's `bg-primary` is fine).
 *
 * Mintlify's internal class names are unstable, so we scope these
 * overrides to a `.linkup-prompt` wrapper we control in MDX:
 *
 *   
 *     ...
 *   
 */
.linkup-prompt {
  border-radius: 10px;
}

/*
 * Tint the card itself.
 *
 * Mintlify's `` ships with `bg-stone-50` (`#FAFAF9`) on a
 * `#F8F8F8` page background — they're effectively the same color, so
 * the card has no visible edge. Apply a subtle brand-sage wash and a
 * stronger sage border so the card reads as its own surface against
 * the page. Dark mode gets the same treatment on top of `bg-stone-900`.
 *
 * `.linkup-prompt > .prompt` matches Mintlify's inner card class. We
 * leave `.prompt` selectors here scoped under `.linkup-prompt` so this
 * never leaks to other `` instances we might add later.
 */
.linkup-prompt > .prompt {
  background-color: rgba(124, 169, 148, 0.10) !important;
  border-color: rgba(124, 169, 148, 0.40) !important;
}

html.dark .linkup-prompt > .prompt,
.dark .linkup-prompt > .prompt {
  background-color: rgba(124, 169, 148, 0.12) !important;
  border-color: rgba(124, 169, 148, 0.35) !important;
}

@media (prefers-color-scheme: dark) {
  html:not(.light) .linkup-prompt > .prompt {
    background-color: rgba(124, 169, 148, 0.12) !important;
    border-color: rgba(124, 169, 148, 0.35) !important;
  }
}

.linkup-prompt p,
.linkup-prompt > div > div > :is(p, span, div) {
  color: #101828 !important;
}

html.dark .linkup-prompt p,
html.dark .linkup-prompt > div > div > :is(p, span, div),
.dark .linkup-prompt p,
.dark .linkup-prompt > div > div > :is(p, span, div) {
  color: #E8F0EB !important;
}

@media (prefers-color-scheme: dark) {
  html:not(.light) .linkup-prompt p,
  html:not(.light) .linkup-prompt > div > div > :is(p, span, div) {
    color: #E8F0EB !important;
  }
}

/*
 * Hide the inline "Ask a question..." floating AI input.
 *
 * Mintlify renders an additional floating chat input on every docs page
 * (a centered, rounded textarea with the placeholder "Ask a question..."
 * and a Cmd+I shortcut + send button). It duplicates functionality we
 * already expose via the navbar Ask AI entry point, so we hide just the
 * floating variant and leave the rest of the assistant intact.
 *
 * `chat-assistant-floating-input` is Mintlify's documented element
 * selector for that floating input
 * (https://mintlify.mintlify.dev/docs/customize/custom-scripts).
 *
 * Intentionally left untouched:
 *   - `#assistant-entry` / `#assistant-entry-mobile` — top navbar Ask AI
 *     button (kept; this is our primary entry point).
 *   - `#chat-assistant-sheet` / `chat-assistant-input` — the assistant
 *     chat panel and the textarea inside it (kept; opens from the navbar).
 *   - `#search-bar-entry` — top navbar search trigger (kept).
 *
 * If Mintlify renames or restructures the floating input element, this
 * rule may stop matching and the input could reappear; revisit if so.
 */
chat-assistant-floating-input {
  display: none !important;
}

/*
 * Browser-synthesized bold for body copy.
 *
 * `docs.json -> fonts` only loads the Regular (400) `.woff2` of Season Sans
 * and Season Mix. Without a Bold weight file, `**...**` MDX (rendered as
 * /) has nothing to fall back to and the browser keeps the
 * Regular glyphs — bold text is visually indistinguishable from body copy.
 *
 * `font-synthesis: weight` tells the browser it's allowed to fake a bold
 * weight from the loaded Regular file. Modern browsers (Safari/Chrome/
 * Firefox/Edge) all support this. It's a stopgap — a real Bold `.woff2`
 * registered in `docs.json -> fonts` would look noticeably crisper — but
 * it restores the visual weight contrast that Markdown bold relies on.
 *
 * Scoped to / and the Tailwind weight utilities Mintlify uses
 * for headings, table headers, and emphasized inline copy so the rule
 * doesn't accidentally synthesize bold on text that already has a real
 * bold font loaded (e.g. inline `` in pre blocks).
 */
strong,
b,
th,
.font-bold,
.font-semibold,
.font-medium {
  font-synthesis: weight style !important;
  -webkit-font-synthesis: weight style !important;
}

Get Started

Endpoints

Platform

Guides

Tutorials

FAQ

Documentation Index