[Index]

API Reference for relation/SubscriberDeviceProfile

Extension Mobility based relation.

Model ref.: relation/SubscriberDeviceProfile

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/SubscriberDeviceProfile/add/
  • hierarchy=[hierarchy]
  • format=json
 The GUI Add form of relation/SubscriberDeviceProfile 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/SubscriberDeviceProfile 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/SubscriberDeviceProfile/ hierarchy=[hierarchy] {"hrefs":["/api/relation/SubscriberDeviceProfile/[pkid1]", "/api/relation/SubscriberDeviceProfile/[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/SubscriberDeviceProfile 
      GET http://[host-proxy]/api/relation/SubscriberDeviceProfile/?hierarchy=[hierarchy]&format=json

    Move

    Task Call URL Parameters Payload
    Move the instance with [pkid] to [target_hierarchy] POST /api/tool/DataMove/?model_type=relation/SubscriberDeviceProfile
    • hierarchy=[hierarchy]
    • context_hierarchy=[target_hierarchy]
    • format=json
    • (nowait=true)
    		 {"hrefs": ["/api/relation/SubscriberDeviceProfile/[pkid]"]}
    Bulk Move POST /api/tool/DataMove/?model_type=relation/SubscriberDeviceProfile
    • hierarchy==[hierarchy]
    • context_hierarchy=[target_hierarchy]
    • format=json
    • (nowait=true)
    		 {"hrefs": ["/api/relation/SubscriberDeviceProfile/[pkid1]", "/api/relation/SubscriberDeviceProfile/[pkid2]",...]}

    • Move one or more model instances ([pkid1],[pkid2],...) from source hierarchy (pkid or dot notation) to target_hierarchy (pkid or dot notation). A move can only take place from a source hierarchy equal to or lower than target_hierarchy.
    • For a list of hierarchy pkids and their dot notation available from [hierarchy], use the GET call:
      GET http://[host-proxy]/api/relation/SubscriberDeviceProfile/?hierarchy=[hierarchy]&format=json&schema_rules=true

    Bulk Export

    Task Call URL Parameters Payload
    Get a selected [export_format] of the schema and instances [pkid1], [pkid2],... of relation/SubscriberDeviceProfile; optionally with tag_version at [version] and Configuration Template as [configtemplate]. POST /api/relation/SubscriberDeviceProfile/export/
    • hierarchy=[hierarchy]
    • version=[version]
    • schema=
    • schema_rules=
    • template_name=[configtemplate]
    • export_format=[raw_xlsx|xlsx|json]
    		 { "hrefs":["/api/relation/SubscriberDeviceProfile/[pkid1]", "/api/relation/SubscriberDeviceProfile/[pkid2]",...]}}

    For export_format=json, the response is a time stamped zip file of data in JSON as in the system database. Item properties such as strings that are empty or Boolean values that are not set, are not included. The filename in the response is of the format as the example:

            Content-Disposition: attachment; filename=export_2013-05-17_14:20:19.186444.json.zip
        Content-Language:en
        Content-Type:application/x-zip

    For export_format=raw_xlsx, the response is a MS Excel spreadsheet with columns corresponding to the JSON format export and a response filename format:

            Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_CCYY-MM-DD_HH-MM-SS.xlsx
        Content-Language:en
        Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    For export_format=xlsx, the response is a MS Excel spreadsheet, arranged by any Field Display Policies that apply. The columns correspond with those of a Bulk Load Template export sheet. The response filename format is:

            Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_formatted_CCYY-MM-DD_HH-MM-SS.xlsx
        Content-Language:en
        Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    The XLSX format can be used to bulk load instances of relation/SubscriberDeviceProfile and the JSON format can be used to import instances of relation/SubscriberDeviceProfile.

    • To get the list of all instance pkids [pkid1],[pkid2], ..., use the List GET call for relation/SubscriberDeviceProfile: 
    •  GET http://[host-proxy]/api/relation/SubscriberDeviceProfile/?hierarchy=[hierarchy]

    Export Bulk Load Template

    Task Call URL Parameters Response
    Get a compressed format of the Bulk Load spreadsheet template for relation/SubscriberDeviceProfile POST /api/relation/SubscriberDeviceProfile/export_bulkload_template/
    • hierarchy=[hierarchy]
    • modeltype=relation/SubscriberDeviceProfile
    		 The response is an attachment of the format: filetype_bulkloadsheet.xlsx.gz

    Configuration Template

    Task Call URL Parameters Response
    Configuration Template GET /api/relation/SubscriberDeviceProfile/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/SubscriberDeviceProfile/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/SubscriberDeviceProfile/
    • hierarchy=[hierarchy]
    • format=json
    • schema=true
    		 The relation/SubscriberDeviceProfile schema and all instances as JSON.

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

    (Show the first instance)

    Help

    Task Call URL Parameters Response
    Get the on-line Help for relation/SubscriberDeviceProfile. GET /api/relation/SubscriberDeviceProfile/help hierarchy=[hierarchy] On-line help of Model ref.: relation/SubscriberDeviceProfile as HTML

    Instance API Reference

    Modify

    Task Call URL Parameters Payload
    Modify PUT /api/relation/SubscriberDeviceProfile/[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/SubscriberDeviceProfile/[pkid] hierarchy=[hierarchy]

    Move

    Task Call URL Parameters Payload
    Move POST /api/tool/DataMove/[pkid]/?model_type=relation/SubscriberDeviceProfile hierarchy=[hierarchy] If payload required:

    Export

    Task Call URL Parameters Response
    Get a selected [export_format] of the schema and a single instance with [pkid] of relation/SubscriberDeviceProfile; optionally with tag_version at [version] and Configuration Template as [configtemplate]. GET /api/relation/SubscriberDeviceProfile/[pkid]/export
    • hierarchy=[hierarchy]
    • version=[version]
    • schema=
    • schema_rules=
    • template_name=[configtemplate]
    • export_format=[raw_xlsx|xlsx|json]
    		 The response is an attachment. Refer to the list below.

    For export_format=raw_xlsx, the response is a "raw" MS Excel spreadsheet with columns corresponding to the JSON format export and a response format:

            Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_CCYY-MM-DD_HH-MM-SS.xlsx
        Content-Language:en
        Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    For export_format=xlsx, the response is a MS Excel spreadsheet, formatted to show all columns and a response format:

            Content-Disposition: attachment; filename=<resource_type>_<resource_name>_exportedsheet_formatted_CCYY-MM-DD_HH-MM-SS.xlsx
        Content-Language:en
        Content-Type:application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

    For export_format=json, the response is a time stamped zip file of data in JSON and a response format:

            Content-Disposition: attachment; filename=export_2013-05-17_14:20:19.186444.json.zip
        Content-Language:en
        Content-Type:application/x-zip

    The XLSX format can be used to bulk load instances of relation/SubscriberDeviceProfile and the JSON format can be used to import instances of relation/SubscriberDeviceProfile.

    For Bulk Export, refer to the Bulk Export section.

    Get

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

    Help

    Task Call URL Parameters Response
    Help GET /api/relation/SubscriberDeviceProfile/[pkid]/help hierarchy=[hierarchy] The on-line Help for relation/SubscriberDeviceProfile.