CreateSmsSignRequest.Builder (alibabacloud-dysmsapi20170525 4.0.8 API)

java.lang.Object
- com.aliyun.sdk.service.dysmsapi20170525.models.CreateSmsSignRequest.Builder

所有已实现的接口:

darabonba.core.RequestModel.Builder<CreateSmsSignRequest,CreateSmsSignRequest.Builder>

封闭类:

CreateSmsSignRequest
```
public static final class CreateSmsSignRequest.Builder
extends Object
```

方法概要

所有方法实例方法具体方法
限定符和类型	方法和说明
`CreateSmsSignRequest.Builder`	`appIcpRecordId(Long appIcpRecordId)` AppIcpRecordId.
`CreateSmsSignRequest.Builder`	`applySceneContent(String applySceneContent)` Application scenarios, instructions as follows: For registered websites, enter the domain name with HTTP or HTTPS that has been registered with the MIIT.
`CreateSmsSignRequest.Builder`	`authorizationLetterId(Long authorizationLetterId)` AuthorizationLetterId.
`CreateSmsSignRequest`	`build()`
`CreateSmsSignRequest.Builder`	`moreData(List<String> moreData)` Additional information to supplement uploaded business proof documents or screenshots, which helps reviewers understand your business details.
`CreateSmsSignRequest.Builder`	`ownerId(Long ownerId)` OwnerId.
`CreateSmsSignRequest.Builder`	`qualificationId(Long qualificationId)` Approved or under-review qualification ID.
`CreateSmsSignRequest.Builder`	`remark(String remark)` Explanation of the SMS signature scenario, with a maximum length of 200 characters.
`CreateSmsSignRequest.Builder`	`resourceOwnerAccount(String resourceOwnerAccount)` ResourceOwnerAccount.
`CreateSmsSignRequest.Builder`	`resourceOwnerId(Long resourceOwnerId)` ResourceOwnerId.
`CreateSmsSignRequest.Builder`	`signName(String signName)` Signature name.
`CreateSmsSignRequest.Builder`	`signSource(Integer signSource)` Signature source.
`CreateSmsSignRequest.Builder`	`signType(Integer signType)` Signature type.
`CreateSmsSignRequest.Builder`	`thirdParty(Boolean thirdParty)` Choose whether the applied signature is for self-use or third-party use.
`CreateSmsSignRequest.Builder`	`trademarkId(Long trademarkId)` TrademarkId.

从类继承的方法 java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- 方法详细资料
  - appIcpRecordId
```
public CreateSmsSignRequest.Builder appIcpRecordId(Long appIcpRecordId)
```
    AppIcpRecordId.
  - applySceneContent
```
public CreateSmsSignRequest.Builder applySceneContent(String applySceneContent)
```
    Application scenarios, instructions as follows:
    - For registered websites, enter the domain name with HTTP or HTTPS that has been registered with the MIIT.
    - For launched apps, provide a display link from the app store with HTTP or HTTPS, ensuring the app is online.
    - For public accounts or mini-programs, input the full name, ensuring they are online.
    - For e-commerce platform store names, applicable only to enterprise users, provide a display link with HTTP or HTTPS for the store.
    example:
    http://www.aliyun.com/
  - authorizationLetterId
```
public CreateSmsSignRequest.Builder authorizationLetterId(Long authorizationLetterId)
```
    AuthorizationLetterId.
  - moreData
```
public CreateSmsSignRequest.Builder moreData(List<String> moreData)
```
    Additional information to supplement uploaded business proof documents or screenshots, which helps reviewers understand your business details.
    
    This parameter is optional; please fill it out based on your actual needs.
  - ownerId
```
public CreateSmsSignRequest.Builder ownerId(Long ownerId)
```
    OwnerId.
  - qualificationId
```
public CreateSmsSignRequest.Builder qualificationId(Long qualificationId)
```
    Approved or under-review qualification ID.
    Before applying for an SMS signature, please first Apply for Qualification.
    
    You can view the qualification ID on the Qualification Management page.
    This parameter is required.
    example:
    8563**
  - remark
```
public CreateSmsSignRequest.Builder remark(String remark)
```
    Explanation of the SMS signature scenario, with a maximum length of 200 characters.
    
    The scenario explanation is one of the reference materials for signature review. Please provide a detailed description of the usage scenarios for your live services, along with links to verify these services such as website URLs with MIIT备案, app store display links, full names of public accounts or mini-programs, etc. For login scenarios, test account credentials are also required. A comprehensive application explanation enhances the efficiency of signature and template reviews. Refer to the Application Scenario column in the Signature Source table for filling in SMS scenarios.
    
    example:
    SMS signature for the login scenario using verification code.
  - resourceOwnerAccount
```
public CreateSmsSignRequest.Builder resourceOwnerAccount(String resourceOwnerAccount)
```
    ResourceOwnerAccount.
  - resourceOwnerId
```
public CreateSmsSignRequest.Builder resourceOwnerId(Long resourceOwnerId)
```
    ResourceOwnerId.
  - signName
```
public CreateSmsSignRequest.Builder signName(String signName)
```
    Signature name. Please adhere to the Signature Specifications.
    Signature names are case-insensitive; e.g., 【Aliyun Communication】 and 【aliyun communication】 are considered identical.
    
    If your verification code signature and general signature names are the same, the system defaults to using the general signature for sending SMS messages.
    This parameter is required.
    example:
    Aliyun
  - signSource
```
public CreateSmsSignRequest.Builder signSource(Integer signSource)
```
    Signature source. Values:
    - 0: Full name or abbreviation of an enterprise or institution.
    - 1: Full name or abbreviation of a MIIT-registered website.
    - 2: Full name or abbreviation of an App.
    - 3: Full name or abbreviation of an official account or mini-program.
    - 4: Full name or abbreviation of an e-commerce platform store.
    - 5: Full name or abbreviation of a trademark.
    For detailed information on signature sources, refer to Signature Source.
    
    This interface does not support applying for signatures with sources as Test or Learning and Trial Use. If you need to apply for signatures with these sources, please go to the SMS Service Console.
    
    This parameter is required.
    example:
    1
  - signType
```
public CreateSmsSignRequest.Builder signType(Integer signType)
```
    Signature type. Values:
    - 0: Verification Code
    - 1: General (Default)
    It is recommended to use the default value: General.
    
    example:
    1
  - thirdParty
```
public CreateSmsSignRequest.Builder thirdParty(Boolean thirdParty)
```
    Choose whether the applied signature is for self-use or third-party use.
    - false: Self-use (default)
    - true: Third-party use
      
      Notice: Please select self-use qualification ID when the signature is for self-use; choose third-party use qualification ID when it"s for third-party use.
    example:
    false
  - trademarkId
```
public CreateSmsSignRequest.Builder trademarkId(Long trademarkId)
```
    TrademarkId.
  - build
```
public CreateSmsSignRequest build()
```

类 CreateSmsSignRequest.Builder

方法概要

从类继承的方法 java.lang.Object

方法详细资料

appIcpRecordId

applySceneContent

authorizationLetterId

moreData

ownerId

qualificationId

remark

resourceOwnerAccount

resourceOwnerId

signName

signSource

signType

thirdParty

trademarkId

build