General Request Instructions (Base URL & Authentication)
Before making API requests, please understand the global network endpoints (Base URLs) and standard authentication methods used by our platform for different business lines.
1. Base Request URL (Base URL)
1.1 AI Model API Endpoints (for calling text, image, and video models)
APIShop has fully upgraded its underlying global network infrastructure to provide outstanding API response speeds and enterprise-grade security.
By deploying global edge computing nodes and intelligent routing technology, the system now supports ultra-fast nearby access worldwide. You no longer need to manually switch or configure nodes for different regions based on the physical location of your servers. Requests in all network environments now uniformly use our global primary endpoint.
Whether you are integrating with third-party tools (such as ClaudeCode and OpenClaw) or initiating code requests from your production servers, please configure Base URL to the following global endpoint:
https://cloud.apishop.aiEnterprise Network Features:
- Global intelligent routing: Automatically detects the client’s network environment and intelligently assigns the lowest-latency international dedicated route, ensuring millisecond-level ultra-fast response across borders and in complex network conditions.
- Enterprise-grade security protection: Powered by top-tier Web Application Firewall (WAF) and automatic DDoS mitigation mechanisms to safeguard your business continuity and data transmission security around the clock.
- Minimal, seamless integration: A high-availability architecture provides enterprise-grade SLA assurance. In most AI clients (such as Chatbox) or coding plugins, simply enter the single address above in the Base URL or API Endpoint field to make it work (note: some plugins may require appending
/v1at the end; follow the specific client prompt if needed).
2. API Authentication (Authentication)
APIShop global APIs use the industry-standard Bearer Token method for permission validation. To ensure the security of data transmission and credentials, all API requests must (strongly recommended) be made over HTTPS.
Header format example:
(Note: There must be a space between Bearer and your Key)
Authorization: Bearer YOUR_API_KEY3. Data Format (Content-Type)
Except for endpoints specifically noted otherwise (such as file uploads), we use JSON for both requests and responses. Please ensure your request headers include:
Content-Type: application/jsonNext steps
Now that you have the Base URL and authentication method for the relevant product, you can next:
- Go to the specific development tool integration guide and fill in your Key and Base URL in the development tool.
- Or start calling the Text Conversation (Chat Completions) API directly through code.