Server Callback Setup

All Plans

Configure your game server to receive vote data for in-game rewards

Overview

Server callbacks allow VotePipe to send vote data directly to your game server, enabling you to automatically reward players for voting. This feature is available on all plans.

Note: Server callbacks require a publicly accessible endpoint on your game server. Make sure your server can receive HTTP POST requests from the internet.

Setup Instructions

Create an HTTP endpoint on your game server that accepts POST requests
Go to Callbacks in the dashboard
Enter your callback URL (e.g., https://your-server.com/api/vote)
Optionally, set an authentication secret (sent as Authorization: Bearer header)
Click Test Callback to verify it works
Save your settings

Endpoint Requirements

HTTP Method

POST

Response Codes

200 OK - Vote processed successfully
4xx - Client error (will retry)
5xx - Server error (will retry)

Timeout

Your endpoint should respond within the timeout period for your plan:

Free: 5 seconds
Pro: 15 seconds
Network: 30 seconds

Authentication

If you configure an authentication secret, VotePipe will send it in the Authorization header:

http

Authorization: Bearer <your-secret>

Always verify this header on your server to ensure requests are coming from VotePipe.

Payload Format

VotePipe sends vote data in JSON format:

json

{
  "event": "vote",
  "vote_id": "vt_550e8400-e29b-41d4-a716-446655440000",
  "voter_name": "PlayerName",
  "provider": "hytale-servers-pro",
  "received_at": "2026-01-02T15:30:00.123Z"
}

See the Payload Format page for detailed field descriptions.

Retry Logic

VotePipe automatically retries failed callbacks:

5 immediate retries with exponential backoff (1s, 2s, 4s, 8s, 16s)
Pro+: Additional delayed retries over 1-4 hours

Learn more about retry logic.

Troubleshooting

Common issues and solutions:

Callback not receiving requests

Verify your callback URL is publicly accessible
Check firewall rules allow incoming POST requests
Ensure your server is running and the endpoint exists
Use the Test Callback button to verify connectivity

Authentication failures

Verify the Authorization header matches your configured secret
Check for extra spaces or encoding issues

See the troubleshooting guide for more help.

API Management

You can also manage callbacks programmatically using the API:

→ List all callbacks → Create a callback via API → Test a callback endpoint → Delete a callback