Why do I get 404 on http://x.x.x.x/rest/api/2/field/customfield_11200/option

Question

Why do I get 404 on http://x.x.x.x/rest/api/2/field/customfield_11200/option The call to http://x.x.x.x/rest/api/2/field gives me back... [ { "id": "fixVersions", "name": "Fix Version/s", "custom": false, "orderable": true, "navigable": true, "searchable": true, "clauseNames": [ "fixVersion" ], "schema": { "type": "array", "items": "version", "system": "fixVersions" } }, { "id": "customfield_11200", "name": "Customer", "custom": true, "orderable": true, "navigable": true, "searchable": true, "clauseNames": [ "cf[11200]", "Customer" ], "schema": { "type": "option", "custom": "com.atlassian.jira.plugin.system.customfieldtypes:select", "customId": 11200 } }, So why does... GET http://x.x.x.x/rest/api/2/field/customfield_11200/option Give...

404

null for uri: http://10.210.51.160/rest/api/2/field/customfield_11200/option Is this feature only on the Cloud platform REST api ? Or is it in the on site version as well?

Yashashvi Dave · Answer

@Daniel Wester followup questions on this -

1) Is field context endpoint still not available on Jira service api?

2) If not, is there any other way to fetch custom field context using REST API on Jira Server?

Thanks

Amir Katz (Outseer) · Answer

The link provided by @Daniel Wester is titled

JIRA Server platform REST API reference

and indeed, there is no API to get list of all custom fields.

Daniel Wester · Answer

You answered the question - It's only available on Jira Cloud api. You'll want to take a look at: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/

Jira Cloud and Jira Server aren't really the same products anymore (from an api perspective).