• Register



Accept a plan specification and clone that plan

NOTE:This method is available when API Packager is turned on for a customer. Please contact Support or your Account Manager if you have any questions about API Packager.


plan id

An integer representing the unique id of the application to delete. You may also pass a json object with a field of id to identify the plan you wish to clone.


An plan object, as described by the object.describe call. This is actual plan that was cloned.


A Sample JSON-RPC plan.clone Request


The JSON-RPC Response

    "name":"Copy of Evaluation",
    "description":"Evaluation Plan, used to understand the API",
    "notes":"Get developers off this plan after 90 days",

Permissions Required

The user who owns the key used to authenticate the plan.clone call must be a member of one of the following roles

  • Administrator
  • API Manager

See authentication.


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.

Docs Navigation