All Products
Search
Document Center

Data Management:CreateOrder

Last Updated:Aug 17, 2026

Creates a ticket.

Operation description

To simplify ticket creation, if you need to create the following types of tickets, call the dedicated operations:

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

dms:CreateOrder

create

*All Resource

*

None None

Request parameters

Parameter

Type

Required

Description

Example

Tid

integer

No

The tenant ID. You can call the GetUserActiveTenant or ListUserTenants operation to obtain this parameter.

3***

Comment

string

Yes

The description of the ticket.

test

PluginParam

object

Yes

The parameters for creating the ticket. The value is a JSON string. The parameters vary based on the ticket type. For more information, see Supplementary description of PluginParam below the table.

{PluginParam_test}

RelatedUserList

string

No

The IDs of the stakeholders of the ticket. Separate multiple IDs with commas (,).

user1,user2

PluginType

string

Yes

The ticket type. For valid values, see PluginType parameter description.

DATA_EXPORT

AttachmentKey

string

No

The key of the attachment that is returned after the attachment is uploaded. You can call the GetUserUploadFileJob operation to obtain this parameter.

test_AttachmentKey

RealLoginUserUid

string

No

No

Supplementary description of PluginParam

# Schema design
 {
    "title": "test", // Title
    "description": "test", // Description
    "dbId": 11****, // Baseline database
    "logic": false, // Specifies whether the database is a logical database
    "relatedIds": [], // User IDs of change stakeholders
  }

# Data export
 {
  "classify": "Reason category", // Reason category
  "dbId": 17****, // ID of the database to export
  "exeSQL": "select 1", // Export SQL statement
  "logic": false, // Specifies whether the database is a logical database
  "ignoreAffectRows": false, // Specifies whether to skip the affected rows check
  "affectRows": 1, // Estimated number of affected rows
  "ignoreAffectRowsReason": "" // Reason for skipping the affected rows check
 }

# Permission ticket
{
	"seconds": xxx, // Permission duration, in seconds
	"permType": xx, // Permission type: 1-Query, 2-Export, 4-Change. To apply for multiple permission types, add the values together. For example, the value for query and export permissions is 3.
	"resources": [{
		"dbId": xxx, // Database ID
		"instanceId": xxx // Instance ID
		"logic": xxx // Specifies whether the database is a logical database
		"tableName": xxx // Table name
		"tableId": xxx // Table ID
		"columnName": xxx // Column name
	}],
	"type": "xx" // INSTANT, DB, or TABLE
}

Response elements

Element

Type

Description

Example

object

CreateOrderResult

object

OrderIds

array

The information about the tickets that are created.

integer

The ticket ID.

12***

RequestId

string

The request ID.

427688B8-ADFB-4C4E-9D45-EF5C1FD6****

ErrorCode

string

The error code.

UnknownError

ErrorMessage

string

The error message.

UnknownError

Success

boolean

Indicates whether the request is successful. Valid values:

  • true: The request is successful.

  • false: The request fails.

true

Examples

Success response

JSON format

{
  "CreateOrderResult": {
    "OrderIds": [
      0
    ]
  },
  "RequestId": "427688B8-ADFB-4C4E-9D45-EF5C1FD6****",
  "ErrorCode": "UnknownError",
  "ErrorMessage": "UnknownError",
  "Success": true
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.