Introduction
Welcome to the Connect World API documentation. This API enables you to manage streaming subscriptions, process payments, and integrate with our content catalog.Base URL
All API requests should be made to:Authentication
The Connect World API uses server-side validation and rate limiting instead of API keys for public endpoints. All payment operations are secured through:- Rate limiting per IP address
- Server-side price validation to prevent tampering
- Honeypot fields to detect bot traffic
- Input sanitization on all parameters
Rate Limiting
Rate limits are applied per IP address to prevent abuse:| Endpoint | Rate Limit | Window |
|---|---|---|
/api/orders | 5 requests | 10 minutes |
/api/stripe | 10 requests | 15 minutes |
/api/paypal/create-order | 10 requests | 15 minutes |
/api/paypal/capture-order | No limit | - |
/api/tmdb | No limit | - |
Rate Limit Response
When you exceed the rate limit, you’ll receive a429 status code:
Error Response Format
All API errors follow a consistent format:Common HTTP Status Codes
Request succeeded
Resource successfully created
Invalid or missing parameters in the request
Rate limit exceeded - wait before retrying
Server error - contact support if persists
Error Codes
Common error messages you may encounter:| Error Message | Cause | Solution |
|---|---|---|
Datos del formulario inválidos o incompletos | Missing or invalid request parameters | Check all required fields are provided |
Plan inválido | Invalid plan ID | Use a valid plan ID: plan-1, plan-2, or plan-3 |
Duración inválida | Invalid subscription duration | Use valid months: 1, 2, 3, 6, or 12 |
Monto inválido | Amount doesn’t match plan pricing | Use correct price for selected plan and duration |
Número de dispositivos inválido | Devices don’t match plan | Ensure devices match the plan (1, 2, or 3) |
Demasiadas solicitudes | Rate limit exceeded | Wait before making more requests |
Available Plans
Connect World offers three subscription plans:Plan IDs
Quick Start
Here’s a typical workflow for creating a subscription:- Choose a plan and duration from the available options
- Create a payment intent using
/api/stripeor/api/paypal/create-order - Process the payment on the client side
- Create the order using
/api/orderswith the payment receipt ID
API Endpoints
Orders
Create and manage subscription orders
Stripe
Create Stripe payment intents
PayPal
Create and capture PayPal orders
TMDB
Fetch trending movies and shows
Request Headers
All POST requests should include:Best Practices
- Always validate prices client-side before submitting (server validates again)
- Implement exponential backoff when rate limited
- Handle all error responses gracefully
- Never expose payment secrets in client code
Support
If you encounter issues with the API:- Check this documentation for correct usage
- Verify your request parameters match the schemas
- Check rate limits and error messages
- Contact support with the error details and timestamp
