Developers

The AXEDOMO API

A small, public HTTP API for sending leads, complaints, stock alerts and bookings to a shop from anywhere: a landing page, a partner site, or your own tools. Every endpoint, field and status code below is taken straight from the running code.

Base URLhttps://www.axedomo.com

All requests and responses are JSON. Send Content-Type: application/json on every POST.

Authentication

The public endpoints are scoped by your shop_id, a public identifier for your shop, not a secret. There is no API key today. Only active shops accept writes.

Errors

A failed request returns a non-200 status and a body of the shape { "error": { "code": "INVALID_INPUT" } }. Validation failures add an issues list.

Your shop_id

Find your shop_id in your AXEDOMO admin, or ask us. Every request is tied to one shop, so leads and bookings land in the right place.

GET/api/v1/health

Health check

A public uptime probe. Returns the service name, version and a timestamp.

Auth: Public. No authentication.

Example request

curl https://www.axedomo.com/api/v1/health

Example response

200 OK

{
  "status": "ok",
  "service": "axedomo",
  "version": "1.168.0",
  "timestamp": "2026-07-19T00:00:00.000Z"
}

POST/api/v1/leads/submit

Submit a lead

Capture an enquiry for a shop from any site or form. The shop's team is notified.

Auth: Public, scoped by shop_id. No API key.

Body

shop_id	string (UUID)	required	The shop the lead belongs to.
name	string (1 to 120)	required	The person's name.
email	string, email (max 160)	required	Contact email.
phone	string (max 40), nullable	optional	Contact phone.
message	string (1 to 4000)	required	The enquiry text.
product_id	string (UUID), nullable	optional	A product the lead is about.

Example request

curl -X POST https://www.axedomo.com/api/v1/leads/submit \
  -H "Content-Type: application/json" \
  -d '{
  "shop_id": "00000000-0000-0000-0000-000000000000",
  "name": "Alex Morgan",
  "email": "alex@example.com",
  "message": "Do you deliver on weekends?"
}'

Example response

200 OK

{
  "data": { "ok": true }
}

Errors

400	INVALID_JSON	The body is not valid JSON.
400	INVALID_INPUT	A field failed validation. An issues array is included.
400	LEAD_FAILED	The shop is not active, or the write was rejected.

The team email is best effort. A mail problem never changes the 200 response.

POST/api/v1/complaints/submit

Submit a complaint

Raise a complaint against a shop, optionally tied to an order.

Auth: Public, scoped by shop_id.

Body

shop_id	string (UUID)	required	The shop the complaint is about.
email	string, email (max 254)	required	Contact email.
subject	string (3 to 120)	required	A short subject line.
body	string (3 to 4000)	required	The complaint detail.
name	string (max 120), nullable	optional	The person's name.
related_order_id	string (UUID), nullable	optional	An order the complaint relates to.

Example request

curl -X POST https://www.axedomo.com/api/v1/complaints/submit \
  -H "Content-Type: application/json" \
  -d '{
  "shop_id": "00000000-0000-0000-0000-000000000000",
  "email": "alex@example.com",
  "subject": "Late delivery",
  "body": "My order arrived two days later than promised."
}'

Example response

200 OK

{
  "id": "b7c1e2f3-4a5b-6c7d-8e9f-0a1b2c3d4e5f"
}

Errors

400	BAD_JSON	The body is not valid JSON.
400	VALIDATION_ERROR	A field failed validation. A field errors map is included.
404	SHOP_INACTIVE	The shop is not active.
500	ERROR	An unexpected error occurred.

POST/api/v1/stock-alerts/subscribe

Subscribe to a back-in-stock alert

Auth: Public, scoped by shop_id.

Body

shop_id	string (UUID)	required	The shop that owns the product.
product_id	string (UUID)	required	The product to watch.
email	string, email (max 254)	required	Where to send the alert.

Example request

curl -X POST https://www.axedomo.com/api/v1/stock-alerts/subscribe \
  -H "Content-Type: application/json" \
  -d '{
  "shop_id": "00000000-0000-0000-0000-000000000000",
  "product_id": "11111111-1111-1111-1111-111111111111",
  "email": "alex@example.com"
}'

Example response

200 OK

{
  "id": "c8d2f3a4-5b6c-7d8e-9f0a-1b2c3d4e5f60"
}

Errors

400	BAD_JSON	The body is not valid JSON.
400	VALIDATION_ERROR	A field failed validation.
400	INVALID_EMAIL	The email was rejected.
404	SHOP_INACTIVE or PRODUCT_NOT_FOUND	The shop is inactive or the product does not exist.
500	ERROR	An unexpected error occurred.

Subscribing the same email to the same product twice is safe: it updates in place.

POST/api/v1/bookings/create

Create a time-slot booking

Book a resource for a start and end time. For appointment-style bookings.

Auth: Public, scoped by shop_id.

Body

shop_id	string (UUID)	required	The shop that owns the resource.
resource_id	string (UUID)	required	The bookable resource.
starts_at	string, ISO date-time	required	Slot start.
ends_at	string, ISO date-time	required	Slot end.
customer_email	string, email	required	The customer's email.
customer_name	string (1 to 120), nullable	optional	The customer's name.
notes	string (max 2000), nullable	optional	Any booking notes.

Example request

curl -X POST https://www.axedomo.com/api/v1/bookings/create \
  -H "Content-Type: application/json" \
  -d '{
  "shop_id": "00000000-0000-0000-0000-000000000000",
  "resource_id": "22222222-2222-2222-2222-222222222222",
  "starts_at": "2026-08-01T09:00:00.000Z",
  "ends_at": "2026-08-01T10:00:00.000Z",
  "customer_email": "alex@example.com"
}'

Example response

200 OK

{
  "data": { "booking_id": "d9e3a4b5-6c7d-8e9f-0a1b-2c3d4e5f6071" }
}

Errors

400	INVALID_JSON	The body is not valid JSON.
400	INVALID_INPUT	A field failed validation. An issues array is included.
400	BOOKING_FAILED	The slot was rejected, for example already taken.

POST/api/v1/bookings/create-date-range

Create a date-range booking

Book a resource across a check-in and check-out date. For nightly stays and rentals.

Auth: Public, scoped by the resource_id (which belongs to one shop).

Body

resource_id	string (UUID)	required	The bookable resource.
check_in	string (YYYY-MM-DD)	required	First night.
check_out	string (YYYY-MM-DD)	required	Departure day.
customer_email	string, email (max 254)	required	The customer's email.
customer_name	string (max 120), nullable	optional	The customer's name.
notes	string (max 2000), nullable	optional	Any booking notes.

Example request

curl -X POST https://www.axedomo.com/api/v1/bookings/create-date-range \
  -H "Content-Type: application/json" \
  -d '{
  "resource_id": "22222222-2222-2222-2222-222222222222",
  "check_in": "2026-08-01",
  "check_out": "2026-08-04",
  "customer_email": "alex@example.com"
}'

Example response

200 OK

{
  "id": "e0f4b5c6-7d8e-9f0a-1b2c-3d4e5f607182"
}

Errors

400	INVALID_JSON	The body is not valid JSON.
400	INVALID_INPUT	A field failed validation. A field errors map is included.
400	CHECK_IN_IN_PAST or WRONG_MODE	The dates or the resource mode are not valid.
404	RESOURCE_NOT_FOUND or SHOP_INACTIVE	The resource does not exist or its shop is inactive.
409	DATES_UNAVAILABLE	The range overlaps an existing booking.
500	BOOKING_FAILED	An unexpected error occurred.

Not shown here

The storefront also uses internal endpoints (cart, checkout, analytics) and endpoints that need a signed-in customer or shop owner. Those are first-party and are not part of this public contract, so they can change without notice. Stripe reaches AXEDOMO over a signature-verified webhook, which is machine to machine and not a developer endpoint.

Need something that is not here, or a higher-trust integration? Talk to us.