service.fetch
Description
Fetch a single service object. Please see Fetching Objects for an overview of how the fetch method works.
Parameters
service key
A string representing the unique id of the service to fetch. You may also pass a json object with a field of service_key to identify the service you wish to fetch.
Response
An service object, as described by the object.describe call. NULL is returned if the member could not be found.
Examples
A Sample JSON-RPC Service Fetch Request
{ "method": "service.fetch", "params": [1001], "id": 1 }
The JSON-RPC Response
{ "result": { /* Service Object Here */ }, "error": null, "id": 1 }
Permissions Required
The user who owns the key used to authenticate the service.fetch call must be a member of one of the following roles
- Administrator
- Api Manager
See authentication.
Errors
In addition to the standard json-rpc errors and authentication errors, service.fetch may also return these errors:
HTTP Status Code | JSON-RPC Code | Error Message | Description |
---|---|---|---|
400 | 1002 | Field "service_key" is required | You've passed an object to trigger the alternative object identifier syntax, but that object does not contain a service_key field. |
Docs Navigation
- API Documentation Portal
- IO Docs Definition
- Mashery API Documentation
- Mashery 3.0 API Guide
- Mashery 2.0 API Guide
- OAuth Supporting Methods
- Examples
- 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
- Event Trigger API
- Differences between Roles and Portal Access Groups
- Managing a Portal Access Group Using Mashery V2 or V3 API
- Mashery Reporting Event Post API Guide
- Tips and Tricks
- Your Portal
- API Traffic Manager
- I/O Docs WSDL requirements