Complete prospect data, one clean request.

Retrieve ranked prospect dossiers that keep source-backed facts separate from analyst conclusions. Every government record includes an official link and a reproducible locator. Draft material is never returned.

Getting access

Open your private invitation link, create your profile, and save the production API key shown during setup. The key appears once. Future dashboard sign-ins use a secure link sent to your work email—no password or shared portal credential required.

Quickstart

curl https://dashboard.osmaura.com/v2/prospects \
  -H "Authorization: Bearer $SIGNALS_API_KEY"

The response contains the latest published edition and its complete prospect dossiers in ranked order. A normal edition contains 20 prospects.

Authentication

Send your production read key as a bearer token on every request:

Authorization: Bearer signals_live_••••••••••••

Keys are scoped to one account. The API infers the account from the key, so requests never include organization names or account identifiers.

Get prospects

Returns your latest published edition. To retrieve a historical edition, pass an ISO date:

GET /v2/prospects?date=2026-07-21

Response shape

{
  "object": "prospect_edition",
  "schema_version": "2.0",
  "edition_date": "2026-07-21",
  "revision": 2,
  "published_at": "2026-07-22T02:14:09Z",
  "count": 20,
  "prospects": [
    {
      "id": "sig_01example",
      "prospect": {
        "type": "organization",
        "name": "Example Company",
        "legal_names": ["Example Company, Inc."],
        "domain": "example.com",
        "locations": [{"city": "Austin", "state": "TX", "country": "US"}],
        "identifiers": {"cik": null, "uei": null}
      },
      "data": {
        "dol_oflc": {
          "lca": {
            "statistics": {
              "total_filings": 3,
              "named_counsel_filings": 0
            },
            "records": [{
              "id": "dol_lca_I-200-example",
              "case_number": "I-200-example",
              "status": "Certified",
              "source": {
                "publisher": "U.S. Department of Labor",
                "official_page_url": "https://www.dol.gov/agencies/eta/foreign-labor/performance",
                "dataset": {
                  "filename": "LCA_Disclosure_Data_FY2026_Q2.xlsx",
                  "download_url": "https://www.dol.gov/media/LCA_Dislclosure_Data_FY2026_Q2.xlsx",
                  "record_layout_url": "https://www.dol.gov/sites/dolgov/files/ETA/oflc/pdfs/LCA_Record_Layout_FY2026_Q2.pdf",
                  "data_through": "2026-03-31"
                },
                "record_locator": {
                  "column": "CASE_NUMBER",
                  "value": "I-200-example"
                },
                "retrieved_at": "2026-07-21T20:00:00Z"
              }
            }]
          }
        },
        "contacts": []
      },
      "analysis": {
        "ranking": {
          "rank": 1,
          "disposition": "qualified",
          "confidence": 0.96,
          "scores": {"evidence_strength": 96, "overall_rank": 92}
        },
        "summary": "Three reviewed LCAs show a small sponsorship program with repeated process friction and no named filing counsel.",
        "why_now": {
          "narrative": "A dated deployment milestone raises the operational cost of another delayed technical hire, although it does not prove that a new filing is imminent.",
          "trigger_date": "2026-07-09",
          "urgency_window": "Before the next sponsored technical hire.",
          "evidence_ids": ["event_example", "dol_lca_I-200-example"]
        },
        "counsel_analysis": {
          "classification": "observed_pro_se",
          "narrative": "None of the three reviewed LCAs names an attorney or law firm. This applies only to the reviewed public filings and cannot rule out private advice.",
          "filings_reviewed": 3,
          "named_counsel_filings": 0,
          "evidence_ids": ["dol_lca_I-200-example"]
        },
        "lead_factors": [],
        "counterevidence": [],
        "context_only": [],
        "limitations": []
      },
      "coverage": {
        "sources": [{
          "source": "dol_lca",
          "status": "matched",
          "data_through": "2026-03-31",
          "record_count": 3
        }],
        "identity_warnings": [],
        "known_gaps": ["Private legal advice is not publicly observable."]
      }
    }
  ]
}

Response structure

Every prospect item has exactly five top-level fields: id, prospect, data, analysis, and coverage. Rank belongs under analysis.ranking.

Data and analysis never blur together

A filing status, date, attorney field, grant amount, or approval count belongs in data. A total calculated from those records is also data when its inputs are named. Statements such as “observed pro se,” the lead score, and the explanation of why a fact matters belong only in analysis.

Counsel is never represented as a bare boolean. The response reports the number of reviewed filings, the number naming counsel, the review scope, confidence, and the limitation that public records cannot reveal every private advisory relationship.

Official links and record locators

Every government-derived record includes a clickable official page. Bulk datasets also include the exact downloadable file, record layout when available, data-through date, and a locator such as a case number and column name. Interactive sources include the exact query needed to reproduce the result.

A source code such as dol_lca is never sufficient by itself. Use the links and locator inside the record’s source object to verify the fact.

Edition history

Lists your published edition dates, revision numbers, publication times, and counts. It does not expose drafts or internal review state.

Errors

{
  "error": {
    "code": "not_found",
    "message": "No published signal edition was found."
  }
}

Version 1 compatibility

GET /v1/signals and GET /v1/signal-editions remain available for existing integrations. New integrations should use version 2, which returns complete prospect dossiers rather than the compact legacy signal shape.

Key rotation

Open the signals dashboard, choose API keys, and select Rotate. The old key is revoked immediately and the replacement secret is displayed once.

Published responses include an ETag. Send If-None-Match to avoid downloading an unchanged edition.