[Index]

API Reference for relation/MultiVendorService_Subscriber

Subscriber relation model used for deletion in multi-vendor

Model ref.: relation/MultiVendorService_Subscriber

The full URL would include the host-proxy name: https://[host-proxy].

Variables are enclosed in square brackets.

For a list of available UUIDs and their dot notations:
GET /api/v0/data/HierarchyNode/?format=json

Get the Add form

Task Call URL Parameters Response
Get the GUI Add form. GET /api/relation/MultiVendorService_Subscriber/add/
  • hierarchy=[hierarchy]
  • format=json
The GUI Add form of relation/MultiVendorService_Subscriber as JSON

The API call to the /add/ URL can only be made from a hierarchy that allows the model type to be added. The actions in the response shows the url for the POST API call to create an instance.

Create

Task Call URL Parameters Payload
Create POST /api/relation/MultiVendorService_Subscriber/ hierarchy=[hierarchy]
(For payload specification)

  • Response is a transaction pkid for the create action.
  • Use the GET call to
    tool/Transaction/[trans pkid]
    to inspect the created resource and its instance pkid.
  • Bulk Delete

    Task Call URL Parameters Payload
    Bulk delete [pkid1],[pkid2]... DELETE /api/relation/MultiVendorService_Subscriber/ hierarchy=[hierarchy] {"hrefs":["/api/relation/MultiVendorService_Subscriber/[pkid1]", "/api/relation/MultiVendorService_Subscriber/[pkid2]", ...]}
    • For the instance pkids [pkid1],[pkid2], ... that can be added to the DELETE call (the instance pkids to delete), refer to the List GET call for: relation/MultiVendorService_Subscriber
      GET http://[host-proxy]/api/relation/MultiVendorService_Subscriber/?hierarchy=[hierarchy]&format=json

    Configuration Template

    Task Call URL Parameters Response
    Configuration Template GET /api/relation/MultiVendorService_Subscriber/configuration_template/ hierarchy=[hierarchy]
    • POST call to create the Configuration Template
    • Configuration Template schema

    • Use the returned properties to create the POST payload data for the .
    • For a description of the schema that shows properties to add to the POST payload:
      • The POST call is of the format:
      • POST http://[host-proxy]/api/data/ConfigurationTemplate/?hierarchy=[hierarchy]

    Field Display Policy

    Task Call URL Parameters Response
    Field Display Policy GET /api/relation/MultiVendorService_Subscriber/field_display_policy/ hierarchy=[hierarchy]
    • POST call to create the Field Display Policy
    • Field Display Policy schema

    • Use the returned properties to create the POST payload data for the .
    • For a description of the schema that shows properties to add to the POST payload:
    • The POST call is of the format:
      • POST http://[host-proxy]/api/data/FieldDisplayPolicy/?hierarchy=[hierarchy]

    List

    Task Call URL Parameters Response
    List GET /api/relation/MultiVendorService_Subscriber/
    • hierarchy=[hierarchy]
    • format=json
    • schema=true
    The relation/MultiVendorService_Subscriber schema and all instances as JSON.

    (The list will return 0 to 3 relation/MultiVendorService_Subscriber instances)

    (Show the first instance)

    Instance API Reference

    Modify

    Task Call URL Parameters Payload
    Modify PUT /api/relation/MultiVendorService_Subscriber/[pkid]/ hierarchy=[hierarchy] (For payload specification)

    For Bulk modification, refer to the Bulk Modify section.

    Delete

    Task Call URL Parameters Response
    Delete DELETE /api/relation/MultiVendorService_Subscriber/[pkid]/ hierarchy=[hierarchy]

    Get

    Task Call URL Parameters Response
    Get GET /api/relation/MultiVendorService_Subscriber/[pkid]/ hierarchy=[hierarchy] The relation/MultiVendorService_Subscriber instance with [pkid].