developer_class.update
Description
Update a developer class or a list of developer classes Please see Updating Objects for an overview of how the update method works.
Parameters
developer_class
An developer_class object, as described by the object.describe call. If a field in the developer_class object is ommitted, no change will be made to that field. If extra fields are passed, they will be ignored. The primary identifier must be specified.
Response
An developer_class object, as described by the object.describe call. This is actual developer_class that was updated.
Examples
A Sample JSON-RPC developer_class.update Request
{
"method":"developer_class.update",
"id":17,
"params":[{
"name":"Test Developer Class",
"description":"This is a new developer class.",
"qps_limit_override_allowed":true,
"rate_limit_override_allowed":true,
"id":518
}]
}
The JSON-RPC Response
{
"result": {
"id":518,
"created":"2012-11-26T19:08:34Z",
"updated":"2012-11-26T19:11:22Z",
"name":"Test Developer Class",
"description":"This is a new developer class.",
"rate_limit_override_allowed":true,
"qps_limit_override_allowed":true,
"block_calls":false,
"object_type":"developer_class"
},
"error":null,"id":17
}
Permissions Required
The user who owns the key used to authenticate the developer_class.update call must be a member of one of the following roles
- Administrator
- Program Manager
- Community Manager
See authentication.
Errors
In addition to the standard json-rpc errors and authentication errors, application.fetch may also return these errors:
HTTP Status Code | JSON-RPC Code | Error Message | Description |
---|---|---|---|
400 | 1000 | Invalid Object | The object could not be created because the object would be invalid. See Validating Fields for details on the format of this error. |
400 | 1001 | Duplicate Object | The object could not be created because an object already exists with the same identifier. |
400 | 1002 | Field "x" is required. | The object could not be created because a required field was not specified. A field marked false for optional was not specified. The error object data will include the name of the missing field. |
500 | 2001 | Create Failed | The object could not be created. This is the error message of last resort for object creation and usually indicates a systems integration failure, invalid internal data, or a transient issue. These errors are logged by Mashery. |
403 | 4200 | This operation is not allowed for the service specified | The service specified does not allow key creation via the API. |
400 | 5000 | Object "type" with "key" of "value" could not be found | The object could not be updated because it could not be found. |