Paddle Webhooks - Are custom /api/* routes supported?

Teable Discussions
1

Hi everyone,

I’m building an app with:
• Paddle Billing
• Teable tables for subscription storage

The frontend Paddle checkout integration works correctly.

However, I need a webhook endpoint for Paddle events such as:
• subscription.created
• subscription.updated
• transaction.completed
• transaction.payment_failed

I implemented a standard Next.js Route Handler:
app/api/paddle/webhook/route.ts

But after publishing, the live URL:

https://domain.com/api/paddle/webhook

returns 404.

So I’m trying to understand:

  • Does Teable App Builder support custom Next.js API routes / Route Handlers?
  • Is the hosting environment frontend/static only?
  • Are there special deployment steps required for /api/* endpoints?
  • Has anyone successfully implemented Paddle/Stripe webhooks?

If backend routes are NOT supported, what is the recommended architecture?

My goal is simply:

Paddle webhook
↓
Update Teable Subscriptions table

Thanks!

2

Hi @Alex ,

App Builder supports Next.js API routes — apps have no special restriction on /api/* endpoints.

The 404 is most likely a route path, implementation, or republishing issue. A quick way to confirm: ask the AI to create a minimal route that just returns 200, publish it, and test if it’s reachable. Once that works, you can wire up the Paddle webhook logic.

1 Like
3

This is solved, thanks!

1 Like