Skip to content
Bindly Developer Docs

Quickstart

The fastest path to a working integration is the bindly CLI. Install it, sign in once, and you can start intake sessions and submit to Hedge from your terminal or a script. If you would rather call the REST API directly, skip to Call the API directly.

Use the CLI

Section titled “Use the CLI”

  1. Install the CLI.

    Terminal window
    npm i -g bindly-cli

    Homebrew and a one-line install script are also available. See the CLI guide for all three options.

  2. Sign in.

    Terminal window
    bindly login

    bindly login uses the OAuth 2.1 device flow: it prints a short code and a URL, you approve the sign-in in Bindly, and the CLI stores a short-lived token for you. For non-interactive automation, sign in with a workspace API key instead: bindly login --api-key bsk_....

  3. Start an intake session.

    Terminal window
    bindly session new --insured "Acme HVAC" --state TX --lob general_liability

    This opens a fill session for the insured and returns its id. Continue filling the intake in the Bindly app, or drive it from an MCP assistant.

  4. Submit to Hedge.

    Terminal window
    bindly session submit <session-id>

    Once the session is ready, this forwards the filled forms to Hedge on your workspace’s connected account and returns the resulting Hedge submission id.

Call the API directly

Section titled “Call the API directly”

Every CLI command maps to a REST endpoint under https://engine.bindly.insure. Requests are JSON over HTTPS. Authenticate with a workspace API key, sent either as a bearer token or an X-API-Key header. See Authentication for the OAuth options.

Start a session

Section titled “Start a session”

The only required field is the applicant’s insured_name. state, lobs, and naics_code are optional and help Bindly build the right application.

Terminal window
curl -X POST "https://engine.bindly.insure/org/sessions" \
  -H "Authorization: Bearer $BINDLY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "insured_name": "Acme HVAC",
    "state": "TX",
    "lobs": ["general_liability"],
    "naics_code": "238220"
  }'

The response contains the new session, including its session_id, which you use to track progress and submit.

Submit to Hedge

Section titled “Submit to Hedge”
Terminal window
curl -X POST "https://engine.bindly.insure/org/sessions/$SESSION_ID/submit" \
  -H "Authorization: Bearer $BINDLY_API_KEY"

Bindly uploads the session’s filled forms to Hedge on your workspace’s connected account, finalizes the submission, and returns the Hedge submission id. Continue in the API Reference.

Where to go next

Section titled “Where to go next”

Create a workspace API key, or set up the OAuth 2.1 device flow and browser sign-in. See Authentication.