Blocked Time Endpoints4

Booking Endpoints40

Coupon Endpoints4

Customer Endpoints13

Extra Endpoints2

Group Endpoints1

Notification Endpoints4

Promocode Endpoints2

Reporting Endpoints2

Room Endpoints2

Studio Endpoints1

Customer Endpoints

Create a customer

Create a new customer on Jammed.

With a new customer, you must at least provide an name and email address.

You can also issue actions to the endpoint, to create and invite the customer to set a password - Jammed will then send them an email from your account with a link to set their password.

You can't create a customer with an email address that already exists as a registered customer on Jammed. You can create a customer with an email address that already exists, so long as the customer is not yet registered on Jammed.

Jammed API doesn't accept passwords for customer creation process - they must be set by the customer themselves in the invitation process to verify the email and to improve security.

post/customers.json

Headers

Authorizationstring required

Response

Customer created

idinteger

Use to identify the customer in other API calls

namestring

The customers given full name

emailstring

The customers email address

mobilestring

The customers mobile phone number

avatarstring

The customers avatar image URL, if any

credit_balanceinteger

The customers current credit balance in cents/pence/units

This cannot be changed via the API

status'unregistered' | 'invited' | 'registered' | 'banned' | 'behind_payment'

The status of the customer

unregistered: The customer has booked but not registered an account invited: The customer has been invited to register an account registered: The customer has registered an account banned: The customer has been marked as banned from booking (and will not be able to book) behind_payment: The customer has been marked as behind on payments (and will not be able to book)

reminders_opt_inboolean

Whether this customer wants to receive reminders

mailing_list_opt_inboolean

Whether this customer wants to be on the mailing list

signed_upboolean

Whether the customer has signed up

signed_up_atinteger

Unix timestamp from epoch - when the customer signed up

bookings_countinteger

The number of bookings the customer has made

created_atinteger

Unix timestamp from epoch - when the customer was created

updated_atinteger

Unix timestamp from epoch - when the customer was last updated

last_booking_atinteger

Unix timestamp from epoch - when the customer last booked

Changes

Changed in 5 of the 32 revisions of this API.31013

Jun 8, 2026v26ad81b94d5301See the full diff
- ○
  added the optional property / to the response with the status
  response-optional-property-added
Mar 29, 2026v23535cc88f40712See the full diff
- ▲
  response property items/regular_bookings_count list-of-types was widened by adding types boolean to media type application/json of response 201
  response-property-list-of-types-widened
- ○
  added the optional property /// to the response with the status
  response-optional-property-added
- ○
  added the optional property /// to the response with the status
  response-optional-property-added
Jan 13, 2025v2b0215746332253See the full diff
- ●
  added the new banned enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new behind_payment enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new invited enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new registered enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new unregistered enum value to the / response property for the response status
  response-property-enum-value-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  added the optional property / to the response with the status
  response-optional-property-added
- ○
  the response property /// became required for the status
  response-property-became-required
Jan 13, 2025v29331d0ba95381See the full diff
- ○
  the response property /// became required for the status
  response-property-became-required
May 5, 2022v295c52cb13f9a256See the full diff
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ●
  removed the optional property / from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property /// from the response with the status
  response-optional-property-removed
- ●
  removed the optional property / from the response with the status
  response-optional-property-removed
- ●
  removed the optional property / from the response with the status
  response-optional-property-removed
- ○
  removed the banned enum value from the / response property for the response status
  response-property-enum-value-removed
- ○
  removed the behind_payment enum value from the / response property for the response status
  response-property-enum-value-removed
- ○
  removed the invited enum value from the / response property for the response status
  response-property-enum-value-removed
- ○
  removed the registered enum value from the / response property for the response status
  response-property-enum-value-removed
- ○
  removed the unregistered enum value from the / response property for the response status
  response-property-enum-value-removed
- ○
  response property items/regular_bookings_count list-of-types was narrowed by removing types boolean from media type application/json of response 201
  response-property-list-of-types-narrowed
This revision also has 29 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history