Send pre-alert to subscribers

POST /pick/tipster/prealert/

Operation ID: prealert_pick_via_api

Send pre-alert for a pick of a specific package via API. This notifies subscribers that a pick is coming soon.

Request Body

{
  "apikey": "your_package_api_key_here"
}

Parameters

Field	Type	Required	Description
apikey	string	Yes	API key of the package to send pre-alert for

Response

Success Response (200)

{
  "status": "success",
  "message": "Pre-alert was sent to 150 subscribers",
  "package_name": "Premium Racing Tips",
  "subscriber_count": 150,
  "timestamp": "2024-01-24T21:00:00+11:00",
  "alert_details": {
    "alert_type": "pre_alert",
    "delivery_method": "push_notification",
    "estimated_pick_time": "2024-01-24T21:15:00+11:00"
  }
}

Error Responses

• 401 Invalid credentials - Authentication token is invalid or missing

• 404 API key is not valid - The provided API key is not valid or doesn't exist

• 500 Failed to send pre-alerts - Server encountered an error while sending pre-alerts

Usage

curl -X POST "https://betmatic.app/api/pick/tipster/prealert/" \
  -H "Content-Type: application/json" \
  -H "Authorization: Token your_token" \
  -d '{
    "apikey": "your_package_api_key_here"
  }'

Potential Use Cases

1. Subscriber Engagement: Alert subscribers that a pick is coming to increase engagement

2. Timing Coordination: Give subscribers advance notice to prepare for upcoming picks

3. Premium Service: Provide premium subscribers with early alerts before public picks

4. Market Preparation: Allow subscribers time to prepare their betting accounts

5. Expectation Management: Set expectations about when picks will be available

6. Subscriber Retention: Keep subscribers engaged with regular communication

7. Strategic Timing: Send alerts at optimal times for maximum subscriber attention

8. Service Differentiation: Differentiate premium packages with pre-alert features

Authentication

This endpoint requires authentication. Include your token in the Authorization header:

Authorization: Token your_token_here

Important Notes

• API Key Validation: The API key must be valid and associated with your tipster account

• Subscriber Count: The response includes the number of subscribers who received the alert

• Timing: Pre-alerts should be sent with sufficient time before the actual pick

• Rate Limiting: Be mindful of how frequently you send pre-alerts to avoid subscriber fatigue

• Package Association: Each API key is associated with a specific tip package

Best Practices

1. Consistent Timing: Send pre-alerts at consistent intervals before picks

2. Clear Communication: Ensure subscribers understand what a pre-alert means

3. Follow Through: Always follow pre-alerts with actual picks within reasonable time

4. Subscriber Preferences: Respect subscriber preferences for alert frequency

5. Quality Control: Only send pre-alerts for high-quality picks to maintain credibility

Integration Examples

Scheduled Pre-Alert:

# Send pre-alert 15 minutes before pick
curl -X POST "https://betmatic.app/api/pick/tipster/prealert/" \
  -H "Content-Type: application/json" \
  -H "Authorization: Token your_token" \
  -d '{
    "apikey": "premium_racing_2024_key"
  }'

Automated Workflow:

# Python example for automated pre-alert
import requests
import time

def send_prealert(api_key, auth_token):
    url = "https://betmatic.app/api/pick/tipster/prealert/"
    headers = {
        "Content-Type": "application/json",
        "Authorization": f"Token {auth_token}"
    }
    data = {"apikey": api_key}
    
    response = requests.post(url, json=data, headers=headers)
    return response.json()

# Send pre-alert before publishing pick
result = send_prealert("your_api_key", "your_auth_token")
print(f"Pre-alert sent to {result.get('subscriber_count', 0)} subscribers")

\