Hey there! Let's break down the most common issues that might be stopping your Pwinty webhook from firing, and walk through how to fix them step by step.

1. Double-Check Your Callback URL Configuration #

• First, verify the URL in your Pwinty dashboard is 100% correct: No typos, missing https:// (Pwinty requires HTTPS for production callbacks), or wrong path. Also, note that localhost or internal network URLs won't work—your endpoint needs to be publicly accessible. If you're testing locally, use a tool like ngrok to expose your local server to the internet.
• Make sure you've subscribed to the right events: Pwinty triggers callbacks only for specific events (like orderStatusChanged). Did you set the callbackUrl when creating the order via API, or configure a global default callback in the Pwinty dashboard? Ensure the event type you care about is enabled.

2. Verify Your Endpoint Is Accessible #

• Send a test POST request to your callback URL using tools like curl or Postman to simulate Pwinty's payload. For example:

  {
    "orderId": "test-order-123",
    "status": "Completed",
    "eventType": "orderStatusChanged"
  }
  

  If you don't receive this test request, your endpoint isn't reachable—fix your network settings, firewall, or use a tunnel tool for local testing.

3. Confirm Pwinty's Event Trigger Conditions Are Met #

• Check if the order status actually changed: Pwinty only sends a callback when the order status transitions (e.g., from Submitted to Processing, or Processing to Completed). Head to the Pwinty dashboard and check the order's status history to confirm a status change occurred.
• Don't mix up sandbox and production environments: Callback settings are separate for Pwinty's test (sandbox) and production environments. If you're testing in sandbox, make sure your callback URL is set in the sandbox dashboard, not the production one.

4. Debug Server-Side Issues #

• Check your server logs: Look for incoming requests from Pwinty. If you see requests but they're failing, logs will show errors like JSON parsing issues, permission errors, or unhandled exceptions.
• Ensure your endpoint accepts POST requests: Pwinty sends callbacks via POST—if your endpoint only handles GET, it'll ignore the request.
• Check firewalls/security groups: Your server's firewall or cloud provider's security group might be blocking Pwinty's IP addresses. If Pwinty publishes a list of allowed IPs, add them to your whitelist.
• Return a 200 OK response: Pwinty expects a successful 200 status code in response. If your endpoint returns 4xx/5xx errors, Pwinty will retry a few times before stopping. Make sure your endpoint responds with 200 even if you're still processing the payload in the background.

5. Test Pwinty's Callback Directly #

• Use Pwinty's built-in test tools (if available): Some API providers let you manually trigger test callbacks from their dashboard. Look for this option in Pwinty's webhook settings to send a test event to your URL.
• Check Pwinty's error logs: The Pwinty dashboard might have logs for failed callback attempts—look for messages like "URL unreachable" or "timeout" to narrow down the issue.

If you've gone through all these steps and still aren't getting callbacks, try creating a minimal callback endpoint (one that just returns 200 OK without any business logic) and test with that. This will help rule out issues with your application code.

内容的提问来源于stack exchange，提问作者RASHI choudhary