REST API Reference for Offline Mediation Controller

Export Node Customization

post

/v1/actions/export

Exports the customization and configuration of a node.

Request

There are no request parameters for this operation.

Supported Media Types

application/json

Root Schema : schema

Type: object

The payload schema to export nodes and Node Managers data to a file.

Show Source

exportNodeChain(required): boolean

The flag indicating whether to export node chain associated with nodes, identifiers for which are mentioned in nodeIDsToExport.

Example: true
fileName: string

The exported data's file name.

Example: export
nodeIDsToExport(required): array nodeIDsToExport

The list of identifiers of the nodes to export.
nodeManagersToExport(required): array nodeManagersToExport

The list of Node Managers to export.

{
    "required":[
        "nodeManagersToExport",
        "exportNodeChain",
        "nodeIDsToExport"
    ],
    "properties":{
        "nodeManagersToExport":{
            "description":"The list of Node Managers to export.",
            "example":[
            ],
            "items":{
                "type":"string"
            },
            "type":"array"
        },
        "exportNodeChain":{
            "description":"The flag indicating whether to export node chain associated with nodes, identifiers for which are mentioned in nodeIDsToExport.",
            "example":true,
            "type":"boolean"
        },
        "nodeIDsToExport":{
            "description":"The list of identifiers of the nodes to export.",
            "items":{
                "type":"string"
            },
            "type":"array"
        },
        "fileName":{
            "description":"The exported data's file name.",
            "example":"export",
            "type":"string"
        }
    },
    "description":"The payload schema to export nodes and Node Managers data to a file.",
    "type":"object"
}

Nested Schema : nodeIDsToExport

Type: array

The list of identifiers of the nodes to export.

Show Source

Array of: string

{
    "description":"The list of identifiers of the nodes to export.",
    "items":{
        "type":"string"
    },
    "type":"array"
}

Nested Schema : nodeManagersToExport

Type: array

The list of Node Managers to export.

Show Source

Array of: string

{
    "description":"The list of Node Managers to export.",
    "example":[
    ],
    "items":{
        "type":"string"
    },
    "type":"array"
}

Response

Supported Media Types

application/octet-stream
application/json

200 Response

The customization was exported successfully.

400 Response

The server cannot process the request due to a client error.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

401 Response

The client does not have the correct privileges.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

403 Response

The request was not authorized.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

404 Response

Requested resource cannot be found.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

405 Response

This method is not allowed.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

409 Response

The request could not be processed due to a conflict with the existing state of the resource.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

500 Response

The system has encountered an internal server error.

Root Schema : Error

Type: object

Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).

Show Source

@type: string

Defines the sub-class entity when sub-classing.
cause: string

Cause of the exception
code(required): string

The application relevant details defined in the API or a common list.
message: string

The details and corrective actions for the error shown to the client user.
reason(required): string

The reason for the error, which is shown to a client user.
referenceError: string (uri)

URI of documentation describing the error
status: string

HTTP Error code extension

{
    "required":[
        "code",
        "reason"
    ],
    "properties":{
        "code":{
            "description":"The application relevant details defined in the API or a common list.",
            "type":"string"
        },
        "reason":{
            "description":"The reason for the error, which is shown to a client user.",
            "type":"string"
        },
        "message":{
            "description":"The details and corrective actions for the error shown to the client user.",
            "type":"string"
        },
        "cause":{
            "description":"Cause of the exception",
            "type":"string"
        },
        "status":{
            "description":"HTTP Error code extension",
            "type":"string"
        },
        "referenceError":{
            "description":"URI of documentation describing the error",
            "format":"uri",
            "type":"string"
        },
        "@type":{
            "description":"Defines the sub-class entity when sub-classing.",
            "type":"string"
        }
    },
    "description":"Used when an API encounters an Error, typically with a HTTP error response-code (3xx, 4xx, 5xx).",
    "type":"object"
}

Examples

The following example shows how to export a node's customization details by submitting a POST request on the REST resource using cURL. For more information about cURL, see Use cURL.

The -d option specifies the file to attach as the request body.

curl -X POST 'http://hostname:port/actions/export' -d @sampleExportCustomization.json

Example of Request Body

The following is an example of the contents of the sampleExportCustomization.json file sent as the request body.

{
  "exportNodeChain": true,
  "fileName": "abc.npl",
  "nodeIDsToExport": [
    "31eoen-otm-lnenf3zn"
  ],
  "nodeManagersToExport": [
    "NMGR-31eoen-otm-lne65v6v"
  ]
}

Example of Response Body

If successful, the response code 200 is displayed and a download link is generated.