API calls stopped working after migrating Sendy to another server

Comments

• Ben

  January 19

  Hi,

  When moving Sendy to a new server, API issues are usually caused by configuration differences rather than Sendy itself.

  Here are a few things to check:

  1. Make sure the API key you’re using matches the one shown in your Sendy's main settings on the new server.
  2. Verify that the Sendy URL in your API calls is updated to the new domain and that it’s accessible over HTTPS.
  3. Check that your server has cURL enabled and that outbound requests are not blocked by a firewall or security group.
  4. Ensure the database connection details in includes/config.php are correct and pointing to the active database.
  5. If you’re calling the API from another server, confirm that your hosting provider isn’t blocking cross-server requests.

  You can also check your server’s error logs to see if any errors are being returned when the API endpoint is hit, as this often points directly to the cause.

  Best regards,
  Ben