API Endpoints & Data Localization
As a leading global cloud communications provider, PaaSoo has deployed core infrastructure across multiple regions worldwide. To deliver the lowest possible network latency for your business while ensuring strict compliance with local data privacy regulations (such as the EU GDPR and China's Data Security Law), PaaSoo enforces strict regional isolation and data localization mechanisms.
When calling PaaSoo APIs, you must use the appropriate API Base URL (Endpoint) that corresponds to the PaaSoo entity you contracted with or registered under.
1. Global API Base URL Mapping
Please locate your business region in the table below, verify the supported products for that node, and use the recommended Base URL for all your API requests.
| Region | API Base URL | Supported Services | Data Localized | Use Case & Compliance |
|---|---|---|---|---|
| Singapore (Global) | https://api.paasoo.com | SMS, MMS, Voice | Yes (Singapore) | Default / Global Primary Node. Suitable for global operations without specific regional data compliance requirements. |
| Europe | https://api.paasoo.eu | SMS, MMS, Voice | Yes (Ireland) | EU Compliant Node. Data is securely isolated within the EU. Highly recommended for customers requiring GDPR compliance. |
| Mainland China | https://api.paasoo.cn | SMS, MMS, Voice | Yes (Beijing, China) | China Compliant Node. Complies with China's Data Export Security Assessment Measures. Dedicated environment for domestic operations. |
| India | https://api.paasoo.in | SMS, MMS, Voice | Yes (Mumbai, India) | India Compliant Node. Complies with TRAI regulations and local data localization mandates. |
| Hong Kong | https://api.paasoo.hk | SMS, MMS, Voice | Yes (Hong Kong, China) | Suitable for APAC and Greater Bay Area businesses, providing an isolated data storage environment. |
| Japan | https://api.paasoo.jp | Voice Only | Routed to Global Node | Optimized access point for low latency Voice services in Japan. Data security and storage are managed by the Global Primary Node. |
| Taiwan | https://api.paasoo.com.tw | SMS, MMS, Voice | Routed to Global Node | Optimized access point for low latency in Taiwan. Data security and storage are managed by the Global Primary Node. |
Please ensure you select the appropriate API endpoint based on your data compliance requirements and the location of your target users.
- Strict Compliance Requirements: If your business is subject to specific legal jurisdictions (e.g., EU GDPR, China's "Security Assessment Measures for Outbound Data Transfers", or India's data localization policies), please make sure to select the corresponding local compliant node. This ensures your data is stored securely within the local region without cross-border transmission.
- Global General Requirements: If your business does not have specific regional data residency restrictions, we recommend using the default Singapore (Global) primary node to achieve the best global network connectivity.
2. Using Endpoints in Your Code
When referencing specific API endpoints in this documentation (e.g., the Send SMS API), you will need to append the specific API path (such as /json for JSON responses) to your chosen API Base URL, along with your authentication parameters.
Example: Calling the Send SMS API using the Global Endpoint (api.paasoo.com)
# Request URL Structure: [Your Regional Base URL] + [API Path] + [Parameters]
# Please replace API_KEY and API_SECRET with your actual credentials
https://api.paasoo.com/json?key=API_KEY&secret=API_SECRET&from=TEST&to=12025550123&text=This+is+test+from+TEST
Tip: In your actual integration, please ensure that parameter values (like the text content) are properly URL-encoded. If your contracted entity belongs to a different region (e.g., Europe), simply replace api.paasoo.com in the example above with api.paasoo.eu.
3. Product-Specific Notes
- SMS / MMS: Fully support data localization and regional isolation. Please note that the Japan node (
api.paasoo.jp) does not support SMS/MMS services. To send SMS in Japan, please use the Singapore Global Primary Node (api.paasoo.com). - Voice: Due to the nature of international telecom carrier signaling and routing architectures, certain core control nodes for Voice products may be centralized in specific data centers (e.g., Singapore). If you have strict local data residency requirements for Voice media streams, please refer to the Voice API or contact your dedicated account manager.
If you encounter any technical issues or have business inquiries during the API integration, please do not hesitate to contact our Support team at support@paasoo.com. We are always here to assist you.