What authentication does the Coupontools API use?

Coupontools requires paired credentials sent as the `X-API-Key` and `X-API-Secret` headers on every request. Through Jentic, both values are stored encrypted in your Jentic One instance and the agent receives a scoped session token rather than the raw credentials.

Can I validate a coupon code before applying a discount?

Yes. Call GET /coupon/{couponId}/validate with the coupon ID. The response indicates whether the coupon is active, unexpired, and not yet redeemed, so a checkout backend can decide whether to honour the discount.

How do I redeem a coupon at checkout?

POST /coupon/{couponId}/redeem marks the coupon as consumed and is the right endpoint to call once an order has been confirmed. Pair it with the validate call to keep redemption logic atomic.

What are the rate limits for the Coupontools API?

Coupontools applies plan-tier-based rate limits rather than a single public number. Most live shops should batch list calls and rely on per-coupon validate/redeem calls during user actions to stay well within typical quotas.

How do I issue a coupon through Jentic?

Search Jentic for 'create a Coupontools coupon', load the schema for POST /coupon, and execute it with discount value, expiry, and any customer reference. Jentic supplies the X-API-Key and X-API-Secret headers automatically.

Can I limit what my agent is allowed to do with the Coupontools API?

Yes. Because you run Jentic One yourself, your own rules decide which Coupontools operations the agent may call, so you can allow validate and redeem while withholding destructive calls like DELETE /coupon/{couponId} unless you explicitly add them. Since the coupon id sits in the URL path (for example /coupon/{couponId}/redeem), a rule can pin the agent to a single coupon so it acts only on that one. The paired X-API-Key and X-API-Secret stay in your own instance and are injected at execution time, so the agent never handles the raw credentials.