OnlineFlowVersion - Chat App Message Service - Alibaba Cloud ドキュメントセンター

Operation description

You can call this operation to publish a flow version. You can also click a flow name on the Flow Editor page to go to the canvas orchestration page and manually publish a flow version.
Before calling this operation, make sure that you have a successfully created flow and that your flow is bindded to a phone number or merchant account ID.
If you do not have a successfully created flow, you can manually create a flow and bindded it to a phone number or merchant account ID on the Flow Editor page, or call the CreateChatFlow and FlowBindPhone operations to create a flow and bind it to a phone number or merchant account ID.
After a flow with a non-manual trigger type is published, the flow is triggered when the bound phone number or merchant account sends a message to the merchant. If your flow contains components that incur fees for corresponding cloud services, such as message sending or function calling, make sure that you fully understand the billing methods and pricing of the related services before using this operation.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

cams:OnlineFlowVersion

update

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
FlowCode	string	No	The flow code. You can view the flow code on the Flow Editor page.	f4912c16943b4dfba44bd6fedacf****
FlowVersion	string	No	The flow version. You can click a flow name on the Flow Editor page to go to the canvas page and view the flow version.	1
Remark	string	No	The flow remark. You can view the flow remark on the Flow Editor page.	Trigger verification template delivery through API.
BizCode	string	No	The business tenant code. Default value: ALICOM_OPAAS. Valid values: ALICOM_OPAAS : ALICOM_OPAAS	ALICOM_OPAAS
BizExtend	object	No	The business extension information. Default value: an empty collection.	{}

Response elements

Element	Type	Description	Example
	object
Response	object	The response content.
AccessDeniedDetail	string	The access denied details.	None
RequestId	string	The request ID.	90E63D28-E31D-1EB2-8939-A94866411B2O
Message	string	The error message.	None
Code	string	The status code.	OK
Success	boolean	Indicates whether the operation was successful. Valid values: true: Successful. false: Failed.	true

Examples

Success response

JSON format

{
  "Response": {
    "test": "test",
    "test2": 1
  },
  "AccessDeniedDetail": "None",
  "RequestId": "90E63D28-E31D-1EB2-8939-A94866411B2O",
  "Message": "None",
  "Code": "OK",
  "Success": true
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.