メニュー

Expand
ページを評価:

Regulation Resource

Regulations Response Properties

The Twilio Regulatory Compliance REST API allows you to view and understand Regulations. Regulations are requirements based on End-Users and Supporting Documents set for by each country's government.

A Regulation dictates the Regulatory Bundles composition of Item Assignments.

Regulations can and do change. Please make sure not to hardcode any regulation within your application. The Regulation resource is for you to call and populate the values required for regulatory compliance.

Resource Properties in REST API format
sid
sid<RN> Not PII

The unique string that identifies the Regulation resource.

friendly_name
文字列 Not PII

A human-readable description that is assigned to describe the Regulation resource. Examples can include Germany: Mobile - Business.

iso_country
文字列 Not PII

The ISO country code of the phone number's country.

number_type
文字列 Not PII

The type of phone number restricted by the regulatory requirement. For example, Germany mobile phone numbers provisioned by businesses require a business name with commercial register proof from the Handelsregisterauszug and a proof of address from Handelsregisterauszug or a trade license by Gewerbeanmeldung.

end_user_type
enum:end_user_type Not PII

The type of End User the regulation requires - can be individual or business.

requirements
オブジェクト Not PII

The SID of an object that holds the regulatory information of the phone number country, phone number type, and end user type.

url
url Not PII

The absolute URL of the Regulation resource.

Fetch a Regulation Instance

GET
https://numbers.twilio.com/v2/RegulatoryCompliance/Regulations/{Sid}

A Regulation instance details the End-User Types and values along with Supporting Document Types.

パラメーター
Parameters in REST API format
sid
Path
GET sid<RN> Not PII

The unique string that identifies the Regulation resource.

例 1
        
        
        

        Retrieve a list of regulations

        GET
        https://numbers.twilio.com/v2/RegulatoryCompliance/Regulations

        The Regulations list is extensive and covers all Twilio's countries in the Phone Number Regulations Guidelines.

        The Regulations LIST endpoint is filterable by IsoCountry, NumberType, and EndUserType so you can select the correct instance of the collection of regulatory requirements.

        パラメーター
        Parameters in REST API format
        end_user_type
        オプション
        GET ienum:end_user_type Not PII

        The type of End User the regulation requires - can be individual or business.

        iso_country
        オプション
        GET 文字列 Not PII

        The ISO country code of the phone number's country.

        number_type
        オプション
        GET 文字列 Not PII

        The type of phone number that the regulatory requiremnt is restricting.

        例 1
              
              
              
              ページを評価:

              ヘルプが必要ですか?

              We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Community Forums or browsing the Twilio tag on Stack Overflow.

                    
                    
                    

                    フィードバックくださりありがとうございます!

                    We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

                    Sending your feedback...
                    🎉 Thank you for your feedback!
                    Something went wrong. Please try again.

                    Thanks for your feedback!

                    Refer us and get $10 in 3 simple steps!

                    ステップ1

                    Get link

                    Get a free personal referral link here

                    ステップ2:

                    Give $10

                    Your user signs up and upgrade using link

                    ステップ3

                    Get $10

                    1,250 free SMSes
                    OR 1,000 free voice mins
                    OR 12,000 chats
                    OR more