> ## Documentation Index
> Fetch the complete documentation index at: https://lmn.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# LMN Open API

> Browse Korean inventory, place orders on behalf of dealers, and track every car through delivery.

LMN's Open API gives partners programmatic access to Korean used-car inventory (auction + dealer sources) and a full order-lifecycle integration: browse → bid commitment → acquisition → Korean export → ocean shipping → delivery confirmation.

## What you can do

<CardGroup cols={2}>
  <Card title="Browse inventory" icon="car" href="/endpoints/vehicles">
    Filter the live catalog by make, model, year, mileage, price, auction-house, accident grade, and more. Returns landed-cost estimates per vehicle.
  </Card>

  <Card title="Watch buying conditions" icon="bell" href="/eagle-eye">
    Save dealer buying briefs and receive alerts when new matches, price drops, repeat listings, or removals appear.
  </Card>

  <Card title="Place orders" icon="gavel" href="/endpoints/orders">
    Commit to a vehicle on behalf of your dealer with a bid ceiling. LMN handles bidding/purchasing on your behalf.
  </Card>

  <Card title="Receive webhooks" icon="bolt" href="/webhooks/overview">
    Real-time event notifications for order state changes and Eagle Eye watch activity.
  </Card>

  <Card title="Push fulfillment" icon="ship" href="/endpoints/status-updates">
    Confirm post-departure events (in transit, customs, delivered) to close the loop.
  </Card>
</CardGroup>

## Operational boundary

LMN handles inventory aggregation, bidding/purchasing, Korean-side export logistics, and vessel loading. **Partners handle** dealer identity & KYC, ocean freight booking after vessel handoff, destination customs, and local delivery. See [conventions](/conventions) for the full split.

## Money model

**No upfront deposits.** Order creation is a bid commitment, not a payment. Payment owed only on `secured` (auction win), wire transfer same US business day. Partner-to-dealer payment arrangements are entirely outside this API.

## Get started

Sandbox access is self-serve — no sales call, no waiting on an approval queue. You can be making authenticated calls in about five minutes.

<Steps>
  <Step title="Sign up">
    Create an account at [console.lmnauto.com](https://console.lmnauto.com/console/signup) with your work email and company name. Approval is automatic — there is no queue. You'll get a one-time code by email to log in.
  </Step>

  <Step title="Mint a sandbox key">
    On the **Keys** page, create a sandbox key. It's shown **once**, at creation — LMN stores only a hash and cannot show it to you again. Sandbox keys are prefixed `lmn_stg_` and carry a **1,000-call trial budget**, which is plenty to build and certify an integration.
  </Step>

  <Step title="Make your first call">
    ```bash theme={null}
    curl -H "x-api-key: lmn_stg_YOUR_KEY" \
      "https://sandbox-api.lmnauto.com/v1/vehicles?limit=1"
    ```

    A `200` means you're integrated. See [Quickstart](/quickstart) for the full first-integration path, or [Build with AI](/ai-builders) if you're using Lovable, Cursor, or Claude.
  </Step>

  <Step title="Browse + place a sandbox order">
    Sandbox read endpoints return current auction inventory, so you build against realistic data. Sandbox orders are non-binding; coordinate with LMN ops to move test orders through lifecycle states for webhook/status testing.
  </Step>

  <Step title="Request production access">
    When your integration is ready, submit the **Request production access** form in the console. Production is approval-gated — we review your use case and expected volume and get back to you within 24 hours. Approval unlocks production key minting; production keys have no call budget.
  </Step>
</Steps>

<Note>
  **Sandbox keys have no IP allowlist.** You can call the sandbox API from a laptop, a CI runner, or a serverless function with rotating egress IPs — nothing to register. Production keys *are* IP-restricted; you'll register egress ranges at approval time. See [Authentication](/authentication).
</Note>

## Stable contract

The API is versioned via the `/v1/` prefix. Breaking changes increment the major version with a 90-day deprecation window. Additive enum values and documentation/example corrections ship under the current major version and are recorded in the [changelog](/changelog).