UpdateSmsSign-阿里云帮助中心

Modifies signatures that failed review or passed review. After modification, the signature is automatically submitted for review and enters the pending review state.

Operation description

For details about the changes between the new operation and the original operation, see Announcement on updating the signature and template operations for SMS.
Supports modifying signatures that failed review and signatures that passed review. Refer to Suggestions for handling SMS review failures and invoke this operation to resubmit the signature for review after modification.
If you need to edit the name of a signature that failed review, this operation does not support it. Access the console to make the change. SMS Service signature console.
Signature information applied through the operation is synchronized to the SMS Service console. For related operations on signatures in the console, see SMS signatures.

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

dysms:UpdateSmsSign

none

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
SignName	string	Yes	The SMS signature that has not passed review. You can view SMS signatures that have not passed review on the Domestic Messages > Signature Management tab in the console. You can also call the QuerySmsSignList operation to view SMS signatures that have not passed review.	阿里云验证码
Remark	string	No	The description of the SMS signature scenario. This is one of the reference items for signature review. The description cannot exceed 200 characters. Note Provide the usage scenarios of your online business, along with the website URL or marketplace download link of your actual business. Provide a complete SMS example that reflects your business scenario. Provide the pass parameter content for variables, and describe in detail the business scenarios and the reason for choosing the variable property. If the signature involves a government or enterprise organization, include the fixed telephone number of that organization. A well-completed application description improves the review efficiency for signatures and templates. Incomplete or non-compliant descriptions may affect the approval of your signature review.	Apply for verification code for login scenario
SignType	integer	No	The signature type. Valid values: 0: Verification code. 1: General (default value). Use the default value General.	1
MoreData	array	No	The additional materials. Upload supporting business documents or business screenshots to help reviewers understand your business details. See Signature application materials and upload the relevant materials.
	string	No	The file information uploaded to OSS. File names must not contain Chinese characters or special characters. For file upload instructions, see Upload files through OSS.	10098689758*****/1234qwe.png
QualificationId	integer	Yes	The ID of the qualification that has passed review. Note Before applying for an SMS signature, apply for a qualification first. You can view the qualification ID on the Qualification Management page.	8563**
ApplySceneContent	string	No	The app store link. If the signature source is "App already live", that is, SignSource is set to 2, enter an app store link that starts with http:// or https:// and make sure the app is already live.	http://www.aliyun.com/
SignSource	integer	Yes	The signature source. Valid values: 0: Full or abbreviated name of an enterprise or institution. (Recommended) 5: Full or abbreviated name of a trademark. 2: Full or abbreviated name of an app. (Not recommended) For detailed descriptions of signature sources, see Signature sources. Valid values: 0 : Full or abbreviated name of an enterprise or institution. 1 : Full or abbreviated name of a website registered with MIIT. 2 : Full or abbreviated name of an app. 3 : Full or abbreviated name of a public account or mini program. 4 : Full or abbreviated name of an e-commerce platform store. 5 : Full or abbreviated name of a trademark.	2
ThirdParty	boolean	No	The signature usage. Valid values: false: Own use (default value). The signature is the enterprise name, website name, or product name verified under this account. true: Third-party use. The signature is the enterprise name, website name, or product name that is not verified under this account. Important If the signature is for own use, select an own-use qualification ID. If the signature is for third-party use, select a third-party qualification ID.	false
AuthorizationLetterId	integer	No	The authorization letter ID. If the signature is for third-party use, the authorization letter ID cannot be empty. Otherwise, the signature review will not pass. The unified social credit code in the authorization letter must match the unified social credit code in the qualification information bound to the signature. Otherwise, signature creation fails.	1000********1234
TrademarkId	integer	No	The trademark entity ID. Note If SignSource is set to 5, you must provide the trademark entity ID. You can obtain the trademark entity ID by calling the CreateSmsTrademark operation.	1000009081***
AppIcpRecordId	integer	No	The APP ICP filing entity ID. Note If SignSource is set to 2, you must provide the filing entity ID. You can obtain the filing entity ID by calling the CreateSmsAppIcpRecord operation.	100001***1234

Response elements

Element	Type	Description	Example
	object
RequestId	string	The ID of the request. It is a unique identifier generated by Alibaba Cloud for the request and can be used to troubleshoot and locate issues.	A90E4451-FED7-49D2-87C8-00700A8C4D1D
Code	string	The request status code. Valid values: OK: The request was successful. For other error codes, see Error code list.	OK
Message	string	The description of the status code.	OK
SignName	string	The name of the modified signature.	Login verification
OrderId	string	The ticket number. Reviewers use this parameter when querying reviews. Provide this ticket number if you need to expedite the review.	2004417****

Examples

Success response

JSON format

{
  "RequestId": "A90E4451-FED7-49D2-87C8-00700A8C4D1D",
  "Code": "OK",
  "Message": "OK",
  "SignName": "Login verification",
  "OrderId": "2004417****"
}

Error codes

HTTP status code	Error code	Error message	Description
400	ForbiddenAction	Access to the account is denied. Please contact the administrator.
400	ParameterMismatch.ThirdParty	The type of signature, whether for personal use or for a third party, should be consistent with the qualifications.	Whether the signature is used by a third party should be consistent with the qualification.
400	SignName.Exists	Sorry, this signature already exists and cannot be applied for again.	Sorry, this signature already exists and cannot be reapplied.
400	InvalidQualification	The qualification should be approved.	Invalid qualification, qualification should be approved.
400	InvalidApplySceneContent	For certain signature sources, the applySceneContent should be an HTTP or HTTPS link.	invalid application scenario, under some signature sources, The application scenario should be an HTTP or HTTPS link.
400	InvalidSignName	The signature cannot contain spaces, special symbols, or all numbers.	The signature cannot contain special characters such as simplified Chinese, English, or spaces other than digits, and cannot be all digits.
400	MissApplySceneContent	In some signature sources, the applySceneContent is required.	Under some signature sources, the application scenario is required.
400	MissingSignName	The signature name cannot be empty.	Signature name cannot be empty
400	SmsAuthorizationLetterNotMatch	Please bind the available authorization letter whose the social credit code is same to the the social credit code of qualification.	Please bind the available authorization letter whose the social credit code is same to the the social credit code of qualification
400	SmsAuthorizationLetterNotExist	Authorization does not belong to the customer.	The authorization letter does not belong to this customer.
400	SmsSignNotAuthorized	the signature is not in the sign scope of the authorization letter.	The signature is not within the scope of the authorization.
400	TrademarkNotExist	The trademark does not exist.	The associated trademark entity does not exist.
400	AppIcpRecordNotExist	The APP-ICP record does not exist.	The associated APP ICP filing entity does not exist.
404	QualificationNotFound	Qualification does not exist.	Qualification does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.