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

[Jeff Porter]

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

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<status>
 <status-code>404</status-code>
 <message>null for uri: http://10.210.51.160/rest/api/2/field/customfield_11200/option</message>
</status>

Is this feature only on the Cloud platform REST api ?

Or is it in the on site version as well?

[Daniel Wester]

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

[Amir Katz (Outseer)]

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.

[Yashashvi Dave]

@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