> ## 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.

# Poll funding updates

> Retrieve a funding feed, consume cursor pages, and persist a polling checkpoint.

[Human guide: work with your agent →](/docs/human/recipes/poll-funding-updates)

> [!NOTE]
>
> Read a funding window and advance its checkpoint only after consuming its
> cursor pages.

This procedure uses the [Funding feed contract](/docs/funding-data), a pull-only
feed rather than a company-specific Monitor. Each request is metered.

## Get the first page

Inspect the live contract and price before calling it:

```bash theme={null}
deepline 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.

## 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" > funding-page-1.json
```

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
```

## 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.

## Verify this task

Preserve the window, returned cursor, and successful page outcomes. Advance the durable checkpoint after the entire chosen window is consumed.

Ask your agent to explain a failed check before repeating work or expanding the scope.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.