Okapi Okapi

Jira and Confluence Cloud REST APIs GET /rest/api/3/field/{id}/context/defaultValue endpoint removal

Stopped workingSubscribe to Jira and Confluence Cloud REST APIsShare

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.


Calls it hits

  • GET /rest/api/3/field/{id}/context/defaultValue

What to use instead of these calls

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.

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

Jira and Confluence Cloud REST APIs, Announcement

Facts

API
Jira and Confluence Cloud REST APIs *.atlassian.net
Kind
Endpoint removal
Takes effect
October 1, 2026
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Jira and Confluence Cloud REST APIs's own pages

Questions

When does this change take effect?

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

What happens to calls after October 1, 2026?

They have failed since October 1, 2026.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


More from Jira and Confluence Cloud REST APIs 10

  1. GET /rest/api/3/workflow/searchEndpoint removal Stopped working
  2. PUT /rest/api/3/field/{id}/context/defaultValueEndpoint removal Stopped working
  3. No date GET /rest/api/2/searchEndpoint removal Deprecated, no date
  4. No date GET /rest/api/3/issue/createmetaEndpoint removal Deprecated, no date
  5. No date GET /rest/api/3/searchEndpoint removal Deprecated, no date
  6. No date GET /rest/api/latest/searchEndpoint removal Deprecated, no date
  7. No date POST /rest/api/2/expression/evalEndpoint removal Deprecated, no date
  8. No date POST /rest/api/2/searchEndpoint removal Deprecated, no date
  9. No date POST /rest/api/3/expression/evalEndpoint removal Deprecated, no date
  10. No date POST /rest/api/3/searchEndpoint removal Deprecated, no date

You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub

Get notifications

Subscribe to Jira and Confluence Cloud REST APIs

Hear about each breaking change Jira and Confluence Cloud REST APIs announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Jira and Confluence Cloud REST APIs

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.