# API support for Packages

**URL:** <https://tech-support.simplybook.me/t/api-support-for-packages/1679>\
**Category:** Feature Requests\
**Created:** [April 15, 2026, 7:53am UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679 "2026-04-15T07:53:13Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![joshrigg99](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/j/59ef9b/32.png) [@joshrigg99](https://tech-support.simplybook.me/u/joshrigg99)\
**Post date:** [April 15, 2026, 7:53am UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/1 "2026-04-15T07:53:13Z")

</div>

Hi,

I’m building a custom booking interface using your JSON-RPC and REST API v2. The gift card endpoints (/admin/promotions/gift-cards and /admin/promotions/issue-gift-card) have been excellent and allowed us to fully automate gift card purchases.

We’d love the same level of API support for Packages. Currently there are no endpoints to:

1. List available packages (GET)
2. Get a client’s active package instances with remaining credits (GET)
3. Purchase/assign a package instance to a client (POST)
4. Book using a package credit (passing a package instance ID in the book() method)

The PackageInstanceEntity and PackageEntity are already documented in the REST API docs, so the data models exist — it’s just the endpoints that are missing.

This would allow developers building custom booking interfaces to offer the full package experience without falling back to the native widget. Right now, package management is the only feature we can’t automate.

Would be a great addition to the API. Thanks!

---

<div class="post-metadata">

**Author:** ![mib](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/m/ec9cab/32.png) [@mib](https://tech-support.simplybook.me/u/mib)\
**Post date:** [April 15, 2026, 7:53am UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/2 "2026-04-15T07:53:24Z")

</div>

Assigned @val\_komarov on April 15, 2026, 7:53am UTC



---

<div class="post-metadata">

**Author:** ![Alancoppin](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/a/67e7ee/32.png) [@Alancoppin](https://tech-support.simplybook.me/u/Alancoppin)\
**Post date:** [November 11, 2026, 3:05pm UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/3 "2026-11-11T15:05:55Z")

</div>

+1 from us, with a concrete use case and a narrower ask, since part of the original request is now covered.

We run Wildwood Sauna on our own booking site built on REST API v2. Customers who sign in with email and password use the public API with their client token, and for them packages work well: `GET /public/packages`, `GET /public/packages/instances`, `POST /public/invoice` + `add-package`, and applying a package to a booking invoice.

We also offer “Continue with Google”. Our server verifies the Google account, matches the verified email to a client (`GET /admin/clients?filter[search]=`), and then acts for that client through the admin API, because there’s no way to get a client token without the client’s password. Through the admin API we can now book (`POST /admin/bookings`), apply a package to an invoice (`POST /admin/invoices/{id}/package`), and list a client’s gift cards (`GET /admin/promotions/gift-cards?filter[purchased_by_client_id]=`). Thanks for those.

What’s still missing for packages on the admin side:

1. List a client’s package instances, with remaining credits. There’s no admin equivalent of `GET /public/packages/instances`. Today we rebuild it from the client’s invoices, which misses passes assigned by staff without an invoice.
2. Sell a package to a client: create an invoice for a `client_id` and add a package line, so it can be paid through `GET /admin/invoices/{id}/payment-link`. The same applies to gift cards, since `issue-gift-card` issues without payment.
3. Products on `POST /admin/bookings`. `AdminBookingBuildEntity` has no `products` field.

Alternatively, one change would remove the need for all three. The admin API already has OpenID sign-in for staff (`POST /admin/auth/openid-token` with `{provider, token}`). A client equivalent, for example `POST /public/clients/login-by-openid` with `{provider: "google", token}`, would return a client token for the client whose verified email matches, the same way your own booking site’s Google sign-in works. Then Google sign-ins on partner sites could use the public API exactly like password sign-ins, packages included.

Two smaller requests:

- A return URL on `GET /admin/invoices/{id}/payment-link`.
- The client cancellation and reschedule cutoff hours exposed in `/public/config` or `/admin/config`.

Happy to test any of this before release.

---

<div class="post-metadata">

**Author:** ![val\_komarov](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/v/848f3c/32.png) [@val\_komarov](https://tech-support.simplybook.me/u/val_komarov)\
**Post date:** [November 16, 2026, 8:10am UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/4 "2026-11-16T08:10:26Z")

</div>

Hi, I’ll check what of these can be added

---

<div class="post-metadata">

**Author:** ![val\_komarov](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/v/848f3c/32.png) [@val\_komarov](https://tech-support.simplybook.me/u/val_komarov)\
**Post date:** [November 16, 2026, 5:42pm UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/5 "2026-11-16T17:42:20Z")

</div>

We can’t add authentication by _any_ Google token - we should check whether it is given to a known app. Is it ok if we add a setting where you would enter your Google OAuth Client ID (and/or your Facebook App ID) to the API custom feature? Your site would send us the token Google or Facebook gives you after sign-in, and we return a client token.

A return URL on `GET /admin/invoices/{id}/payment-link` — we can add it, but probably OpenID would solve your needs instead?

The client cancellation and reschedule cutoff hours — I’d suggest per booking flags instead; we already have can\_reschedule\_booking and can\_reschedule\_booking\_error\_reason (not yet documented), and we could add similar can\_cancel\_booking and can\_cancel\_booking\_error\_reason

---

<div class="post-metadata">

**Author:** ![Alancoppin](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/a/67e7ee/32.png) [@Alancoppin](https://tech-support.simplybook.me/u/Alancoppin)\
**Post date:** [November 16, 2026, 8:43pm UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/6 "2026-11-16T20:43:06Z")

</div>

Thanks Val, that’s exactly what we need.

1. Google / Facebook → client token: yes please, a setting for our Google OAuth Client ID (and Facebook App ID) in the API custom feature is perfect. A few details so we build against it correctly:

- Which Google token will you accept: the ID token (JWT, audience checked against our Client ID) or the access token? We’d prefer the ID token.
- For a verified email with no client yet, could it return a clear “client not found” (rather than creating one), so we can collect phone and terms and then call `/public/clients/register`?
- For an email that matches an existing client (including one with a password), it should sign into that client, not create a duplicate.
- Same token lifetime and `remember` option as `/public/clients/login`?

2. Return URL on the payment link: agreed, not needed if (1) lands. Normal client sessions already use `callback_url` on `/public/payment-processor/pay`.

3. Cutoffs: per-booking flags are better than hours, thanks. `can_cancel_booking` / `can_cancel_booking_error_reason` alongside the reschedule pair, on `GET /public/booking` (and the admin bookings), would let us hide Cancel / Change time and show the reason. That includes unpaid bookings still waiting for payment, which customers currently can’t cancel.

Happy to test any of these early. Thanks again!

---

<div class="post-metadata">

**Author:** ![val\_komarov](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/v/848f3c/32.png) [@val\_komarov](https://tech-support.simplybook.me/u/val_komarov)\
**Post date:** [November 17, 2026, 8:59am UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/7 "2026-11-17T08:59:33Z")

</div>

Yes, the ID token for Google.

For the automatic registration, we can add a request parameter whether to use it. Our current internal logic for similar situation is:

- if a record with given external id already exists, auth it
- if it doesn’t exist, but a record with given email exists, reflect that in the response. In this case you can call “automatic client merge”, i.e. associate existing client record with given external id
- if neither exists, client record is not created automatically at this point, but only at the moment when client purchases something (books a service, buys a product etc.)

Token lifetime and remember options - noted, will add.

Sorry, no early testing - we will test internally and deploy when ready. This feature is waiting for another one to be released first

---

<div class="post-metadata">

**Author:** ![Alancoppin](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/a/67e7ee/32.png) [@Alancoppin](https://tech-support.simplybook.me/u/Alancoppin)\
**Post date:** [November 17, 2026, 10:53pm UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/8 "2026-11-17T22:53:42Z")

</div>

Thanks Val, that all works for us. One question on the “neither exists” case: what does the response contain then? Can we create the client with `/public/clients/register` (with phone and terms) and get a client token for the Google identity, or will booking with the ID token create and link the client itself?  
Let me know when it’s released 🙏, thanks a lot!!

---

<div class="post-metadata">

**Author:** ![val\_komarov](https://tech-support.simplybook.me/letter_avatar_proxy/v4/letter/v/848f3c/32.png) [@val\_komarov](https://tech-support.simplybook.me/u/val_komarov)\
**Post date:** [November 18, 2026, 7:45am UTC](https://tech-support.simplybook.me/t/api-support-for-packages/1679/9 "2026-11-18T07:45:19Z")

</div>

I’ll describe the scenario when it is implemented.

Current internal behavior for the case “neither exists” is to store client data in the token you receive from auth endpoint, and after that two options - either client record will be created automatically from that data once service is booked, or you can manually call an endpoint to create that client record from the data stored in the token
