Look up growth predictions

Before you begin

This example was verified with Predictions and Insights access. 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.

Persona: Go-to-market teams

Use case: Look up growth predictions

Primary APIs: Growth Prediction Search and Growth Prediction Lookup

Before interpreting the results, review prediction scores and timing. See API Packages Overview for the reference matching your licensed access.

Step 1:

Search for a Growth Prediction

In this step, we’ll request the latest Growth Prediction for a specific company to confirm whether one exists.

Endpoint

https://api.crunchbase.com/v4/data/searches/growth_predictions

Query

For the first part of this exercise, we’re going to search for the latest Growth Predictions for the company Writer (UUID: a3674669-6d9e-4f70-895f-3c8c99bcb7ad):

Now that we have the field_id defined, here is the sample query we can run that will search for available Growth Predictions for the company Writer:

curl --include --request POST \
  --url 'https://api.crunchbase.com/v4/data/searches/growth_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.

Response

Response examples below are historical, shortened JSON samples; search samples show one entity and card samples show at most one record per card. Other fields or records may be omitted. Counts and values change; count is the total matching records, while entities contains the returned page.

The historical response reports 10 matching growth prediction records, with the date of each prediction and their unique identifier (UUID). This UUID can be used to get more information about that specific Growth Prediction (more on that below).

{
  "count": 10,
  "entities": [
    {
      "uuid": "030b0f7c-8dc3-4b25-9ce2-baed5d8f1ee6",
      "properties": {
        "identifier": {
          "image_id": "0566443d3dbe4075aa9dad798801e206",
          "uuid": "030b0f7c-8dc3-4b25-9ce2-baed5d8f1ee6",
          "entity_def_id": "growth_prediction",
          "value": "Growth Prediction 2026-03-28"
        },
        "organization": {
          "permalink": "writer",
          "image_id": "jqgtyt2qclr1ikl5mpjv",
          "uuid": "a3674669-6d9e-4f70-895f-3c8c99bcb7ad",
          "entity_def_id": "organization",
          "value": "Writer"
        },
        "generated_on": "2026-03-28"
      }
    }
  ]
}

Outcome

By using the Search GrowthPrediction Entities endpoint, we’re able to query Crunchbase for a list of all the Growth Predictions that have been made for the particular company that meets our ICP. From here, we can take the latest one and retrieve all the information about it.

Step 2

Retrieve and Operationalize the Latest Growth Prediction

Now that we have a list of the Growth Predictions for the company Writer, we’re now going to query Crunchbase for the latest one, and retrieve all the information we have for that prediction. This will help your teams retrieve the full prediction object — including probability score and probability tier — to determine whether the company is likely to experience future high-growth. These fields can be integrated into scoring models, CRM updates, or notification systems to prioritize outreach to accounts that may require scaling solutions or increased engagement.

Endpoint

https://api.crunchbase.com/v4/data/entities/growth_predictions/\{entity_id}

Query

For the second part of this exercise, we’re going to retrieve the data behind the latest growth prediction that we found in the previous query (above) using its unique identifier (UUID). Replace {prediction_uuid} below with the UUID of the latest record selected in Step 1:

Key Fields for this Query

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

Response

The following illustrative response shows a growth prediction lookup. Your response depends on the prediction UUID selected in Step 1. The shortened example shows selected top-level properties; the request explicitly selects the context fields shown below. card_ids=fields also returns a separate cards.fields object, which is omitted from this example. Fields may be absent when no value is available.

{
  "properties": {
    "identifier": {
      "uuid": "030b0f7c-8dc3-4b25-9ce2-baed5d8f1ee6",
      "value": "Growth Prediction 2026-01-24",
      "image_id": "7299fb1a70b6414b8adb52b6d56d486b",
      "entity_def_id": "growth_prediction"
    },
    "probability_score": 0.9529,
    "runway_speculation": {
      "uuid": "5d591058-76cc-4fa6-8ad1-be4d0186b70d",
      "value": "Series C - Writer",
      "image_id": "jqgtyt2qclr1ikl5mpjv",
      "permalink": "writer-series-c--5d591058",
      "entity_def_id": "funding_round"
    },
    "unicorn_status": "c200_evidence_present",
    "created_at": "2026-01-15T09:59:33Z",
    "key_employee_changes": [
      {
        "uuid": "d3be8cd0-ad46-4507-9c59-a0d44b234311",
        "image_id": "7299fb1a70b6414b8adb52b6d56d486b",
        "entity_def_id": "key_employee_change"
      },
      {
        "uuid": "356d3002-3eb9-43c1-b4f8-3c620bdc0f0c",
        "image_id": "7299fb1a70b6414b8adb52b6d56d486b",
        "entity_def_id": "key_employee_change"
      }
    ],
    "probability_tier": "p100_positive_high"
  }
}

Outcome

From this response, we’re able to conclude:

Having this level of detail on what’s coming around the corner allows your teams to know which companies to target before your competitors do.

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. For a complete result set, follow search pagination while preserving the filters and ordering. For request failures, use the shared request and retry guidance.