# Intros Public API — Full Reference > Programmatic access to Bridge introductions, contacts, and CC inbox threads on intros.brdg.app for scripts and agents. > Human-readable docs: [/developers/api](/developers/api) > OpenAPI: [/api/v1/openapi.yaml](/api/v1/openapi.yaml) > Short agent summary: [/llms.txt](/llms.txt) --- # Intros Developer API Programmatic access to **Bridge introductions**, **contacts**, and **read-only CC inbox** data on `intros.brdg.app`. Use a **Bridge API key** (same key as other Bridge apps such as Raise). **Base URL (this app):** `https://intros.brdg.app/api/v1` **LLM-friendly mirrors:** [/llms.txt](/llms.txt) (short) · [/llms-full.txt](/llms-full.txt) **OpenAPI 3.1:** [/api/v1/openapi.yaml](/api/v1/openapi.yaml) Every endpoint: - Authenticates with a Bridge API key as `Authorization: Bearer …`. - Returns either `{ "item": ... }` (single resource) or `{ "items": [...], "next_cursor": "...|null" }` (collection). - Returns errors as `{ "error": { "code": "...", "message": "..." } }`. - Sends and receives JSON. --- ## Auth Every request must send a Bearer token. Preflight `OPTIONS` requests are short-circuited and do not require auth. ``` Authorization: Bearer ``` - Generate or revoke keys in [brdg.app](https://brdg.app) account settings. - The API acts as the user who owns the key — permissions match the Intros web UI. - `GET /v1/me` is a lightweight call to verify a key. --- ## MCP (AI apps) Connect Grok, Claude, ChatGPT, Cursor, or similar tools to Intros over [Model Context Protocol](https://modelcontextprotocol.io/). **MCP server URL:** `https://intros.brdg.app/mcp` ### Auth 1. **OAuth (recommended)** — Paste the MCP URL into your AI app. You approve on `https://intros.brdg.app/connect`. Scopes: `intros:read` (default) and optional `intros:write`. Manage or revoke connections in **Inbox → Settings → AI apps**. 2. **Bridge API key** — Send `Authorization: Bearer ` on MCP requests (no OAuth). The key gets full read + write tool access. ### Tools (v2) | Scope | Tools | |-------|--------| | `intros:read` | `get_me`, `list_todo_intros`, `search_intros`, `get_intro`, `get_intro_counts`, `search_contacts`, `get_contact`, `list_inbox_threads`, `get_inbox_thread`, `get_intros_guide`, `report_issue` | | `intros:write` (sends email) | `make_intro`, `make_cc_intro`, `forward_intro`, `forward_intros_with_template`, `publish_cc_intro`, `resend_intro_email`, `request_changes_intro` | | `intros:write` (lifecycle) | `confirm_intro`, `accept_intro`, `decline_intro`, `rate_intro` | | `intros:write` (records, no email) | `log_historical_intro` | | `intros:write` (contacts) | `create_contact`, `update_contact` | - Start with `list_todo_intros`. Each intro carries `todo_reason`, `next_actor` and `available_actions`. - `search_intros` filters by person (`query`), `status`, `my_role`, `flow`, `category` and dates, and returns compact summaries unless `detail: "full"`. - Every tool that sends email takes `dry_run: true`, which returns the sender, recipients, subject and body without sending (`forward_intro` shows your note; Bridge builds the final email around it), and `from_account_id` (from `get_me.send_accounts`; defaults to your primary mailbox). - Agents never pass magic-link tokens. Lifecycle tools resolve the right token from your role. - `log_historical_intro` records an intro that happened outside Bridge: before you joined, offline, or over another channel such as email, calendar, WhatsApp or chat. Use it when an intro is missing, or to record how you know someone. It's saved as completed, and the existing intro is returned if there is one. Logged intros can't be edited. - `get_intros_guide` returns the [Concepts](#concepts) tables below. v2 replaced `list_intros`, `list_contacts`, `create_intro` and `cancel_intro` with `search_intros`, `search_contacts`, `make_intro` / `make_cc_intro` and `decline_intro`. Claude Code one-liner: ```bash claude mcp add --transport http intros https://intros.brdg.app/mcp ``` --- ## Concepts Roles, statuses, flows, tokens and count buckets shared by the REST API and the MCP tools. Generated from `supabase/functions/mcp/lib/glossary.ts`; edit it there. _(inferred)_ marks definitions read from app behaviour and not yet confirmed by the Bridge backend. ### What Bridge does on its own (read before following up) Bridge sends these emails itself. Don't send your own versions. `get_intro` with `detail: "full"` shows what's scheduled for an intro in `upcoming_jobs`. Times are Bridge's defaults and skip weekends and holidays, so treat them as approximate. - **Opt-in reminder:** about 5 days after an intro is offered, the requester gets the opt-in email again if they haven't answered. Sent once. - **Forward reminder:** about 1 day after the requester opts in, the connector is reminded to forward it. - **Target reminder:** about 5 days after the intro is forwarded, the target gets it again if they haven't answered. Sent once. - **No reply from the target:** on opt-in intros, about 10 days later the status becomes `no_response_from_n2` and the requester is told. - **When the target accepts:** one email goes to the requester and target together, from the connector's mailbox (or from Bridge on their behalf), in a new thread. The default subject is "Requester (Org) <> Target (Org)" and it opens "A, meet B! B, meet A!". The connector gets a note that feedback will be asked for in 2 weeks. - **Feedback request:** 14 days after acceptance, the requester and target are each asked how the intro went (Great, Okay, Not good, Not connected yet), with one reminder 14 days later. Their answer and comment go to the connector. - **Turning them off:** reminders and feedback requests are on by default. The connector can turn them off for an intro in Intros (`from_reminders_enabled`, `to_reminders_enabled`, `from_feedback_enabled`, `to_feedback_enabled`). ### After an intro is accepted - The accept email has already connected them, and Bridge will ask for feedback. A follow-up from the requester or target (`send_follow_up_email`) is optional, for sharing a calendar link or next step. It goes as a reply to the accept email, so it threads with it. Ask the user before sending one. - **Avoid duplicate follow-ups.** Bridge doesn't store emails the user sent from their own mail, or follow-ups sent with `send_follow_up_email`, on the intro, and replies to Bridge's emails don't reach it. So `get_intro` won't show them. Intros does remember follow-ups sent from Intros (web or MCP) and refuses a second. If you can read the user's email, check there for a reply or follow-up first. - **Record what happened.** The requester and target answer the feedback request with `rate_intro`. Anyone on the intro can log what it led to with `record_intro_outcome`: an estimated value in USD and a short note, such as "Led to a $250K seed investment". - **Status can't be set directly.** Only the target can accept. The connector can cancel with `decline_intro`. - **Category.** Bridge's AI guesses each opt-in intro's category (fundraising, sales, recruitment, other) from the requester's reason. If it's missing or wrong and you're confident, set it with `set_intro_category`; a category set by hand is kept. ### Roles | Role | `my_role` | Fields | Meaning | |------|-----------|--------|---------| | requester | `n1` | from, from_email, from_contact_id | The person being introduced. Opts in, can update or withdraw, rates the intro. | | target | `n2` | to, to_email, to_contact_id | The person the requester wants to meet. Accepts or declines the forwarded intro. | | connector | `broker` | broker, broker_email, broker_contact_id | Makes, reviews and forwards the intro (also called broker or owner). Usually the Intros user. | ### Statuses | Status | Meaning | Next actor | Terminal | Tools | |--------|---------|------------|----------|-------| | `initialized` | Created, waiting on the first opt-in. If the connector offered it, the requester must opt in. If the requester asked through an intro link (flow opt_in_via_intro_link), the connector reviews it. | depends | no | `confirm_intro`, `resend_intro_email`, `decline_intro` | | `confirmed` | Requester opted in. Waiting for the connector to forward it to the target. | connector | no | `forward_intro`, `forward_intros_with_template`, `publish_cc_intro`, `request_changes_intro`, `decline_intro` | | `changes_requested` | Connector asked the requester to update their details. Waiting for the requester. | requester | no | `confirm_intro`, `decline_intro`, `forward_intro` | | `published` | Forwarded to the target. Waiting for the target to accept or decline. | target | no | `accept_intro`, `decline_intro`, `resend_intro_email` | | `pending_auto_forward` | Forward is scheduled automatically and can no longer be canceled. The target can accept or decline once it becomes published. _(inferred)_ | target | no | — | | `no_response_from_n2` | Target has not replied after reminders. Not terminal: the target can still accept, the connector can resend or cancel. | target | no | `accept_intro`, `decline_intro`, `resend_intro_email` | | `delayed` | Paused. The web app only colours it as delayed; the backend meaning is not documented. _(unknown)_ | none | no | — | | `accepted` | Target accepted; both sides are connected. Success. If feedback_requested, the requester and target can rate it. | none | yes | `send_follow_up_email`, `rate_intro`, `record_intro_outcome` | | `rejected` | Target declined. | none | yes | — | | `canceled` | Requester declined or withdrew. | none | yes | — | | `canceled_by_owner` | Connector canceled an intro they offered. | none | yes | — | | `declined_by_owner` | Connector declined a requested intro (shown as canceled for single_opt_in). | none | yes | — | | `pending_auto_decline` | Decline email is queued. Treat as declined. _(inferred)_ | none | no | — | ### Flows `flow` on an intro is the Bridge flow below. | Flow | Label | Meaning | Create with | Emails on create | |------|-------|---------|-------------|------------------| | `opt_in` | Forwardable | Double opt-in (best practice). Requester opts in, connector forwards, target accepts. | `make_intro` | Emails the requester asking them to opt in. The target hears nothing until forward_intro. | | `single_opt_in` | Single opt-in | Requester's opt-in is skipped; only the target is asked. | `make_intro` | Emails the target asking whether they want the intro. _(inferred)_ | | `fast` | Fast intro | No opt-in. Introduces both people directly. | `make_intro` | Emails the requester and target together, plus any CC contacts. _(inferred)_ | | `cc` | CC intro | Intro made over email with intros@cc.brdg.app CC'd, or created as a CC intro. | `make_cc_intro` | With send_now, emails send_to (all, requester or target). Without it, creates the record only; send later with publish_cc_intro. | | `opt_in_via_intro_link` | Forwardable | Requester asked through the connector's public intro link. The connector reviews it. | no | Not created through the API. | | `manual` | Manual | Historical or manually recorded intro. No emails, no ratings. | no | Not created through the API. _(inferred)_ | ### To-do reasons `list_todo_intros` returns intros waiting on you, each with a `todo_reason`. | Reason | Your role | Meaning | Usual tool | |--------|-----------|---------|------------| | `forward` | connector | Confirmed intro waiting for you to forward. | `forward_intro` | | `review_request` | connector | Someone asked for an intro through your intro link. | `get_intro` | | `review_cc_thread` | connector | A CC'd email thread linked to the intro needs review. | `get_inbox_thread` | | `opt_in` | requester | An intro was offered to you; opt in or decline. | `confirm_intro` | | `update_requested` | requester | The connector asked you to update your details. | `confirm_intro` | | `accept_or_decline` | target | An intro was forwarded to you. | `accept_intro` | | `give_feedback` | requester | Accepted intro with feedback requested and no rating from you yet (also as target). | `rate_intro` | ### Sending and tokens - Send tools email real people from your mailbox. Each takes `dry_run: true`, which returns `sent: false` and the sender, recipients, subject and body without sending. `forward_intro` returns your note with `body_is_final: false`, because Bridge builds the final email around it. - Lifecycle tools also take `dry_run: true`, which returns what would happen and who would be notified. `decline_intro` as connector needs an explicit `notify`. - A repeat send for the same intro within 10 minutes is refused unless `allow_resend: true`. - Ratings: `great`, `okay`, `not_good`, `no_feedback`. - `since` / `updated_since` filter by last update, not creation. Bridge pages start at 0. | Name | What it is | Belongs to | Agent passes it | |------|------------|------------|-----------------| | `initialized_token` | Magic-link token for the requester's actions (opt in, withdraw, rate). | Requester | no | | `published_token` | Magic-link token for the target's actions (accept, decline, rate). | Target | no | | `from_account_id` | Not an auth token: the id of a connected mailbox to send from (Bridge token_id). List them with get_me.send_accounts. Omit to use the primary mailbox. | Whoever sends | yes | ### Count buckets Bridge computes these buckets server-side; definitions marked inferred are not yet confirmed. `get_intro_counts` also returns counts computed from the same data as `list_todo_intros`, which always agree with it. | Bucket | Meaning | Confidence | |--------|---------|------------| | `all` | Every intro you can see. | confirmed | | `active` | Open intros created recently (the complement of archived). | inferred | | `confirm` | Waiting on your action, as the backend counts it. Not guaranteed to equal list_todo_intros. | inferred | | `noreply` | Waiting on someone else: initialized, published, no_response_from_n2 or changes_requested. | inferred | | `completed` | Accepted intros that are not network asks. | inferred | | `archived` | Open, not an ask, created more than 28 days ago. | inferred | | `received` | Intros you received (as target, or requests to you as connector). | unknown | | `canceled_by_owner` | Status canceled_by_owner. | inferred | | `declined` | Declined by anyone: canceled, rejected, declined_by_owner, canceled_by_owner. | inferred | | `declined_by_me` | Declined by you in your role: connector → *_by_owner, requester → canceled, target → rejected. | inferred | | `rated` | Accepted intros with feedback received. | inferred | | `received_as_connector_via_introlink` | Requests sent to you through your intro link (flow opt_in_via_intro_link). | inferred | | `ask_all` | Intros tied to your asks (network_ask_id set). | inferred | | `ask_confirm` | Your asks waiting on you. | inferred | | `ask_declined` | Your asks that were declined. | inferred | | `network_ask_all` | Asks coming from your network or org. | inferred | | `network_ask_confirm` | Asks from your network waiting on you. | inferred | | `network_ask_declined` | Asks from your network that were declined. | inferred | ### Tools **Read** - `get_me`: You, your email addresses and send_accounts (mailboxes you can send from). - `list_todo_intros`: Intros waiting on you, each with a todo reason. Start here. - `search_intros`: Filter by query (name, email, company), status, my_role, flow, category, dates. Compact by default. - `get_intro`: One intro with next actions. include_messages adds email bodies. - `get_intro_counts`: Counts computed from your intros, plus Bridge's raw buckets. - `search_contacts`: Fuzzy search on name, email and company, or exact email lookup. - `get_contact`: One contact by id. - `list_inbox_threads / get_inbox_thread`: Read-only CC inbox threads. - `get_intros_guide`: This guide, by topic. - `report_issue`: Tell the Intros team a tool did something unexpected. **Send (real email; all take dry_run and from_account_id)** - `make_intro`: Create an opt_in, single_opt_in or fast intro between two contacts. - `make_cc_intro`: Create a CC intro; send_now emails send_to, otherwise record only. - `forward_intro`: Connector forwards a confirmed intro to the target. - `forward_intros_with_template`: Bulk-forward confirmed intros with your saved template. - `publish_cc_intro`: Send the email for a CC intro. - `resend_intro_email`: Resend the pending email: opt-in to the requester, or forward to the target. - `request_changes_intro`: Ask the requester to update their details (emails them). - `send_follow_up_email`: After an accepted intro, email the other person your follow-up (your saved template, usually with your calendar link). Check they haven't already been followed up first. - `record_intro_outcome`: Log what an accepted intro led to: an estimated USD value and a short note. - `set_intro_category`: Set an intro's category (fundraising, sales, recruitment, other) when Bridge's guess is missing or wrong. - `update_follow_up_template`: Change the follow-up template, e.g. to put in a real calendar link. **Lifecycle (tokens are resolved for you; all take dry_run)** - `confirm_intro`: Requester opts in, or submits updated details after changes_requested. - `accept_intro`: Target accepts. - `decline_intro`: Decline in your role: target rejects, requester withdraws, connector cancels. Connectors must pass notify, which controls the decline email. - `rate_intro`: Rate an accepted intro: great, okay, not_good or no_feedback. **Record (no email)** - `log_historical_intro`: Record an intro that happened outside Bridge as completed; returns the existing one if already logged. **Contacts** - `create_contact`: Create a contact (returns the existing one if the email is known). - `update_contact`: Update a contact. ### Deep links To have the user make the intro themselves, in their browser, open: `https://intros.brdg.app/inbox?makeIntro=1&n1=&n1_name=&flow=opt_in` Make intro opens with that person as N1 (the requester); the user picks who to introduce them to, reviews and sends. No API key: it uses the user's signed-in session. URL-encode values and leave out empty ones. | Param | Meaning | |-------|---------| | `makeIntro` | `1`. Required. | | `n1` | Email. Selects them directly; creates the contact if new. | | `n1_name` | Full name. Without `n1`, the user's contacts are searched for it and the user picks. | | `n1_title`, `n1_company`, `n1_linkedin` | Saved on the contact only where it has no value yet; never overwrites. `n1_linkedin` must be a `linkedin.com/in/…` URL. | | `n2`, `n2_name`, `n2_title`, `n2_company`, `n2_linkedin` | Same, for the target. Usually left out so the user picks. | | `flow` | `opt_in` (forwardable, default), `single_opt_in` or `fast`. | Use `make_intro` to send it yourself; use a deep link when the user should choose N2 or review in Intros. --- ## Base URL ``` https://intros.brdg.app/api/v1 ``` All paths below are relative to this base URL. --- ## Errors Every error returns a JSON envelope with stable error codes: ```json { "error": { "code": "forbidden", "message": "Access denied." } } ``` | HTTP | `error.code` | Typical cause | |------|-------------------|---------------| | 400 | `invalid_request` | Bad JSON, missing fields, bad query value, or Bridge rejected the input | | 400 | `invalid_domain` | Reserved for future domain helpers | | 401 | `unauthorized` | Missing, malformed, or invalid API key | | 403 | `forbidden` | Valid key but not allowed on resource | | 404 | `not_found` | Unknown route or missing resource | | 429 | `rate_limited` | Too many requests; wait and retry | | 500 | `internal_error` | Unhandled server-side failure | | 502 | `internal_error` | The upstream Bridge API failed | Errors from the upstream Bridge API are translated into the closest of these codes. --- ## GET /v1/me Returns the authenticated Bridge user. Useful for verifying an API key. *Wraps `GET https://api.brdg.app/api/v4/users/me`.* **Example request** ```bash curl "https://intros.brdg.app/api/v1/me" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response** ```json { "item": { "id": "uuid", "email": "you@example.com", "first_name": "Alex", "last_name": "Founder", "name": "Alex Founder" } } ``` **Possible errors** - `401 unauthorized` — missing, malformed, or invalid API key. --- ## GET /v1/intros Search and filter the authenticated user's introductions. Returns compact summaries by default. *Wraps `GET https://api.brdg.app/api/v4/introductions/since/:since`, fetching every page and filtering on this server. `since` and `created_after` narrow what's fetched, so searches using them are much faster on large accounts.* **Query parameters** | Name | Type | Required | Description | |------|------|----------|-------------| | `q` | string | no | Matches requester, target or connector name, email or company (case-insensitive). | | `status` | comma-separated list | no | One or more [statuses](#concepts), e.g. `confirmed,published`. | | `my_role` | `requester` \| `connector` \| `target` | no | Your role in the intro. | | `flow` | comma-separated list | no | One or more [flows](#concepts). | | `category` | comma-separated list | no | `fundraising`, `sales`, `recruitment`, `other`. | | `needs_my_action` | boolean | no | Only intros waiting on you, including feedback to give. Unlike MCP `list_todo_intros`, CC-thread review items are not included. | | `created_after` / `created_before` | ISO-8601 | no | Creation date bounds. | | `since` | number or ISO-8601 | no | Unix **seconds** or ISO timestamp. Filters by **last update**, not creation. Defaults to `0`. | | `limit` | integer 1–200 | no | Defaults to `25`. | | `offset` | integer ≥ 0 | no | Defaults to `0`. | | `detail` | `summary` \| `full` | no | `full` returns Bridge attributes (minus magic-link tokens). Defaults to `summary`. | | `page` | integer ≥ 0 | no | Bridge page, 0-indexed. Only for raw sync; skips server-side filtering. | | `data_version` | string | no | Forwards `Data-Version` header to Bridge. Defaults to `7` (matches the Intros web client). | **Example request** ```bash curl "https://intros.brdg.app/api/v1/intros?q=susie&status=confirmed&my_role=connector" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response** ```json { "items": [ { "id": "intro-uuid", "status": "confirmed", "status_meaning": "Requester opted in. Waiting for the connector to forward it to the target.", "flow": "opt_in", "my_role": "connector", "category": "fundraising", "subject": "Intro: Alex <> Susie", "requester": { "name": "Alex Founder", "email": "alex@example.com", "company": "Acme" }, "target": { "name": "Susie Investor", "email": "susie@example.com", "company": "Fund" }, "connector": { "name": "You", "email": "you@example.com" }, "reason": "Raising a seed round…", "from_contact_note": "Met at YC demo day", "todo_reason": "forward", "created_at": "2026-04-23T18:20:00Z", "updated_at": "2026-04-24T09:00:00Z" } ], "total_matched": 1, "next_offset": null, "truncated": false, "meta": { "last_update": 1710000000, "data_version": "7" } } ``` `reason` is the requester's note; `from_contact_note` is the connector's note. `meta.last_update` is Bridge's `Last-Update` response header (use as the next `since`). `truncated` is `true` when the feed was too large to read in full. **Possible errors** - `400 invalid_request` — `since` is not a number or valid ISO timestamp. - `401 unauthorized`. --- ## POST /v1/intros Create an introduction. Branch with the `flow` discriminator. ### `flow: "request"` (standard make-intro) *Wraps `POST https://api.brdg.app/api/v4/introductions`.* **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `flow` | `"request"` | yes | Discriminator. | | `from_id` | string | yes | Contact `ref_id` for the requester (N1). | | `to_id` | string | yes | Contact `ref_id` for the target (N2). | | `intro_flow` | `"opt_in"` \| `"single_opt_in"` \| `"fast"` | yes | Bridge intro flow (sent as `flow` to Bridge). See [flows](#concepts) for who gets emailed. | | `subject` | string | yes | Email subject. | | `message` | string | yes | Email body. | | `token_id` | string \| null | no | Id of the connected mailbox to send from (`tokens[].id` on the Bridge user). Not an auth token. | | `dry_run` | boolean | no | Return `{ "would_send": … }` without creating the intro or sending email. | | `from_contact_note` | string \| null | no | Note saved on the from contact. | | `to_contact_note` | string \| null | no | Note saved on the to contact. | | `cc_contact_ids` | string[] | no | Additional contact ref ids to CC. | | `source_id` | string \| null | no | Source attribution id. | | `network_ask_id` | string \| null | no | Network ask id this intro answers. | | `from` | string | no | Display name override for the requester. | | `from_email` | string | no | Display email override for the requester. | | `to` | string | no | Display name override for the target. | | `to_email` | string | no | Display email override for the target. | | `note` | string \| null | no | Free-form note. | | `linkedin_profile_url` | string \| null | no | LinkedIn URL hint. | ### `flow: "cc"` (CC intro) *Wraps `POST https://api.brdg.app/api/v4/introductions/cc`.* **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `flow` | `"cc"` | yes | Discriminator. | | `from_contact_id` | string | yes | Contact id for the requester. | | `to_contact_id` | string | yes | Contact id for the target. | | `subject` | string \| null | no | Email subject (when sending). | | `message` | string \| null | no | Email body (when sending). | | `source_id` | string \| null | no | Source attribution id. | | `token_id` | string \| null | no | Sending email token id. | | `send_initial_email` | boolean | no | If `false`, creates the intro record without sending email. | | `send_to` | `"requester"` \| `"target"` \| `"all"` \| null | no | Recipient scope. | | `status` | string \| null | no | Override initial Bridge status. | **Example request (`request` flow)** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "flow": "request", "from_id": "contact-ref-id-1", "to_id": "contact-ref-id-2", "intro_flow": "opt_in", "subject": "Intro: Alex <> Susie", "message": "Hi Susie, would love to connect you with Alex…" }' ``` **Example request (`cc` flow)** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "flow": "cc", "from_contact_id": "contact-uuid-1", "to_contact_id": "contact-uuid-2", "send_initial_email": false }' ``` **200 response** ```json { "item": { "intro": { "id": "intro-uuid", "type": "introduction", "attributes": { "status": "initialized" } }, "email_response": null, "message": "OK" } } ``` **Possible errors** - `400 invalid_request` — body fails schema validation. - `401 unauthorized`. - `403 forbidden` — caller cannot create intros for this `from_id` / `from_contact_id`. --- ## GET /v1/intros/counts Pipeline counts for the authenticated user (all, todo, completed, etc). Bridge computes these buckets; see [count buckets](#concepts) for what each one means and which are confirmed. *Wraps `GET https://api.brdg.app/api/v4/counts/intros`.* **Example request** ```bash curl "https://intros.brdg.app/api/v1/intros/counts" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response** ```json { "item": { "all": 42, "active": 5, "confirm": 1, "completed": 31, "archived": 5, "received": 0, "canceled_by_owner": 0, "declined": 0, "declined_by_me": 0, "rated": 12, "received_as_connector_via_introlink": 0, "ask_all": 0, "ask_confirm": 0, "ask_declined": 0, "network_ask_all": 0, "network_ask_confirm": 0, "network_ask_declined": 0 } } ``` **Possible errors** - `401 unauthorized`. --- ## GET /v1/intros/:introId Fetch a single introduction with its messages. *Wraps `GET https://api.brdg.app/api/v4/introductions/:id`. `included` messages from the JSON:API response are merged onto `item`.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `introId` | UUID | The intro id. | **Example request** ```bash curl "https://intros.brdg.app/api/v1/intros/$INTRO_ID" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response** ```json { "item": { "id": "intro-uuid", "type": "introduction", "attributes": { "status": "published", "flow": "opt_in", "subject": "Intro: Alex <> Susie", "from": "Alex Founder", "to": "Susie Investor" }, "included": [ { "id": "msg-1", "type": "introduction_message", "attributes": { "sent_at": "2026-04-23T18:30:00Z", "subject": "Intro: Alex <> Susie", "content": "Hi Susie…" } } ] } } ``` **Possible errors** - `401 unauthorized`. - `403 forbidden`. - `404 not_found`. --- ## POST /v1/intros/:introId/accept Target accepts an intro. *Wraps `POST https://api.brdg.app/api/v4/introductions/:id/acceptions`.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `introId` | UUID | The intro id. | **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `token` | string | yes | Bridge `published_token` (or N2 acceptance token). | | `email` | string | no | Email override when the target opts to accept from a different address. | **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros/$INTRO_ID/accept" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "token": "" }' ``` **200 response** ```json { "item": { "intro": { "id": "intro-uuid", "attributes": { "status": "accepted" } }, "message": "Accepted." } } ``` **Possible errors** - `400 invalid_request` — missing `token`. - `401 unauthorized`. - `403 forbidden` — token does not authorize this action. - `404 not_found`. --- ## POST /v1/intros/:introId/decline Target declines/rejects an intro. *Wraps `POST https://api.brdg.app/api/v4/introductions/:id/rejections`.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `introId` | UUID | The intro id. | **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `token` | string | yes | Bridge `published_token`. | | `cancelation_reason` | string | no | Short reason code. | | `cancelation_message` | string | no | Optional message back to connector. | **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros/$INTRO_ID/decline" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "token": "", "cancelation_reason": "not_interested", "cancelation_message": "Thanks but not a fit right now." }' ``` **200 response** ```json { "item": { "intro": { "id": "intro-uuid", "attributes": { "status": "rejected" } }, "message": "Declined." } } ``` **Possible errors** - `400 invalid_request` — missing `token`. - `401 unauthorized`. - `403 forbidden`. - `404 not_found`. --- ## POST /v1/intros/:introId/forward Forward a confirmed intro to the target. You must be the connector, and the intro must be `confirmed` or `changes_requested`. **Sends one email** to the target (or `to_email`) from the mailbox `token_id` (default: your primary mailbox). `intros@cc.brdg.app` is always CC'd so replies thread back into Intros, plus any `cc` / `bcc` you add. *Wraps `POST https://api.brdg.app/api/v4/introductions/:id/publishings`. A body that fails validation returns `400`; it never falls back to a template forward. To forward with your saved template, use [`POST /v1/intros/forward_with_template`](#post-v1introsforward_with_template).* **Path parameters** | Name | Type | Description | |------|------|-------------| | `introId` | UUID | The intro id. | **Request body** (all optional) | Field | Type | Description | |-------|------|-------------| | `to_email` | string (email) | Recipient. Default: the intro's target. | | `subject` | string | Default: `Intro to {requester} ({company})`. | | `note` | string | Your message to the target. Default: `Hi {target}, would you be interested in an intro to {requester}?` | | `token_id` | string \| null | Mailbox to send from. Default: your primary mailbox. | | `from_contact_note` | string \| null | Internal note about the requester. | | `cc` | string[] | Extra CC emails (`intros@cc.brdg.app` is always included). | | `bcc` | string[] | BCC emails. | | `dry_run` | boolean | Return `{ "would_send": … }` without sending. | **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros/$INTRO_ID/forward" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "note": "Susie, meet Alex…", "dry_run": true }' ``` **Dry-run response** ```json { "item": { "would_send": { "endpoint": "POST /api/v4/introductions/intro-uuid/publishings", "from": "you@example.com", "to": "Susie Kilcoyne ", "cc": ["intros@cc.brdg.app"], "bcc": [], "subject": "Intro to Alex Morgan (Acme)", "note": "Susie, meet Alex…" } } } ``` **200 response** ```json { "item": { "intro": { "id": "intro-uuid", "attributes": { "status": "published" } }, "message": "Forwarded." } } ``` **Possible errors** (nothing is sent) - `400 invalid_request`: malformed field, or the intro isn't `confirmed` / `changes_requested`. - `401 unauthorized`. - `403 forbidden`: you aren't the connector on this intro. - `404 not_found`. --- ## POST /v1/intros/forward_with_template Bulk-forward confirmed intros using your saved forward template. **Sends one email per intro** to each target. Bridge renders the template and picks the sender, so the final text is not known in advance; `dry_run` returns the recipients only. *Wraps `POST https://api.brdg.app/api/v4/introductions/bulk_forward`.* **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `intro_ids` | string[] (1–25) | yes | Confirmed intros where you are the connector. | | `dry_run` | boolean | no | Return `{ "would_send": … }` without sending. | **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros/forward_with_template" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "intro_ids": ["intro-uuid-1", "intro-uuid-2"] }' ``` **Possible errors** - `400 invalid_request` — missing or empty `intro_ids`, or more than 25. - `401 unauthorized`. - `403 forbidden`. --- ## POST /v1/intros/:introId/cancel Connector cancels their own intro. *Wraps `POST https://api.brdg.app/api/v4/introductions/:id/cancel_by_owner`.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `introId` | UUID | The intro id. | **Request body** (all optional) | Field | Type | Required | Description | |-------|------|----------|-------------| | `token` | string | no | Bridge cancel token if available. | | `cancelation_reason` | string \| null | no | Short reason code. | | `cancelation_message` | string \| null | no | Optional message. | **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros/$INTRO_ID/cancel" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "cancelation_reason": "no_longer_relevant" }' ``` **200 response** ```json { "item": { "intro": { "id": "intro-uuid", "attributes": { "status": "canceled_by_owner" } }, "message": "Canceled." } } ``` **Possible errors** - `401 unauthorized`. - `403 forbidden`. - `404 not_found`. --- ## POST /v1/intros/:introId/request-changes Connector asks the requester to update their intro reason or info. *Wraps `POST https://api.brdg.app/api/v4/introductions/:id/request_changes`.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `introId` | UUID | The intro id. | **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `message` | string | yes | Message shown to the requester. | | `token_id` | string \| null | no | Sending email token id. | **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros/$INTRO_ID/request-changes" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "message": "Could you tighten the ask and add a one-liner?" }' ``` **200 response** ```json { "item": { "intro": { "id": "intro-uuid", "attributes": { "status": "changes_requested" } }, "message": "Changes requested." } } ``` **Possible errors** - `400 invalid_request` — missing `message`. - `401 unauthorized`. - `403 forbidden`. - `404 not_found`. --- ## POST /v1/intros/:introId/publish Publish a CC intro: connector sends the intro email to the target. *Wraps `POST https://api.brdg.app/api/v4/introductions/cc/:id/publish`. Only applies to CC-flow intros.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `introId` | UUID | The CC intro id. | **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `content` | string | yes | Plain text email body. | | `subject` | string | yes | Email subject. | | `token_id` | string \| null | no | Sending email token id. | | `cc` | string[] | no | Additional CC emails. | | `bcc` | string[] | no | Additional BCC emails. | **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros/$INTRO_ID/publish" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "content": "Susie, meet Alex…", "subject": "Intro: Alex <> Susie" }' ``` **200 response** ```json { "item": { "intro": { "id": "intro-uuid", "attributes": { "status": "published" } }, "email_response": { "thread_id": "thread-uuid" }, "message": "Published." } } ``` **Possible errors** - `400 invalid_request` — missing `content` or `subject`. - `401 unauthorized`. - `403 forbidden` — intro is not a CC intro or caller is not the owner. - `404 not_found`. --- ## POST /v1/intros/historical Log an intro that happened outside Bridge: before you joined, offline, or over another channel. It is saved as completed and no email is sent. Logged intros can't be edited. Use it for intros you received (you are the requester or target) or made (you are the connector). MCP: `log_historical_intro`. *Wraps `POST https://api.brdg.app/api/v4/introductions/historical`.* Give each person as a contact id or an email. When only an email is given, the contact is looked up and created if missing. If an intro with the same connector and the same two other people (in either order) already exists, it is returned with `duplicate: true` and nothing new is created. `duplicate_check` is `"full"` when every intro was checked, or `"partial"` when not every intro could be compared, in which case a duplicate of an older intro is possible. Canceled or declined intros do not count as already logged. **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `requester` | party | yes | Who was introduced: asked for or received the intro. | | `target` | party | yes | Who they were introduced to. | | `connector` | party | yes | Who made the intro. | Each party is an object with `contact_id` or `email` (one is required) and an optional `name`, used when a contact is created. **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/intros/historical" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "requester": { "email": "you@example.com" }, "target": { "email": "susie@example.com", "name": "Susie Park" }, "connector": { "email": "alex@example.com", "name": "Alex Rivera" } }' ``` **200 response** ```json { "item": { "intro": { "id": "intro-uuid", "attributes": { "source": "historical" } }, "message": "OK" }, "duplicate": false, "duplicate_check": "full" } ``` **Possible errors** - `400 invalid_request` — a party has neither `contact_id` nor `email`, or requester and target are the same person. - `401 unauthorized`. - `403 forbidden` — you are not the requester, target, or connector. - `404 not_found` — a `contact_id` does not exist. --- ## GET /v1/contacts Either incremental sync (with `since`) or name+email lookup. The two modes are mutually exclusive; if `email` or `q` is set, lookup mode runs. *In lookup mode wraps `GET https://api.brdg.app/api/v4/contacts/by_name_and_email`. Otherwise wraps `GET https://api.brdg.app/api/v4/contacts/since/:since`.* **Query parameters — incremental sync** | Name | Type | Required | Description | |------|------|----------|-------------| | `since` | number or ISO-8601 | no | Unix seconds or ISO timestamp. Defaults to `0`. | | `page` | integer ≥ 0 | no | Bridge page, 0-indexed. | | `data_version` | string | no | Forwards `Data-Version` header. Defaults to `2`. | **Query parameters — lookup** | Name | Type | Required | Description | |------|------|----------|-------------| | `email` | string | yes (in lookup mode) | Email to look up. | | `name` | string | no | Optional display name hint. | | `q` | string | alt. | Shortcut: `q=name|email` (pipe separator). | **Example request (sync)** ```bash curl "https://intros.brdg.app/api/v1/contacts?since=0" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response (sync)** ```json { "items": [ { "id": "contact-uuid", "type": "contact", "attributes": { "ref_id": "contact-ref-id", "name": "Alex Founder", "email": "alex@example.com", "company": "Acme", "position": "CEO" } } ], "next_cursor": null, "meta": { "last_update": 1710000000, "data_version": "2" } } ``` **Example request (lookup)** ```bash curl "https://intros.brdg.app/api/v1/contacts?email=alex%40example.com&name=Alex%20Founder" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response (lookup)** ```json { "item": { "contact": { "ref_id": "contact-ref-id", "id": "contact-uuid", "name": "Alex Founder", "email": "alex@example.com" }, "message": "OK" } } ``` **Possible errors** - `400 invalid_request` — `since` not parseable, or lookup `email` missing `@`. - `401 unauthorized`. --- ## POST /v1/contacts Create or upsert a contact by email. *Wraps `POST https://api.brdg.app/api/v4/contacts`.* **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `email` | string (email) | yes | Contact email. | | `name` | string \| null | no | Display name. | | `given_name` | string \| null | no | First name. | | `note` | string \| null | no | Free-form note saved on the contact. | | `enrichment_enabled` | boolean \| null | no | Override enrichment opt-in. | | `linkedin_profile_url` | string \| null | no | LinkedIn URL. | | `public_profile_pic_url` | string \| null | no | Photo URL. | | `alum_status` | string \| null | no | Alum/program affiliation. | **Example request** ```bash curl -X POST "https://intros.brdg.app/api/v1/contacts" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "email": "alex@example.com", "name": "Alex Founder", "linkedin_profile_url": "https://www.linkedin.com/in/alex" }' ``` **200 response** ```json { "item": { "contact": { "ref_id": "contact-ref-id", "id": "contact-uuid", "name": "Alex Founder", "email": "alex@example.com" }, "message": "OK" } } ``` **Possible errors** - `400 invalid_request` — `email` missing or not a valid email. - `401 unauthorized`. - `403 forbidden`. --- ## GET /v1/contacts/:contactId Fetch a single contact by id or ref id. Includes fields like `note` that the `since` feed omits. *Wraps `GET https://api.brdg.app/api/v4/contacts/:id`.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `contactId` | string | Contact `id` or `ref_id`. | **Example request** ```bash curl "https://intros.brdg.app/api/v1/contacts/$CONTACT_ID" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response** ```json { "item": { "contact": { "ref_id": "contact-ref-id", "id": "contact-uuid", "name": "Alex Founder", "email": "alex@example.com", "note": "Met at Acme Demo Day 2026." } } } ``` **Possible errors** - `401 unauthorized`. - `403 forbidden`. - `404 not_found`. --- ## PUT /v1/contacts/:contactId Update fields on an existing contact. All body fields are optional; omitted fields are left untouched. *Wraps `PUT https://api.brdg.app/api/v4/contacts/:id`.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `contactId` | string | Contact `id` or `ref_id`. | **Request body** | Field | Type | Required | Description | |-------|------|----------|-------------| | `email` | string (email) | no | Email override. | | `name` | string \| null | no | Display name. | | `given_name` | string \| null | no | First name. | | `note` | string \| null | no | Free-form note. | | `enrichment_enabled` | boolean \| null | no | Enrichment opt-in. | | `linkedin_profile_url` | string \| null | no | LinkedIn URL. | | `public_profile_pic_url` | string \| null | no | Photo URL. | | `alum_status` | string \| null | no | Alum/program affiliation. | **Example request** ```bash curl -X PUT "https://intros.brdg.app/api/v1/contacts/$CONTACT_ID" \ -H "Authorization: Bearer $BRIDGE_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "note": "Updated note." }' ``` **200 response** ```json { "item": { "contact": { "ref_id": "contact-ref-id", "id": "contact-uuid", "note": "Updated note." }, "message": "OK" } } ``` **Possible errors** - `400 invalid_request`. - `401 unauthorized`. - `403 forbidden`. - `404 not_found`. --- ## GET /v1/inbox/threads List CC inbox threads for the authenticated user. Each thread may embed its related classification rows. *Reads from Supabase under the caller's RLS scope.* **Query parameters** | Name | Type | Required | Description | |------|------|----------|-------------| | `status` | `"processed"` \| `"archived"` \| `"ignored"` | no | Filter by thread status. | | `limit` | integer 1–100 | no | Page size. Defaults to `50`. | | `cursor` | string | no | Opaque cursor returned as `next_cursor` from a prior call. | **Example request** ```bash curl "https://intros.brdg.app/api/v1/inbox/threads?status=processed&limit=20" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response** ```json { "items": [ { "id": "thread-uuid", "workspace_id": "workspace-uuid", "initiator_email": "connector@example.com", "subject": "Intro: Alex <> Susie", "status": "processed", "is_valid": true, "participant_count": 3, "seen": false, "bridge_intro_id": null, "email_thread_id": "email-thread-uuid", "created_at": "2026-04-23T18:20:00Z", "updated_at": "2026-04-23T18:25:00Z", "classifications": [ { "id": "classification-uuid", "connector_email": "connector@example.com", "requester_email": "alex@example.com", "target_email": "susie@example.com", "confidence_score": 0.92, "tags": ["intro_request"], "intro_status": "initialized", "created_at": "2026-04-23T18:21:00Z" } ] } ], "next_cursor": "eyJvZmZzZXQiOjIwfQ" } ``` **Possible errors** - `400 invalid_request` — `cursor` is not a valid encoded cursor. - `401 unauthorized`. --- ## GET /v1/inbox/threads/:threadId Fetch a single inbox thread with all its emails (chronological) and classifications (newest first). *Reads from Supabase under the caller's RLS scope.* **Path parameters** | Name | Type | Description | |------|------|-------------| | `threadId` | UUID | The thread id. | **Example request** ```bash curl "https://intros.brdg.app/api/v1/inbox/threads/$THREAD_ID" \ -H "Authorization: Bearer $BRIDGE_API_KEY" ``` **200 response** ```json { "item": { "thread": { "id": "thread-uuid", "subject": "Intro: Alex <> Susie", "status": "processed", "seen": false }, "emails": [ { "id": "email-uuid-1", "thread_id": "thread-uuid", "from_email": "connector@example.com", "to_emails": ["intros@cc.brdg.app", "susie@example.com"], "cc_emails": [], "subject": "Intro: Alex <> Susie", "body_text": "Susie, meet Alex…", "status": "processed", "created_at": "2026-04-23T18:20:00Z" } ], "classifications": [ { "id": "classification-uuid", "thread_id": "thread-uuid", "intro_status": "initialized", "confidence_score": 0.92, "tags": ["intro_request"], "created_at": "2026-04-23T18:21:00Z" } ] } } ``` **Possible errors** - `401 unauthorized`. - `404 not_found` — thread is missing or not visible to the caller. --- ## Deep links Open Intros in the browser with **Make intro** ready to go. Use this when your app knows who the user wants to introduce, for example the person they just met, and should hand off to Intros rather than send the intro itself. No API key: the link opens in the user's own signed-in session (personal workspace) and they review and send. **URL:** `https://intros.brdg.app/inbox?makeIntro=1&…` | Param | Description | |-------|-------------| | `makeIntro` | `1`. Required. | | `n1` | Email of the person being introduced (the requester). Best option: selects them directly, and creates the contact if they're new. | | `n2` | Email of the person they're being introduced to (the target). Usually left out so the user picks. | | `n1_name` | Full name. With `n1`, names a new contact. Without `n1`, Intros searches the user's contacts for this name and the user picks the right person. | | `n1_title` | Job title. | | `n1_company` | Company. | | `n1_linkedin` | LinkedIn profile URL (`linkedin.com/in/…`). Other URLs are ignored. | | `n2_name`, `n2_title`, `n2_company`, `n2_linkedin` | Same, for N2. | | `flow` | `opt_in` (forwardable, the default), `single_opt_in` or `fast`. Same values as `intro_flow` on [`POST /v1/intros`](#post-v1-intros). Unknown values are ignored. | Title, company and LinkedIn are saved on the contact only where it has no value yet. They never overwrite what the user already has. With a name and no email, they're saved once the user picks the person. Values over 200 characters (500 for LinkedIn URLs) are ignored. URL-encode every value. **Examples** Email known: ``` https://intros.brdg.app/inbox?makeIntro=1&n1=joel%40acme.com&n1_name=Joel%20Smith&n1_title=CTO&n1_company=Acme&n1_linkedin=https%3A%2F%2Flinkedin.com%2Fin%2Fjoelsmith&flow=opt_in ``` Only a name: ``` https://intros.brdg.app/inbox?makeIntro=1&n1_name=Joel%20Smith&flow=opt_in ``` Open it in a new tab. If the user isn't signed in, they sign in first. **Building it in your app** Add a button such as "Offer an intro" wherever your app shows a person, like a call, a meeting or a profile. Send everything you know about them; Intros keeps only what's missing. ```ts type IntroPerson = { email?: string | null; name?: string | null; title?: string | null; company?: string | null; linkedinUrl?: string | null; }; export function makeIntroUrl( person: IntroPerson, flow: "opt_in" | "single_opt_in" | "fast" = "opt_in", ): string { const params = new URLSearchParams({ makeIntro: "1" }); const set = (key: string, value?: string | null) => { const v = value?.trim(); if (v) params.set(key, v); }; set("n1", person.email); set("n1_name", person.name); set("n1_title", person.title); set("n1_company", person.company); set("n1_linkedin", person.linkedinUrl); params.set("flow", flow); return `https://intros.brdg.app/inbox?${params.toString()}`; } // Offer an intro ``` **Deep link or API?** Use a deep link when the user should pick who to introduce, or review the email, in Intros. Use [`POST /v1/intros`](#post-v1-intros) (or the MCP `make_intro` tool) when your app or agent already has both people and the message and sends it itself. AI apps connected over MCP get the same reference from `get_intros_guide` with topic `links`. --- ## Server configuration (deploy) Vercel serverless functions need the following environment variables. Non-`VITE_` names are preferred in production; `VITE_*` fallbacks are accepted for local parity. | Variable | Purpose | |----------|---------| | `BRIDGE_API_URL` | Bridge API base. Defaults to `https://api.brdg.app`. | | `SUPABASE_URL` | Supabase project URL for inbox reads. | | `SUPABASE_ANON_KEY` | Supabase anon key (RLS is enforced via the user's JWT). | | `PROJECT_NAME` | Bridge ↔ Supabase JWT exchange project name (`cc` in this product). | --- ## See also - **Bridge core API:** `https://api.brdg.app` — v4 introductions and contacts are the source of truth. - **Raise public API:** [raise.brdg.app/developers/api](https://raise.brdg.app/developers/api) — sibling app using the same Bridge API key pattern. - **OpenAPI spec:** [/api/v1/openapi.yaml](/api/v1/openapi.yaml). - **LLM-friendly mirrors:** [/llms.txt](/llms.txt) · [/llms-full.txt](/llms-full.txt).