vania-janet/multiturn-rag-retrieval-data huggingface dataset:
-q, --quiet
: Suppress verbose output.

--output FORMAT
: Specify output format. Only 'JSON' is supported.

--api-version
: Version of the access policy API.





 Examples 

Delete policy 140798e2-8ea7db3 of service test:

ibmcloud iam service-policy-delete test 140798e2-8ea7db3

Delete policy 140798e2-8ea7db3 of service ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976:

ibmcloud iam service-policy-delete ServiceId-cb258cb9-8de3-4ac0-9aec-b2b2d27ac976 140798e2-8ea7db3







 ibmcloud iam oauth-tokens 

Retrieve and display the OAuth tokens for the current session:

ibmcloud iam oauth-tokens





 ibmcloud iam roles 

List platform, service-defined, and custom roles:

ibmcloud iam roles [--service SERVICE_NAME --resource-type RESOURCE_TYPE] --source-service SOURCE_SERVICE_NAME]] [--roles ROLE_NAME]



 Command options 

--resource-type
: Resource type of the service. '--service' must be set along with this option.

--roles ROLE_NAME1,ROLE_NAME2...
: Show details of specific roles

--service SERVICE_NAME
: Name of the service. Only list platform-defined roles if not specified.

--source-service
: Name of the service. Only list platform-defined roles if not specified. This option does not support private endpoints.





 Examples 

List platform default access roles and custom roles:

ibmcloud iam roles

List details of platform default access policy roles Administrator, Operator:

ibmcloud iam roles --roles Administrator,Operator
The endpoint to get the current weather data is https://myweatherprovider.mybluemix.net/current?zipcode={zipcode}. Test it out by visiting [https://myweatherprovider.mybluemix.net/current?zipcode=90210](https://myweatherprovider.mybluemix.net/current?zipcode=90210).

![explore-weatherapp-2.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/explore-weatherapp-2.png)
4. Similarly, the endpoint to get today's forecast data is https:// myweatherprovider<span></span>.mybluemix.net/today?zipcode={zipcode}. Test it out by going to [https://myweatherprovider.mybluemix.net/today?zipcode=90210](https://myweatherprovider.mybluemix.net/today?zipcode=90210).

![explore-weatherapp-3.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/explore-weatherapp-3.png)



--------------------





 Add a new OpenAPI spec to create a REST API proxy 



1. Log in to IBM Cloud: [https://cloud.ibm.com](https://cloud.ibm.com).
2. In the IBM Cloud Dashboard, click Cloud Foundry Services. Launch the API Connect service.
3. In API Connect, make sure that the navigation panel is open.
Administering your API Connect Reserved instance 

Use the administration console to manage users and register additional gateways for API Connect V10 Reserved.



 Managing users 

In API Connect, users are grouped into provider organizations. Each provider organization owns a set of assets includeing APIs, products, catalogs, and developer portals. You can create a single provider organization (for example, in a small company) or create multiple provider organizations (for example, different departments in a large company).

In IBM Cloud, user access is managed with the Identity and Access Management (IAM) service. You can define access groups with policies that determine permissions within each provider organization in API Connect, and then you can add members of your company's IBM Cloud to the appropriate access groups, which results in the users becoming members of the provider organization.

For more information on managing users in your Reserved instance, see [Managing users](https://cloud.ibm.com/docs/apiconnect?apiconnect-ri-mng-users).





 Adding and managing gateways 

API Connect uses gateways to manage API traffic. A gateway hosts published APIs and provides the API endpoints used by client applications. Gateways execute API proxy invocations to back-end systems and enforce API policies that manage client identification, security, and rate limiting.

API Connect V10 Reserved deploys with the IBM DataPower API gateway by default. You can deploy additional DataPower gateways for use with your Reserved instance; for example, to distribute API endpoints for different purposes.

For more information on adding gateways to your Reserved instance, see [Adding remote gateways](https://cloud.ibm.com/docs/apiconnect?apiconnect-ri-reg-gwy). For information on managing user access to gateways, see [Managing gateways](https://cloud.ibm.com/docs/apiconnect?apiconnect-ri-mng-gwy).





 Using the toolkit 

The toolkit provides a CLI for working with assets such as APIs and developer portals.
PATCH /v2/settings/policies/<your policy_id> HTTP/1.1
Host: schematics.cloud.ibm.com
Content-Type: application/json
X-ENABLE-POLICIES: true
Authorization: Bearer <auth_token>
{
"name": "policy-1",
"description": "updated Policy for job execution of secured workspaces on agent1",
"resource_group": "Default",
"tags": [
"policy:secured-job"
],
"location": "us-south",
"kind": "agent_assignment_policy",
"target": {
"selector_kind": "ids",
"selector_ids": [
"agent5.13a6"
]
},
"parameter": {
"agent_assignment_policy_parameter": {
"selector_kind": "scoped",
"selector_scope": [
{
"kind": "action",
"tags":
"env:dev",
"k8s"
],
"resource_groups":
"dummy_resource_group"
],
"locations":
"us-south"
]
}
]
}
}
}





 Example to find policies using the API 

POST /v2/settings/policies/search HTTP/1.1
Host: schematics.cloud.ibm.com
Content-Type: application/json
Authorization: Bearer <auth_token>
{
"parameter": {
"kind": "workspace",
"tags": [
"env:dev",
"k8s"
],
"resource_groups": [
"test"
],
"locations": [
"us-south"
]
},
"target": "action"
}







 Next steps
Subnet crn crn:v1:bluemix:public:is:us-south-1:a123456::subnet:0726-ec96c7cd-46f4-4969-9009-7613f8e9e936
Zone name us-south-2
Created 2020-08-27T14:45:42.038-05:00







 Updating subnets for an application load balancer using the API 

The following example illustrates how to use the API to update subnets for an application load balancer.

To update subnets for an application load balancer with the API, perform the following procedure:



1. Set up your [API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentapi-prerequisites-setup).
2. Use the following example to attach a subnet for your application load balancer:

Save the ID and Etag of the load balancer:

export lbId="r134-a3e1f3db-0e98-47ca-9f24-6e1d06dba086"
export Etag="W/cy8hmdd4op0kws5nrta40kmrmnrwodzy4qwwghyuqwq"

curl -H "Authorization: $iam_token" -H "If-Match: $Etag" -X PATCH
"$vpc_api_endpoint/v1/load_balancers/$lbId?version=$api_version&generation=2" -d '{
"subnets": [
{
"id": "0726-ec96c7cd-46f4-4969-9009-7613f8e9e936"
}
]
}'

Sample output:

{
"created_at": "2020-08-24T23:36:22.990359Z",
Prerequisite: You need an IAM bearer token. For more information, see [Retrieving IAM access tokens](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-retrieve-iam-token).

The API endpoint that handles API service keys is https://resource-controller.cloud.ibm.com/v1/resource_keys.

To create a service resource key, enter:

curl -X POST https://resource-controller.cloud.ibm.com/v1/resource_keys -H 'accept: application/json' -H "authorization: Bearer <IAM bearer token>" -H 'content-type: application/json' -d '{"name":"<key name>","source_crn":"<service instance crn>", "parameters":{"role_crn":"<crn of access role>"} }'

Sample response:

{
"id": "crn:v1:staging:public:ibmanalyticsengine:us-south:a/d628eae2cxxxxx229f2xxxx:79c757e9-xxxx-xxxx-xxxx-dff7f01xxxx:resource-key:2278xxxx-xxxx-xxxx-xxxx-59a6da6xxxxe",
"guid": "2278xxxx-xxxx-xxxx-xxxx-59a6da68xxxx",
"url": "/v1/resource_keys/crn%3Av1%3Astaging%3Apublic%3Aibmanalyticsengine%3Aus-south%3Aa%2Fd628eae2cxxxxx229f2xxxx%3A79c757e9-xxxx-xxxx-xxxx-dff7f01xxxx%3Aresource-key%3A2278xxxx-xxxx-xxxx-xxxx-59a6da6xxxxe",
[New API](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/newapi-menu2.png)
7. The New API from WSDL dialog box opens. Click Upload File. ![Upload the .wsdl file](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/4-uploadwsdl.png)
8. Select the weatherprovider.wsdl file that you saved previously.
9. The New API from WSDL dialog box reappears. Check the weatherService check box. Click Done. ![Select weather service](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/newapi2.png)
10. The Design view of the API opens. ![API Editor page](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/designpage2.png)
11. Click ![Save](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/save.png) icon to save your changes. An "API Saved" confirmation notification appears momentarily.
12.
fetch('https://api.coinbase.com/v2/prices/BTC-USD/spot', init),
fetch('https://api.coinbase.com/v2/prices/ETH-USD/spot', init),
fetch('https://api.coinbase.com/v2/prices/LTC-USD/spot', init)
])

const btc = await btcResp.json()
const eth = await ethResp.json()
const ltc = await ltcResp.json()

let combined = {}
combined['btc'] = btc['data'].amount
combined['ltc'] = ltc['data'].amount
combined['eth'] = eth['data'].amount

const responseInit = {
headers: {'Content-Type': 'application/json'}
}
return new Response(JSON.stringify(combined), responseInit)
}
Show more





 Conditional routing 

The easiest way to deliver different content based on the device being used is to rewrite the URL of the request based on the condition you care about. For example:



 Device type 

addEventListener('fetch', event => {
event.respondWith(fetchAndApply(event.request))
})

async function fetchAndApply(request) {
let uaSuffix = ''

const ua = request.headers.get('user-agent')
if (ua.match(/iphone/i) || ua.match(/ipod/i)) {
uaSuffix = '/mobile'
} else if (ua.match(/ipad/i)) {
uaSuffix = '/tablet'
}

return fetch(request.url + uaSuffix, request)
}
Show more







 Hot-link protection
* [Global Tagging Attach](https://cloud.ibm.com/apidocs/taggingattach-tag) and [Detach](https://cloud.ibm.com/apidocs/taggingdetach-tag) APIs
* [Context-based Restriction Rule APIs](https://cloud.ibm.com/apidocs/context-based-restrictionscreate-rule)
* [Secrets Manager APIs](https://cloud.ibm.com/apidocs/secrets-manager)







 Creating network zones 

A network zone represents an allowlist of IP addresses where an access request is created. It defines a set of one or more network locations with the following attributes:



* IP addresses, which include individual addresses, ranges, or subnets.
* VPCs
* Service references, which allow access from other IBM Cloud services.



Make sure to add Security and Compliance Center to network zones for rules that target other IBM Cloud resources, or some operations in your workflow might fail.



 Creating network zones in the console 

To create network zones in the UI, complete the following steps.



1. Determine the resources that you want add to your allowlist.
2. Follow the steps to [create network zones in the console](https://cloud.ibm.com/docs/account?topic=account-context-restrictions-create). Add the Security and Compliance Center service to your network zones to allow Security and Compliance Center to access services and resources that are in your account.







 Creating network zones by using the API 

You can create network zones by using the create-zone command. For more information, see the [API docs](https://cloud.ibm.com/apidocs/context-based-restrictionscreate-zone). You can add Security and Compliance Center to network zones as a service reference to allow Security and Compliance Center to access resources and services in your account that are the subject of a rule.

The serviceRef attribute for Security and Compliance Center is compliance.

Example payload to add Security and Compliance Center to a network zone.

{
"name": "Example zone 1",
"description": "",
Response<ResourceKey> response = service.getResourceKey(getResourceKeyOptions).execute();
ResourceKey resourceKey = response.getResult();

System.out.printf("getResourceKey() response:n%sn", resourceKey.toString());

resource_key = resource_controller_service.get_resource_key(
id=instance_key_guid
).get_result()

print('nget_resource_key() response:n',
json.dumps(resource_key, indent=2))

getResourceKeyOptions := resourceControllerService.NewGetResourceKeyOptions(
instanceKeyGUID,
)

resourceKey, response, err := resourceControllerService.GetResourceKey(getResourceKeyOptions)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(resourceKey, "", " ")
fmt.Printf("nGetResourceKey() response:n%sn", string(b))

const params = {
id: instanceKeyGuid,
};

resourceControllerService.getResourceKey(params)
.then(res => {
console.log('getResourceKey() response:n' + JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});
3. Use the API key that is displayed as the credentials to connect to the service instance.







 Services with service keys 

The following services provide service keys for you to use externally:



* Alert Notification
* Analytics for Apache Spark
* Blockchain
* Discovery
* Event Streams
* Geospatial Analytics
* Globalization Pipeline
* IBM® App Connect
* IBM Cloudant
* Language Translator
In the list of Operations, select post /weatherRequest.
![Post a request](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/13-selectoperation.png)
8. Enter the following xml in the body field. You can select and copy the following example XML, then click the body field to activate the field and paste the example XML.

<?xml version="1.0" encoding="UTF-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<wdata:WeatherRequest xmlns:wdata="http://www.ibm.com/wdata">
<zipcode>10504</zipcode>
</wdata:WeatherRequest>
</soap:Body>
</soap:Envelope>

![The request](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/14-enterrequest.png)
9. Click Invoke. The API returns a Response body that contains information about the current weather.
![15-success.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/15-success.png)







 Conclusion 

In this tutorial, you completed the following tasks:
Superseding API Products 

Duration: 15 mins
Skill level: Beginner



 Objective 

In this tutorial, you will supersede an existing API with a new one in API Connect V5.





 Prerequisites 



1. [Set up your IBM® API Connect for IBM Cloud® instance](https://cloud.ibm.com/docs/apiconnect/tutorials?topic=apiconnect-tut_prereq_set_up_apic_instance).
2. Complete the [Replace an API product tutorial](https://cloud.ibm.com/docs/apiconnect/tutorials?topic=apiconnect-tut_manage_replace).







 Superceding an API Product 



1. Log in to IBM Cloud: [https://cloud.ibm.com](https://cloud.ibm.com).
2. In the IBM Cloud Dashboard, click Cloud Foundry Services. Launch the API Connect service.
3. In API Connect, make sure the navigation panel is open. If not, click >> to open it.



![cloud-apic-dashboard.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/cloud-apic-dashboard.png)



4. Click Drafts > APIs.
5. In the APIs panel, click Weather Provider API to open the REST proxy API.
![rep-api-list.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/rep-api-list.png)
6. Change the Version to 3.0.0.
7. Click the disk icon to save the API changes.
Discovering APIs 

Duration: 25 mins
Skill level: Beginner



 Objective 

In this tutorial, you will learn how a portal user might consume the APIs in the IBM® API Connect for IBM Cloud® V5 Developer Portal. You will gain an understanding of how a portal user would explore products and APIs, view and test APIs, and subscribe to APIs.





 Prerequisite 

There is no prerequisite for this tutorial. As a portal administrator, you can also complete this tutorial while you navigate your developer portal to experience how your portal users navigate your developer portal. Keep in mind that all developer portals have different skins.

If you do not have an existing developer portal, you can set up and configure a developer portal in IBM Cloud before proceeding with this tutorial.





 Explore Products & APIs 

This section shows how a portal user would explore the products and APIs in the developer portal.



1. In a browser, navigate to your API Connect Developer Portal. ![API Connect Developer Portal](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/11-developer-portal.png)
2. In the API Connect Developer Portal, select the API Products tab. ![API Products](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/12-API-products.png)
3. Select one of the available API products to display the available APIs and Plans for the product.
![Select Product](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/13-product.png)
4.
Attaching subnets to a routing table with the API 

To attach subnets to a routing table by using the API, follow these steps:



1. Set up your [API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentapi-prerequisites-setup).
2. Store the VpcId value in a variable to be used in the API command:

export VpcId=<your_vpc_id>
3. Attach a subnet to a routing table:

curl -X PUT "$vpc_api_endpoint/v1/subnets/$subnet_id/routing_table?version=$api_version&generation=2"
-H "Authorization: $iam_token"
-d '{
"id": "37491549-51c0-4acc-9e7b-9ab3628e1a68"
}'
"href": "https://us-south.iaas.cloud.ibm.com/v1/subnets/35984145-9c3a-4626-8ee7-52c7a8742752",
"id": "35984145-9c3a-4626-8ee7-52c7a8742752",
"name": "my-subnet",
"resource_type": "subnet"
},
"transit_encryption": "none",
"virtual_network_interface": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/virtual_network_interfaces/388f01db-41bb-42aa-b5cd-34ba41288d47",
"id": "388f01db-41bb-42aa-b5cd-34ba41288d47",
"name": "my-virtual-network-interface",
"resource_type": "virtual_network_interface"
},
"vpc": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/4c0bb0df-5ca2-43ca-a3de-a4f86010a906",
"id": "4c0bb0df-5ca2-43ca-a3de-a4f86010a906",
"name": "my-vpc",
"resource_type": "vpc"
}
}
],
"total_count": 1
}





 View a single mount target with the API 

Make a GET /shares/{share_id}/mount_targets/{mount_target_id} request to information of a single mount target of a file share.
Listing snapshots with the API 

You can list your snapshots by using the API.



 Listing all snapshots with the API 

With the [VPC API](https://cloud.ibm.com/apidocs/vpc), make a GET/snapshots request to list all snapshots of your volumes. By default, the list shows the most recent snapshots first, followed by older snapshots in descending order.

curl -X GET "$vpc_api_endpoint/v1/snapshots?version=2022-12-16&generation=2" -H "Authorization: $iam_token"

You can filter the list by using the resource group ID, source volume ID, or source volume CRN, and further filter the results by using the following options:



* Limit - To control the number of snapshots displayed on a page.
* Start - To specify which snapshot (by ID) to start the list.
* Sort - To control the order in which you sort the page, such as by date created or alphabetically by snapshot name.



For more information, see the [VPC API reference](https://cloud.ibm.com/apidocs/vpc).

For example, the following call filters the list to show snapshots that were created for a single volume and limits the results to five per page.

curl -X GET "$vpc_api_endpoint/v1/snapshots?version=2022-08-16&generation=2" -H "Authorization: $iam_token" -d '{
"limit": 50,
"source_volume":
"id": "8948ad59-bc0f-7510-812f-5dc64f59fab8"
}'

A successful response looks like the following example.

{
"first": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/snapshots?limit=50"
},
"limit": 50,
"snapshots": [
{
"bootable": true,
Creating a network ACL with the API 

To create a network ACL by using the API, follow these steps:



1. Set up your [API environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentapi-prerequisites-setup).
2. Store the VpcId value in a variable to be used in the API command:

export VpcId=<your_vpc_id>
3. Create a network ACL:

curl -X POST -sH "Authorization:${iam_token}" "$vpc_api_endpoint/v1/network_acls?version=$api_version&generation=2" -d '{"name": "testacl", "vpc":{"id": "'$VpcId'"},"resource_group": {"id": "'$ResourceGroupId'"}}' | jq







 Example: Configuring rules 

For example, you can configure the following inbound rules:



* Allow HTTP traffic from the internet.
* Allow all inbound traffic from the subnet 10.10.20.0/24.
* Deny all other inbound traffic.





Table 1. Information for configuring inbound rules.

 Priority Allow/Deny Protocol Source Destination 

 1 Allow TCP Any IP, ports 80 - 80 Any IP, any port 
 2 Allow ALL 10.10.20.0/24, any port Any IP, any port 
 3 Deny ALL Any IP, any port Any IP, any port 



Then, configure the following outbound rules:



* Allow HTTP traffic to the internet.
* Allow all outbound traffic to the subnet 10.10.20.0/24.
* Deny all other outbound traffic.





Table 2. Information for configuring outbound rules.

 Priority Allow/Deny Protocol Source Destination 

 1 Allow TCP Any IP, any port Any IP, ports 80 - 80 
 2 Allow ALL Any IP, any port 10.10.20.0/24, any port
-d 'grant_type=urn%3Aibm%3Aparams%3Aoauth%3Agrant-type%3Aapikey&apikey=<API_KEY>' > token.json

Replace <API_KEY> with your API key.

The following truncated example shows the contents of the token.json file:

{
"access_token": "b3VyIGZhdGhlc...",
"expiration": 1512161390,
"expires_in": 3600,
"refresh_token": "dGhpcyBjb250a...",
"token_type": "Bearer"
}

Use the full access_token value, prefixed by the Bearer token type.
"enrollsecret": "password",
"admincerts":
"LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCkFkbWluIGNlcnQgZGF0YSB3b3VsZCBiZSBoZXJlIGlmIHRoaXMgd2FzIHJlYWwKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo="
]
},
"tls": {
"cahost": "n3a3ec3-myca.ibp.us-south.containers.appdomain.cloud",
"caport": "7054",
"caname": "tlsca",
"catls": {
"cacert": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCkNlcnQgZGF0YSB3b3VsZCBiZSBoZXJlIGlmIHRoaXMgd2FzIHJlYWwKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo"
},
"enrollid": "admin",
"enrollsecret": "password",
"admincerts":
"LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCkFkbWluIGNlcnQgZGF0YSB3b3VsZCBiZSBoZXJlIGlmIHRoaXMgd2FzIHJlYWwKLS0tLS1FTkQgQ0VSVElGSUNBVEUtLS0tLQo="
] ! ! ! !
}
}
},
"hsm": {
"pkcs11endpoint": "tcp://example.com:666",
},
"config_override": {
"bccsp": {
"default": "PKCS11",
"pkcs11": {
"label": "blockchain",
"pin": "91927001"
}
}
}
}"
Show more
<-- </section "id="section-deploy-a-node-that-uses-an-hsm" "> --><-- </section "id="section-ibp-v2-apis-custom" "> --><-- <section "id="section-ibp-v2-apis-import-with-apis" "> --> Import a network by using APIs You can also use the APIs to import IBM Blockchain components that are created by using the APIs or the IBM Blockchain Platform console into another service instance of the IBM Blockchain Platform.<-- <ol> -->1. Import a CA by calling POST /ak/api/v2/components/ca]POST _ak_api_v2_components_ca] .