Goals API: startValue added to key results

The Goals API now supports a new startValue field on measurable key results, so integrations can store and retrieve the starting value used to calculate progress, especially for “from X to Y” goals (including decreasing measures).

What’s changed

• Added a new optional startValue field for key results with measureType = numeric, currency, or percentage.
• Supported in the following endpoints:
  • POST /v1/goals/goals/{goalId}/key-results (create key results)
  • PATCH /v1/goals/goals/{goalId}/key-results (update key result details)
  • POST /v1/goals/goals/key-results/search (search key results)
• Search responses now return startValue together with target, currentValue, and progress.

Why this matters

• Enables more accurate progress tracking for key results that measure change from an existing value (for example, “Increase from 63 to 70”).
• Supports decreasing measures (for example, “Reduce costs from 450,000 to 350,000”) while keeping progress calculations consistent between Bob and external systems.

How does this affect you

• No breaking changes. Existing requests continue to work if you don’t send startValue.
• If you create/update measurable key results, you can optionally send startValue to preserve the starting value.
• If you consume search responses, you may start seeing startValue returned for measurable key results (for existing key results, it may default to 0 when no starting value was previously set).

To learn more, see Goals API.