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

# Funding data feed

> Poll Deepline’s public funding-round feed, page through results, and keep your own durable cursor.

`deepline_native_get_funding_updates` is the public read endpoint for
Deepline's globally scoped funding-rounds feed. It returns funding discoveries
already in the feed; it does not deploy a Monitor, create a radar, send a
webhook, or change any data.

<Info>
  Each call costs \*\*$0.10** in Deepline usage, regardless of whether the page
      contains one update or 100. `limit` defaults to 100 and cannot exceed 100, so
      a full page costs $0.10. Each subsequent cursor page is a new call.
</Info>

Use this feed when you want to poll global funding discoveries and qualify them
against your own account list. It is not a company-specific monitor and it has
no company, industry, round-stage, or source filter. The optional `since`
field filters by when Deepline discovered an update.

## Get the first page

Inspect the live contract and price before calling it:

```bash theme={null}
deepline tools describe deepline_native_get_funding_updates --json
```

The first call returns up to the 100 most recent updates:

```bash theme={null}
FUNDING_PAYLOAD='{"limit":100}'
deepline tools execute deepline_native_get_funding_updates --input "$FUNDING_PAYLOAD" --json
```

This is a direct read. If you need scheduled execution or durable processing,
put the call in an owned Play or run it from your own scheduler; this endpoint
does not create that schedule for you.

## Inputs and paging

| Field    | Required | Meaning                                                                        |
| -------- | -------- | ------------------------------------------------------------------------------ |
| `limit`  | No       | Maximum number of updates in one page. Integer from 1 to 100; defaults to 100. |
| `since`  | No       | ISO 8601 timestamp. Returns updates discovered at or after that time.          |
| `cursor` | No       | Opaque `next_cursor` value from a previous response. Omit on the first call.   |

The response orders updates most recent first. It includes `has_more` and
`next_cursor`; when `has_more` is true, pass the exact `next_cursor` value in
the next request. Do not construct or alter cursor values.

## Call the API

Use a workspace-scoped API key from a trusted server or worker. Do not expose
the key in browser code.

```bash theme={null}
FUNDING_REQUEST='{"payload":{"limit":100}}'

curl -fsS -X POST \
  "https://code.deepline.com/api/v2/integrations/deepline_native_get_funding_updates/execute" \
  -H "Authorization: Bearer $DEEPLINE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary "$FUNDING_REQUEST"
```

For the next page, persist the prior response and build the request from its
cursor. Only run this when the prior response has `data.has_more: true`.

```bash theme={null}
NEXT_CURSOR="$(jq -er '.data.next_cursor' funding-page-1.json)"
FUNDING_REQUEST="$(jq -cn --arg cursor "$NEXT_CURSOR" '{payload: {cursor: $cursor, limit: 100}}')"

curl -fsS -X POST \
  "https://code.deepline.com/api/v2/integrations/deepline_native_get_funding_updates/execute" \
  -H "Authorization: Bearer $DEEPLINE_API_KEY" \
  -H "Content-Type: application/json" \
  --data-binary "$FUNDING_REQUEST" > funding-page-2.json
```

The following is a representative response from the checked-in contract
fixture:

```json theme={null}
{
  "data": {
    "status": "success",
    "code": 200,
    "message": "Updates retrieved successfully",
    "updates": [
      {
        "update_id": "a0dbeb25-7950-43dc-bb17-6fdc3560da14",
        "record_id": "0df88ee0-cb19-4f17-98d4-0a4f91a73f44",
        "update_type": "radar_finding",
        "discovered_at": "2026-08-21T17:28:45Z",
        "data": {
          "domain": null,
          "radar_id": "814b2e61-bf10-496d-988d-96aaf8319158",
          "radar_type": "industry_funding_rounds",
          "custom_fields": {},
          "next_charge_at": null
        },
        "content": {
          "round": "Series C",
          "amount_usd": 38500000,
          "announced_at": "2026-08-21",
          "company": {
            "name": "Helcim",
            "domain": "helcim.com",
            "hq_country": "Canada",
            "profile_url": "https://www.linkedin.com/company/helcim"
          },
          "references": [
            "https://www.helcim.com/company/helcim-raises-series-c/"
          ]
        }
      }
    ],
    "has_more": true,
    "next_cursor": "eyJyIjoiMjAyNi0wOC0yMFQyMzoxMDowNC4yNzJaIiwiaSI6IjI0MGMxMDBmLWZmMDItNDVlNS1iYzJjLTc2YmIzYjk4YTViYSJ9",
    "timestamp": "2026-08-23T18:24:21Z"
  }
}
```

Use `update_id` as your durable deduplication key. `round` can be `Unknown`
when the source reports a raise without a disclosed stage; treat it as an
unstaged round, not as a funding category.

## Choose a polling strategy

Store the last successful `since` timestamp and the completed cursor chain in
your own system. Use `since` to narrow a later polling window, then consume all
cursor pages for that window before advancing your checkpoint. The contract
does not promise a publication cadence, so choose your polling interval based
on how quickly your team needs to review new funding events.

For a push-based external source that writes event rows into Deepline, use a
[Monitor](/docs/plays/monitors). This funding endpoint remains a pull-only read
feed.