With the Bundle Clone resource, developers can reuse compliance information across Twilio accounts. The resource creates a copy of a twilio-approved regulatory bundle against another account within the same organization. The new regulatory bundle is automatically set to the twilio-approved status, enabling you to start provisioning phone numbers in the new account immediately.
The unique string that we created to identify the Bundle resource.
^BU[0-9a-fA-F]{32}$Min length: 34Max length: 34The SID of the Account that created the Bundle resource.
^AC[0-9a-fA-F]{32}$Min length: 34Max length: 34The unique string of a regulation that is associated to the Bundle resource.
^RN[0-9a-fA-F]{32}$Min length: 34Max length: 34The verification status of the Bundle resource.
draftpending-reviewin-reviewtwilio-rejectedtwilio-approvedprovisionally-approvedThe date and time in GMT in ISO 8601 format when the resource will be valid until.
The email address that will receive updates when the Bundle resource changes status.
The URL we call to inform your application of status changes.
The date and time in GMT when the resource was created specified in ISO 8601 format.
The date and time in GMT when the resource was last updated specified in ISO 8601 format.
The URL of this resource.
POST https://numbers.twilio.com/v2/RegulatoryCompliance/Bundles/{BundleSid}/ClonesThe unique string that identifies the Bundle to be cloned.
^BU[0-9a-fA-F]{32}$Min length: 34Max length: 34application/x-www-form-urlencodedThe SID of the Account where the bundle needs to be cloned.
^AC[0-9a-fA-F]{32}$Min length: 34Max length: 34If set to true, the cloned bundle will be in the DRAFT state, else it will be twilio-approved
The string that you assigned to describe the cloned bundle.
Below is an example of creating a new Bundle Clone resource. The response from Twilio contains a JSON body with the created Bundle Clone's properties.
1// Download the helper library from https://www.twilio.com/docs/node/install2const twilio = require("twilio"); // Or, for ESM: import twilio from "twilio";34// Find your Account SID and Auth Token at twilio.com/console5// and set the environment variables. See http://twil.io/secure6const accountSid = process.env.TWILIO_ACCOUNT_SID;7const authToken = process.env.TWILIO_AUTH_TOKEN;8const client = twilio(accountSid, authToken);910async function createBundleClone() {11const bundleClone = await client.numbers.v212.bundleClone("BUef3a237936fb63163fd852d77c5ba27b")13.create({14friendlyName: "friendlyName",15targetAccountSid: "ACaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaab",16});1718console.log(bundleClone.bundleSid);19}2021createBundleClone();
1{2"bundle_sid": "BUef3a237936fb63163fd852d77c5ba27b",3"account_sid": "ACaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaab",4"regulation_sid": "RNaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",5"friendly_name": "friendlyName",6"status": "twilio-approved",7"valid_until": "2015-07-30T20:00:00Z",8"email": "email",9"status_callback": "http://www.example.com",10"date_created": "2015-07-30T20:00:00Z",11"date_updated": "2015-07-30T20:00:00Z",12"url": "https://numbers.twilio.com/v2/RegulatoryCompliance/Bundles/BUaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaab/Clones"13}
The following statuses encompass the Bundle lifecycle.
| Status | Description |
|---|---|
| draft | The user has created a new Bundle that can be edited with Supporting Documents and End-User objects assigned. |
| pending-review | When the user has finished the draft of the Bundle and submits to Twilio for review, the status moves from draft to pending-review. |
| in-review | Twilio has moved the Bundle from pending-review to in-review. Once Twilio has finished review, the Bundle will go either to twilio-approved or twilio-rejected. |
| twilio-rejected | Twilio has reviewed the Bundle and has determined the Bundle does not meet the regulations. |
| twilio-approved | Twilio has reviewed the Bundle and has determined the Bundles does meet the regulations. |