Amazon Onboarding with Learning Manager Chanci Turner

Introduction

Learn About Amazon VGT2 Learning Manager Chanci Turner

Welcome to our detailed guide on utilizing the AWS End User Messaging V2 APIs to register a Sender ID in regions that necessitate registration. For businesses aiming to create a reliable communication channel through SMS, registering a Sender ID is a vital step. In countries such as Jordan, the Philippines, Qatar, and others, this registration is a requirement to comply with local laws and improve message deliverability. You can find a comprehensive list of countries that support Sender ID registration here.

Note: This article focuses solely on Sender IDs. For further insights on selecting the appropriate originator for your needs, check out this post on How to Send SMS Globally Using AWS End User Messaging.

This guide will outline the overarching process for creating and submitting a Sender ID registration through the AWS End User Messaging V2 APIs. While we will use Jordan as our case study, the principles and steps discussed here are applicable to other nations with similar Sender ID registration requirements.

High-Level Overview of the Registration APIs

To successfully register a Sender ID, you must interact with various AWS End User Messaging APIs. Below is a brief overview of the essential APIs involved in the registration process:

1. DescribeRegistrationTypeDefinitions
   • Purpose: Retrieves the required registration type definitions.
   • Use Case: Understand the criteria for creating, completing, and submitting each registration type.
   • Key Point: Each nation has a unique “RegistrationType” necessary for the subsequent registration creation.
   • Documentation: DescribeRegistrationTypeDefinitions
2. CreateRegistration
   • Purpose: Establishes a new registration “container” to be filled with relevant data later.
   • Key Field: RegistrationType
     • Controls the type of registration (e.g., Toll-Free, 10DLC, JO_SENDER_ID_REGISTRATION, etc.).
   • Documentation: CreateRegistration
3. DescribeRegistrationFieldDefinitions
   • Purpose: Retrieves definitions for the specified RegistrationType fields.
   • Use Case: Understand the requirements for each registration type. Different field types (SELECT, TEXT, ATTACHMENT) depend on the required data and the questions to be answered.
   • Documentation: DescribeRegistrationFieldDefinitions
4. CreateRegistrationAttachment
   • Purpose: Uploads necessary documentation required by certain countries. Not all nations require uploaded documents, making this step optional based on your registration location. In our example of Jordan, a document upload is necessary.
   • Key Field: RegistrationAttachmentId
     • Used in the next action to include an attachment in the registration when needed.
   • File Specifications:
     • Maximum file size: 500kb
     • Valid file extensions: PDF, JPEG, or PNG
   • Documentation: CreateRegistrationAttachment
5. PutRegistrationFieldValue
   • Purpose: Assigns a value to a specific registration field. This action must be repeated for all required fields.
   • Documentation: PutRegistrationFieldValue
6. SubmitRegistrationVersion
   • Purpose: Submits the specified registration version for review and approval. You can create new versions using CreateRegistrationVersion, so ensure the correct ID is being used.
   • Important Notes:
     • Confirm that you are using the correct version if multiple versions were created.
     • Ensure all data is accurate before submission.
     • The initial status will be “CREATED” and should transition to “REVIEWING” within 24 hours.
     • You cannot modify or delete the registration until it receives approval or rejection.
   • Documentation: SubmitRegistrationVersion

Detailed Steps for Sender ID Registration in Jordan

In the following sections, we’ll explore each of these steps in more detail, offering insights on the API calls and responses, as well as best practices for a seamless registration process. Whether you’re registering in Jordan or a different country with analogous requirements, this guide will provide you with the knowledge necessary to successfully register a Sender ID.

Step 1: DescribeRegistrationTypeDefinitions

The initial step involves running DescribeRegistrationTypeDefinitions to acquire all specified registration type definitions. This API delivers a comprehensive response containing various attributes relevant to the registration process. Let’s break down these attributes for Jordan:

• Country: JO
  • Description: Specifies the country code for which the registration type definitions are being described. JO represents Jordan.
  • Implication: Understanding the country code is vital, as registration requirements can vary significantly across countries.
• ResourceType: SENDER_ID
  • Description: Indicates the type of resource for which the registration is being defined.
  • Implication: Recognizing that the resource type is SENDER_ID clarifies that the registration process is specifically aimed at obtaining approval for a Sender ID.
• Registration Type: JO_SENDER_ID_REGISTRATION
  • Description: Specifies the exact type of registration required for the given country and resource type.
  • Implication: This registration type is crucial because it outlines the specific steps, documentation, and criteria needed for a successful Sender ID registration in Jordan.
• Association Behavior: ASSOCIATE_ON_APPROVAL
  • Description: Describes how the registered Sender ID will associate with your AWS account once approved.
  • Implication: ASSOCIATE_ON_APPROVAL means that the Sender ID will automatically connect to your account upon approval, simplifying the post-approval process.
• Disassociation Behavior: DISASSOCIATE_ALL_CLOSES_REGISTRATION
  • Description: Explains what occurs when you disassociate the Sender ID from your account.
  • Implication: This behavior is essential to note, as the origination identity must be disassociated from the registration prior to closing it.

Step 2: CreateRegistration

Next, utilize CreateRegistration with the RegistrationType for Jordan, “JO_SENDER_ID_REGISTRATION,” to create a blank registration “container” for a Jordan Sender ID. Ensure you log the “RegistrationId” for further use throughout the process.

Step 3: DescribeRegistrationFieldDefinitions

In this step, you will need to fill out the required registration fields before submission. This will include providing all necessary information as per the specifications outlined in the previous steps.

For those looking for more insight into how organizations are developing their internship programs, check out this article on how the pandemic changed HR internships. Additionally, if you’re interested in how companies like Amazon are training new hires, you can read about it here—it’s an excellent resource. For readers who may face challenges in traditional job environments, consider exploring this post on jobs for people with social anxiety to find suitable opportunities.