Improving the Tebex Headless API

Hello Tebex Team,

My name is Joshua Cote, and I’m a software engineer who works extensively with Tebex across multiple client projects. A growing number of my clients are transitioning to the Headless API, and while we strongly believe in the potential of a true headless experience, we’ve encountered several limitations that are impacting development efficiency and end-user experience.

I’d like to offer constructive feedback based on real-world implementation experience, and I am also willing to contribute voluntarily if there is an opportunity to collaborate on improvements.

Below are the main areas where enhancements would significantly improve the developer experience:

1. Variables Support
   Currently, when a package uses variables, there is no reliable way through the Headless API to determine:

2. Which variables are required for a package

3. The variable ID
4. Input type
5. Label or metadata

Instead, we receive a generic “variable being used” error and must manually guess which variable applies to which package. This creates unnecessary delays and makes proper automation extremely difficult. Exposing variable definitions directly in the package response would solve this.

1. Server Variables / server_id Handling
   When a store has multiple servers, server_id becomes required. However, there is no indication in the package response showing which server(s) a specific package belongs to.

This forces developers to:

• Ask users to manually select a server without certainty
• Or attempt trial-and-error requests

Ideally, the package response should include the server IDs it is enabled for, so we can accurately associate products with the correct server.

1. Webhooks for Headless API
   Currently, we must repeatedly poll the basket API to detect updates, which increases server load and complicates frontend state management.

Native webhook support for headless baskets and transactions would allow us to:

• Receive real-time POST updates
• Sync frontend state immediately
• Reduce unnecessary API calls

This would greatly improve performance and resource efficiency.

1. Regional Pricing & Testing
   At the moment, regional pricing appears to be hard-locked to the developer’s IP location. This makes it extremely difficult to properly test pricing logic for international clients.

A sandbox mode or a way to simulate regional pricing would be extremely valuable.

Additionally, it would be helpful if pricing responses consistently included:

• Currency symbol
• Currency code (USD, EUR, etc.)
• Final converted price

These additions would make the Headless API far more developer-friendly and production-ready.

I truly believe in the future of Tebex and the potential of the Headless API. I would be happy to explore ways to contribute feedback, assist with testing, or even discuss partnership opportunities that benefit both Tebex and the developers building on top of it.

Thank you for your time, and I look forward to hearing from you.

Best regards,
Joshua Cote