1. Checkout APIs
Salla Platform Docs
  • Overview
  • Authentication
  • Key Concepts
  • Usage Flows
  • Cart
    • Save guest cart data
      POST
    • Generate cart
      POST
    • Get cart
      GET
    • Assign cart to Customer
      POST
    • Apply cart coupon
      POST
    • Remove cart coupon
      DELETE
  • Cart Items
    • Add cart item
      POST
    • Update cart item
      PATCH
    • Delete cart item
      DELETE
  • Schemas
    • SuccessEnvelope
    • GuestDataRequest
    • GuestData
    • Error
    • Money
    • CartTotals
    • TotalLineItem
    • CartItem
    • AssignShippingRequest
    • CartItemsRequest
    • ProductIdentifier
    • CartItemEntry
    • RemoveItemsRequest
    • BadRequest
    • Unauthorized
    • Forbidden
    • NotFound
    • ValidationError
    • Currency
    • AmountLine
    • CartScope
    • CartFeatures
    • CartAmounts
    • CartDiscountEntry
    • CartOptionEntry
    • Cart
    • CartShipping
    • CartItemCreateRequest
    • CartItemUpdateRequest
    • ApplyCouponRequest
    • ErrorEnvelope
    • CartItemOptionInput
    • ErrorObject
    • GenerateCartRequest
Merchant
Merchant
  • Merchant API
  • Embedded SDK
  • Salla OAuth 2.0
Storefront
Storefront
  • Twilight Engine
  • Twilight SDK
  • Web Components
  • Ecommerce Events
  • Component Bundle
  • Checkout APIs
  • Change Log
App Functions
Partner APIs
Partner APIs
  • App API
  • Shipments & Fulfillment APIs
  • Salla AWB
  • Recurring Payments API
  • Billing System Salla partners
  • Communication Apps
Dev Tools
Dev Tools
  • Partners Agent Kit
  • Salla Apps Playbook
  • Salla CLI
Merchant
Merchant
  • Merchant API
  • Embedded SDK
  • Salla OAuth 2.0
Storefront
Storefront
  • Twilight Engine
  • Twilight SDK
  • Web Components
  • Ecommerce Events
  • Component Bundle
  • Checkout APIs
  • Change Log
App Functions
Partner APIs
Partner APIs
  • App API
  • Shipments & Fulfillment APIs
  • Salla AWB
  • Recurring Payments API
  • Billing System Salla partners
  • Communication Apps
Dev Tools
Dev Tools
  • Partners Agent Kit
  • Salla Apps Playbook
  • Salla CLI
Salla - Opensource
Salla - Developers Community
  1. Checkout APIs

Authentication

image.png

Authentication#

The Checkout APIs support two access modes: guest and authenticated.
Store-Identifier is required on all requests. Bearer token authentication is required only on endpoints that explicitly enforce user identity (for example, cart assignment).
ModeAuthorizationUse when
GuestNot requiredCreating carts, adding items, applying coupons, retrieving guest carts
AuthenticatedRequired on protected routesAssigning a cart to a user and operating in user-identity flows
Cart generation supports both contexts:
without auth token: cart is created in guest context
with valid auth token: cart can be created in authenticated customer context
When needed, a guest cart can later be assigned to a logged-in user via the assign endpoint.

Request Headers#

All Checkout API requests must include the required platform headers in addition to store authentication headers.

Required Headers#

HeaderRequiredDescription
Store-IdentifierYesIdentifies the target store for every request
s-sourceYesRequest source identifier app
s-app-nameYesName of the calling application
s-app-versionYesVersion of the calling application
AuthorizationConditionalBearer token in the format Bearer <token>. Required for authenticated/user-scoped operations

Optional Tracking Headers#

These headers are recommended for analytics, attribution, and campaign tracking.
HeaderRequiredDescription
s-utm-sourceNoTraffic source
s-utm-campaignNoCampaign identifier
s-utm-mediumNoMarketing medium
s-utm-termNoPaid keyword / search term
s-utm-contentNoContent variation identifier
s-utm-referrerNoReferrer source URL or identifier

Examples#

These examples demonstrate the minimum required headers for both guest and authenticated Checkout API requests.
Optional tracking headers can also be included to support analytics, attribution, and campaign reporting.

Guest Request#

Authenticated Request#

Request With UTM Headers#

Common Error Responses#

StatusMeaning
400Missing token on endpoint that requires authentication
401Invalid or expired token
403Token is valid but cart access is forbidden (ownership/scope rules)
404Cart not found or invalid cart identifier
Modified at 2026-07-29 11:46:05
Previous
Overview
Next
Key Concepts