plan_endpoint.create

Description

Create a plan endpoint  Please see Creating Objects for an overview of how the create method works.

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.

Parameters

plan_endpoint

An plan_endpoint object, as described by the object.describe call. If a field in the plan_endpoint object is ommitted, a default value will be used if possible. If extra fields are passed, they will be ignored.

Response

An plan_endpoint object, as described by the object.describe call. This is actual plan_endpoint that was created.

Examples

A Sample JSON-RPC plan_endpoint.create Request

{
    "method":"plan_endpoint.create",
    "id":9,
    "params":[[{"plan":{"id":47},
    "service_definition_endpoint":{"id":8},
    "allow_undefined_methods":true},{"plan":{"id":47},
    "service_definition_endpoint":{"id":9},
    "allow_undefined_methods":false},{"plan":{"id":47},
    "service_definition_endpoint":{"id":10},
    "allow_undefined_methods":true}]]
}

The JSON-RPC Response

{
"result": true,
"error": null,
"id": 1
}

Permissions Required

The user who owns the key used to authenticate the plan_endpoint.create 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, application.fetch may also return these errors: