developer.update
This section provides documentation on the v1.0 version of the Mashery API. We will support previously built applications and integration points, but not granting new access keys. These pages are for legacy support purposes. Should you wish to integrate with your Mashery instance, please utilize Mashery API version 2.0.
Description
Updates a developer belonging to a particular Mashery Service Provider.
Authentication
This method requires authentication
| Parameters | Type | Description | Required |
| spkey | string | Service Provider key assigned by Mashery | Yes |
| string |
Select the developer by email address. Either this value or an API key must be defined. | Yes | |
| apikey | string | Select the developer by API key. Either this value or an email address must be defined. | Yes |
| string | Developer's email address | No | |
| status | string | Status of this developer's account. May be one of waiting, active (default), inactive, deleted or disabled. | No |
| first_name | string | Developer's first name | No |
| last_name | string | Developer's last name | No |
| groups | array | List of groups this developer belongs to | No |
| secret | string | Shared secret between Service Provider and Developer. May be used for signing requests. If set to _auto_, a new secret will be automatically generated and returned in the response. | No |
| limits | object | A limits object to specify limits relating to the developer. See definition of developer.setLimits for complete documentation and definition of the available options. | No |
Response
array|object — Success/failure of the call determined by the boolean success property, and the properties stored with the update developer are returned in the properties property.
Examples
A JSON-RPC Request
{
"method": "developer.update",
"params": [{
"spkey": "nzqz4xehpczjrgrjpgbwnskq",
"where": {
"email": "johnqpublic@example.com"
}
"properties": {
"email": "johnqpublic@example.com"
"groups": ["gold"]
}
}],
"id": 18
}
A JSON-RPC Response
{
"result": {
"success": true,
"properties": {
"first_name": "John",
"last_name": "Public",
"email": "johnqpublic@gmail.com",
"groups": ["gold"],
"apikey": "6j3g9msume5w8bfu6tevcggv",
"secret": "fbskfg4e",
"status": "active"
}
},
"error": null,
"id": 18
}
Errors
This method may return one of the following errors:
| Error | Description |
| 4102: Insufficient Privileges | You do not have sufficient privileges to call this method. |
| 400: Bad Request | Your request was incomplete or otherwise invalid. Please review the documentation. |
| 450: Spkey Not In Area | The service requested does not exist in the area specified. |
| 12: Validation Failed | One or more values presented were not acceptable. Please review the documentation. |
| 4006: Developer Invalid Where | The 'where' property of your request was incomplete. The properties 'email' and/or 'apikey' must be specified to perform this operation. |
| 4007: Developer Invalid Where | Unable to find a developer matching the selection criteria. |
| 4008: Update Developer Failed | Could not update developer record. |
| 4009: Update Group Failes | Could not add developer to the specified group. |
| 4010: Update Clear Groups Failed | Could not clear old groups for this developer. |
Docs Navigation
- Support Documentation Portal
- Mashery API Documentation
- Mashery 2.0 API Guide
- Examples
- API Sandbox
- JSON RPC
- Authentication
- API Objects
- Fetching Objects
- Query Language
- Creating Objects
- Updating Objects
- Validating Fields
- Deleting Objects
- Applications
- General Object Methods
- Members
- Packages
- Plans
- Package Keys
- Keys
- Developer Classes
- Services
- Roles
- Mashery 2.0 Reporting API Guide
- Mashery 1.0 API Guide
- Mashery 2.0 API Guide
- Tips and Tricks
- Customizing Your Portal
- API Traffic Manager