XML to JSON Interceptor Addition (ssd api-management add (plan | api)-interceptor xml-json)

The ssd api-management add (plan | api)-interceptor xml-json command allows you to add an "XML to JSON" interceptor to an API or plan flow on Sensedia API Platform.

You can use the ssd api-management add (plan | api)-interceptor xml-json command or its shortened version ssd apim add (plan | api)-interceptor xml-json.

Usage

The ssd api-management add (plan | api)-interceptor xml-json command can be followed by flags with their corresponding arguments:

ssd api-management add (plan | api)-interceptor xml-json [flags]

If no flag is specified, the interactive mode will be activated.

Below you will find a usage example in the direct mode:

# Adds an "XML to JSON" interceptor to an API or a plan for all of its resources and methods
$ ssd (api-management | apim) add api-interceptor xml-json --api-name "Open Banking" --api-version "1.0.0" --revision 1 --flow INBOUND --force-string
$ ssd (api-management | apim) add plan-interceptor xml-json --plan-name "Plan Name" --flow INBOUND --force-string

# Adds an "XML to JSON" interceptor interactively
$ ssd (api-management | apim) add api-interceptor xml-json
$ ssd (api-management | apim) add plan-interceptor xml-json

Available Flags

The following flags can be used with the ssd (api-management | apim) add (plan | api)-interceptor xml-json command:

Flag

Type

Description

Flags for APIs

-n, --api-name

string

API name to which the interceptor will be added

-s, --revision

string

API revision to which the interceptor will be added

-v, --api-version

string

API version to which the interceptor will be added

Flags for plans

-n, --plan-name

string

Plan name to which the interceptor will be added

Other flags

-f, --flow

string

API or plan flow to which the interceptor will be added (INBOUND or OUTBOUND)

--force-string

Establishes that the values must necessarily be converted into string

-h, --help

Displays help for the command

-m, --method

string

Method (operation) to which the interceptor will be added (Optional). E.g.: POST

-a, --path

string

Operation path to which the interceptor will be added (Optional). E.g.: /users

-p, --position

int

Position of the interceptor in the API or plan flow

-r, --resource

string

Resource name to which the interceptor will be added (Optional)

Global Flags

Flag

Type

Description

-c, --config

string

Configuration file (default: $HOME/.sensedia/config.json)

--profile

string

The configuration profile you want to use (default: "default")

--verbose

Lists all requests made by the command. It is possible to store this information in a TXT file instead of displaying it on the terminal. E.g.: $ ssd (api-management | apim) list apis --verbose 2> log.txt

Thanks for your feedback!

EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]