# GET /rest/api/3/field/{}/context/defaultValue stops working

Calls to GET /rest/api/3/field/{id}/context/defaultValue on Jira and Confluence Cloud REST APIs stopped working on October 1, 2026.

On October 1, 2026, the endpoint GET /rest/api/3/field/{id}/context/defaultValue was removed. Calls to this endpoint fail since that date. The API was deprecated ahead of its removal to prepare for a replacement supporting multiple default values per issue type.

## What to use instead

Move to the replacement custom field context default value API announced under CHANGE-3082. Because the replacement was announced as coming soon, verify that it is available before migrating.

Atlassian's replacement API was announced as coming soon: someone must check it is available before migrating.

- API: Jira and Confluence Cloud REST APIs (*.atlassian.net)
- Kind: Endpoint removal
- Takes effect: October 1, 2026
- Calls after that day: fail
- Calls it hits: `GET /rest/api/3/field/{id}/context/defaultValue`
- Source: [Announcement](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-contexts/)
- Verified: November 6, 2026, against Jira and Confluence Cloud REST APIs's own pages
- Page: https://www.okapi.bot/providers/jira-and-confluence-cloud-rest-apis/breaking-changes/get-rest-api-3-field-context-defaultvalue-stops-working/

## Jira and Confluence Cloud REST APIs's words

> This API is deprecated and will be removed in October 2026. A replacement API that supports multiple default values per issue type within a context is coming soon.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent