Look up funding predictions

Find a company’s latest funding prediction and inspect its timing.

Before you begin

Your API key must include the fields and collections requested below. Check your API package if an endpoint or field is unavailable. Complete your first API request to set CRUNCHBASE_API_KEY in bash or zsh. Commands below include response headers; look for HTTP 200, then read the JSON body.

Primary APIs: Funding Prediction Search and Funding Prediction Lookup

Goal: Retrieve the latest prediction’s UUID, probability score, and timing values for a company.


1. Find funding predictions

Endpoint

POST https://api.crunchbase.com/v4/data/searches/funding_predictions

Query

Search for Writer’s funding prediction records using its organization UUID, a3674669-6d9e-4f70-895f-3c8c99bcb7ad, then identify the latest record as described below.

Fields used in this query

field_idWhat this field doesoperator_id (these are the compatible operators per field)
organizationFilter by the organization’s UUID. For this example, we’re using the company Writer, with the UUID: a3674669-6d9e-4f70-895f-3c8c99bcb7ad)blank; contains; eq; includes; not_contains; not_eq; not_includes; starts

Scroll to view all columns →

Run this query to retrieve Writer’s available funding prediction records:

curl --include --request POST \
  --url 'https://api.crunchbase.com/v4/data/searches/funding_predictions' \
  --header "X-cb-user-key: $CRUNCHBASE_API_KEY" \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --data '{
  "field_ids": [
    "organization",
    "generated_on"
  ],
  "query": [
    {
      "field_id": "organization",
      "operator_id": "includes",
      "type": "predicate",
      "values": [
        "a3674669-6d9e-4f70-895f-3c8c99bcb7ad"
      ]
    }
  ],
  "limit": 3
}'

Read generated_on to identify the latest prediction. This request does not specify a sort order. Paginate through all matching records, preserve the organization filter, and select the record with the greatest generated_on value. Use that record’s UUID in Step 2; do not assume the first returned record is the latest.

Example response

The historical example below shows one of 10 matching funding prediction records, including its date and UUID. count is the total matches; entities contains the returned page. The sample is shortened, so other fields and records may be omitted. Counts and values can change.

{
  "count": 10,
  "entities": [
    {
      "uuid": "2cc587c2-124d-48fd-840e-6841a7f58f04",
      "properties": {
        "identifier": {
          "image_id": "fd41cd7328c54618aeda4f9e3f0d45ef",
          "uuid": "2cc587c2-124d-48fd-840e-6841a7f58f04",
          "entity_def_id": "funding_prediction",
          "value": "Funding Prediction 2026-05-23"
        },
        "organization": {
          "permalink": "writer",
          "image_id": "jqgtyt2qclr1ikl5mpjv",
          "uuid": "a3674669-6d9e-4f70-895f-3c8c99bcb7ad",
          "entity_def_id": "organization",
          "value": "Writer"
        },
        "generated_on": "2026-05-23"
      }
    }
  ]
}

Interpret the response

Each returned entity identifies a funding prediction for the selected organization. Compare properties.generated_on across all matching pages and use the UUID of the latest record in Step 2.


2. Retrieve the latest funding prediction

Retrieve the selected funding prediction’s probability score and timing values using its UUID.

Endpoint

GET https://api.crunchbase.com/v4/data/entities/funding_predictions/{entity_id}

Query

Replace {prediction_uuid} with the UUID of the latest funding prediction selected in Step 1:

Fields used in this query

field_idWhat this field means
created_atThe date when this prediction was created and added to our graph
probability_scoreThe predicted probability that this Organization will receive funding
probability_score_timeseriesProvides a timeframe for when we expect this prediction to come true
probability_tierThe predicted probability of this organization raising funds is divided into distinct tiers that quantify the likelihood of this event.

Scroll to view all columns →

Run this request to retrieve the prediction fields listed above:

curl --include --request GET \
  --url 'https://api.crunchbase.com/v4/data/entities/funding_predictions/{prediction_uuid}?field_ids=created_at,probability_score,probability_score_timeseries,organization,probability_tier&card_ids=' \
  --header "X-cb-user-key: $CRUNCHBASE_API_KEY" \
  --header 'Accept: application/json'

Example response

The following illustrative response shows the shape of a funding prediction lookup. Your response depends on the prediction UUID selected in Step 1.

{
  "properties": {
    "organization": {
      "uuid": "a3674669-6d9e-4f70-895f-3c8c99bcb7ad",
      "value": "Writer",
      "image_id": "jqgtyt2qclr1ikl5mpjv",
      "permalink": "writer",
      "entity_def_id": "organization"
    },
    "identifier": {
      "uuid": "81bb80ba-9bf9-4fb7-8d43-0800a09657c4",
      "value": "Funding Prediction 2025-10-25",
      "image_id": "35429ad1989b4996a19407e018d6460a",
      "entity_def_id": "funding_prediction"
    },
    "probability_score": 0.9385,
    "created_at": "2025-10-25T16:58:36Z",
    "probability_tier": "p200_positive_low",
    "probability_score_timeseries": {
      "months_24_plus": 7.017093258889777e-06,
      "months_00_to_05": 0.9999927168195302,
      "months_06_to_11": 1.136322591185592e-07,
      "months_12_to_24": 1.52454951763353e-07
    }
  }
}

Interpret the response

Read the score and timing values separately:

Overall probability and timing are separate outputs

In this illustrative response, probability_score is 0.9385 (about 94%). Separately, probability_score_timeseries.months_00_to_05 is approximately 0.999993. The overall score and timing values are distinct outputs; 94% is not the value reported for the 0–5-month interval.

Check your result

Check the organization UUID and prediction generation date before using a score. An empty result is not a zero probability. Interpret scores and timing using the prediction definitions.

Search requests here use limit: 3 for a small first page. Follow the pagination guidance above for a complete result set, preserving the filters and ordering. For request failures, use the shared request and retry guidance.


Did this page help you?