Skip to content

resendConfirmationEmail request for Brand Order.

Request

Resends the brand registration confirmation email to the end-customer. Certain product verification processes require the end-customer's approval via email to complete a brand's registration for a specific use case. If the end-customer has lost or did not receive the original email, you can call this endpoint to trigger a resend, enabling them to finalize the registration process.

This action can only be requested if the order is in a PENDING state. Furthermore, this functionality is currently available only for 10DLC/RCS (TCR) registration processes.

Security
OAuth2(Required scopes: write)
Path
projectIdstringrequired

Customer's project id

brandIdstringrequired

Brand ID reference

orderIdstringrequired

Order ID

curl -i -X POST \
  'https://compliance.api.sinch.com/v1/projects/{projectId}/us/brands/{brandId}/orders/{orderId}/resendConfirmationEmail' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

OK

Bodyapplication/json
brandOrderIdstringread-only

The unique identifier for the brand order.

brandIdstringread-only

Brand ID this Order belongs to.

statusstring(BrandOrderStatus)read-only

Brand order status represents the current state of the brand order in the system. When a brand order is created, it is in NEW status. After that, it can be moved to PENDING status when the validation process starts, then it can be moved to REJECTED or INCOMPLETE if the validation process fails, or to COMPLETED if the validation process is successful. When a brand order is in INCOMPLETE status, customer can update the brand/brand order. Updating the brand order moves the brand order to PENDING_REVIEW state, what means that is waiting for another review after the customer changes. Finally, a brand order can be moved to ARCHIVED status after a cancellation.

Enum ValueDescription
NEW

A new brand order created, not processed yet.

PENDING

The brand order info is under review.

PENDING_REVIEW

When a brand order is in incomplete status, customer can update the brand/brand order. Updating the brand order moves the brand order to PENDING_REVIEW state, what means that is waiting for another review after the customer changes.

REJECTED

The brand order has been rejected.

INCOMPLETE

The brand order is incomplete. The customer can update the brand/brand order to complete it.

COMPLETED

The brand order validation has been completed and the brand order is approved for integration against the channel specification.

ARCHIVED

The brand order is archived after a cancellation. It can not be updated or submitted for validation.

metadataNamestring(BrandOrderMetadata)read-only

Metadata name of the brand order, which identifies the type of the order and the process it follows. This field is useful to quickly check the type of the order without having to call the Get Brand Order endpoint.

Enum ValueDescription
US_SC_REGISTRY

For US Short Code brand verification. This is a legacy manual process that is now disabled and read-only. New registrations are not possible through this process. For new Short Code registrations, please use US_SC_GCH.

US_SC_GCH

Unified US Short Code verification process via the US Short Code Registry. The specific process to be applied is automatically determined by the brand's programType field: Standard → standard process, Government → government process, Charitable Organization → charity process, Political → political process. This process is free of charge and, upon successful completion, the SHORT_CODE channel will be granted to the brand.

US_SC_GCH_CONTENT_PROVIDER

US Short Code verification process for Content Provider entities. This process internally uses the US Short Code Registry and is free of charge. Upon successful completion, the SHORT_CODE channel will be granted to the content provider.

US_10DLC_TCR_SOLE_PROPRIETOR

To register as a Sole Proprietor for 10-Digit Long Code (10DLC) messaging via 10DLC, you can complete the registration process without needing an Employer Identification Number (EIN). Upon initiating the registration, a One-Time Password (OTP) will be automatically sent to the provided mobile number for identity verification, which you must subsequently submit using the endpoint /v1/projects/{projectId}/us/brands/{brandId}/orders/{orderId}/verifyOtp to successfully authorize and finalize the process.

US_10DLC_TCR_PRIVATE_BRAND_REGISTRATION

Simple brand registration with 10DLC for private companies to obtain the 10DLC channel in the US. This process does not include vetting. You will receive a TCR ID upon completion (approx. 1 minute). Provides lower throughput and a maximum of 3 numbers. Once completed, this process can be re-requested if any data needs to be modified (there are some fields not allowed for edition: legalCompanyName, entityType, federalTaxId and taxCountry). This process can be initiated again for revetting the brand, in case that critical information needs to be updated: entityType, legalCompanyName, federalTaxId or taxCountry. In this case, the brand will go through the same process as a new registration, with the same time of completion, but keeping the same TCR ID and the history of previous registrations.

US_10DLC_TCR_PUBLIC_BRAND_REGISTRATION

Simple brand registration with 10DLC for public companies to obtain the 10DLC channel in the US. This process does not include vetting. You will receive a TCR ID upon completion (approx. 1 minutes). Provides lower throughput and a maximum of 3 numbers. Once completed, this process can be re-requested if any data needs to be modified (there are some fields not allowed for edition: legalCompanyName, entityType, federalTaxId and taxCountry). This process can be initiated again for revetting the brand, in case that critical information needs to be updated: entityType, legalCompanyName, federalTaxId or taxCountry. In this case, the brand will go through the same process as a new registration, with the same time of completion, but keeping the same TCR ID and the history of previous registrations.

US_10DLC_TCR_PRIVATE_BRAND_UPDATE

Brand data update process with 10DLC for private companies that already have the 10DLC channel. This process is used to update any brand data that needs to be modified after a successful registration, except for critical information such as entityType, legalCompanyName, federalTaxId or taxCountry. Cost: free. You will receive a confirmation of the update upon completion (approx. 1 minute). This process does not affect the TCR ID, the throughput or the number of phone numbers allowed. Update process cannot be used after standard or enhanced vetting, as the brand needs to be revetted in case of any critical information update.

US_10DLC_TCR_PUBLIC_BRAND_UPDATE

Brand data update process with 10DLC for public companies that already have the 10DLC channel. This process is used to update any brand data that needs to be modified after a successful registration, except for critical information such as entityType, legalCompanyName, federalTaxId or taxCountry. Cost: free. You will receive a confirmation of the update upon completion (approx. 1 minute). This process does not affect the TCR ID, the throughput or the number of phone numbers allowed. Update process cannot be used after standard or enhanced vetting, as the brand needs to be revetted in case of any critical information update.

US_10DLC_TCR_PRIVATE_MOCK

A free-of-charge mock process for private companies to test the 10DLC integration. Successfully completing this process does not grant the 10DLC channel but serves as a preliminary check to ensure that subsequent paid TCR registrations will be successful.

US_10DLC_TCR_PUBLIC_MOCK

A free-of-charge mock process for public companies to test the 10DLC integration. Successfully completing this process does not grant the 10DLC channel but serves as a preliminary check to ensure that subsequent paid TCR registrations will be successful.

US_10DLC_TCR_PRIVATE_STANDARD_BRAND_REGISTRATION

Initiates a standard brand registration with 10DLC for a private company, which involves an automated review of compliance history, employee count, and other business metrics. The process, which typically takes 5-10 days, is used to verify the brand and assign a vetting score from 0-100 that determines the brand's throughput level with network carriers. A successful registration provides higher throughput and allows for unlimited campaigns and numbers. Once completed, this process can be re-requested if any data not included in US_TCR_PATCH_BRAND needs to be modified. Once completed, this process can be re-requested if any data needs to be modified (there are some fields not allowed for edition: legalCompanyName, entityType, federalTaxId and taxCountry)

US_10DLC_TCR_PUBLIC_STANDARD_BRAND_REGISTRATION

Initiates a standard brand registration with 10DLC for a public company, which involves an automated review of compliance history, employee count, and other business metrics. The process, which typically takes 5-10 days, is used to verify the brand and assign a vetting score from 0-100 that determines the brand's throughput level with network carriers. A successful registration provides higher throughput and allows for unlimited campaigns and numbers. Once completed, this process can be re-requested if any data needs to be modified (there are some fields not allowed for edition: legalCompanyName, entityType, federalTaxId and taxCountry)

US_10DLC_TCR_PRIVATE_ENHANCED_BRAND_REGISTRATION

Initiates an enhanced brand registration for a private company, which is recommended if you are dissatisfied with your Standard vet score and believe a more thorough review could yield a higher rating. This process is designed to improve the brand's vetting score and potentially achieve better throughput. Please note that this enhanced vet can only be ordered after a STANDARD registration is complete.

US_10DLC_TCR_PUBLIC_ENHANCED_BRAND_REGISTRATION

Initiates an enhanced brand registration for a public company, which is recommended if you are dissatisfied with your Standard vet score and believe a more thorough review could yield a higher rating. This process is designed to improve the brand's vetting score and potentially achieve better throughput. Please note that this enhanced vet can only be ordered after a STANDARD registration is complete.

US_RCS_TCR_PRIVATE_BRAND_REGISTRATION

US RCS brand registration process with RCS for private companies. This process is used to verify a private brand for RCS in the US. Upon successful completion, the RCS channel will be granted to the brand.

US_RCS_TCR_PUBLIC_BRAND_REGISTRATION

US RCS brand registration process with RCS for public companies. This process is used to verify a public brand for RCS in the US. Upon successful completion, the RCS channel will be granted to the brand.

US_RCS_TCR_UPDATE_ASSETS

US RCS asset update process with RCS. This process is used to update the brand assets required for RCS, such as logos or banners, after the brand has already been registered.

logsArray of objects(BrandOrderLog)read-only

Detailed history of the status changes this brand went through

channelsArray of stringsread-only

Channels available for this Brand Order

thirdPartyMetadataArray of objects(ThirdPartyElement)read-only

Third party metadata available for this Brand Order

pricingobject(Money)read-only

Includes details of the fee associated with the process to be carried out. For more information about pricing, you may consult your Account Manager or the Sinch Customer Dashboard.

callbackUrlstring, (uri)

The URL to receive the order status update callback. The URL must be a valid URL and must be reachable from Sinch.

createTimestring, (date-time)read-only

Create time of the request. ISO date time format in UTC.

updateTimestring, (date-time)read-only

Update time of the request. ISO date time format in UTC.

Response
{ "brandOrderId": "212421442412", "brandId": "b1c7ccbf-919d-462f-8587-dec95a1b11ee", "status": "PENDING", "metadataName": "US_10DLC_TCR_PRIVATE_BRAND_REGISTRATION", "logs": [], "channels": [], "thirdPartyMetadata": [], "pricing": { "amount": "5.00", "currencyCode": "USD" }, "callbackUrl": "https://example.com/callback", "createTime": "2024-01-15T10:00:00Z", "updateTime": "2024-01-15T10:06:00Z" }
We'd love to hear from you!
Rate this content: