TXT to JSON Interceptor Addition (ssd api-management add (plan | api)-interceptor txt-json)
The ssd api-management add (plan | api)-interceptor txt-json
command allows you to add a "TXT to JSON" interceptor to an API or plan flow on Sensedia API Platform.
You can use the ssd api-management add (plan | api)-interceptor txt-json command or its shortened version ssd apim add (plan | api)-interceptor txt-json .
|
Usage
The ssd api-management add (plan | api)-interceptor txt-json
command can be followed by flags with their corresponding arguments:
ssd api-management add (plan | api)-interceptor txt-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 a "TXT to JSON" interceptor to an API or a plan for all of its resources and methods $ ssd (api-management | apim) add api-interceptor txt-json --api-name "Open Banking" --api-version "1.0.0" --revision 1 --flow INBOUND $ ssd (api-management | apim) add plan-interceptor txt-json --plan-name "Plan Name" --flow INBOUND # Adds a "TXT to JSON" interceptor interactively $ ssd (api-management | apim) add api-interceptor txt-json $ ssd (api-management | apim) add plan-interceptor txt-json
Available Flags
The following flags can be used with the ssd (api-management | apim) add (plan | api)-interceptor txt-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) |
-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: |
--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.: |
Share your suggestions with us!
Click here and then [+ Submit idea]