sso_update_loyalty_checkin

Update Loyalty Check-in

​

Updates a loyalty check-in in the pending state based on external_uid. Requires all parameters to be sent again (no deltas).

Headers
  • x-pch-digest
    Type: string
    required

    The signature for the API call

  • Content-Type
    Type: string
    required

    Set this header to application/json.

  • Accept
    Type: string
    required

    Advertises which content types the client is able to understand

  • Authorization
    Type: string
    required

    You may pass the access_token instead of the authentication_token in Online Ordering endpoints to authorize the request. It must be supplied as Bearer ACCESS_TOKEN_GOES_HERE. Note: When authentication is performed using Advanced Authentication, you must include the id_token in the id-token header and the access_token in the Authorization header. See Access Punchh APIs Using Access and ID tokens

  • User-Agent
    Type: string
    required

    For details, see User Agent.

  • id-token
    Type: string

    A token that contains identity information about the authenticated user. It is used to verify the user’s identity and is required only when authentication is performed using Advanced Authentication. This token alone does not grant access to Punchh APIs. To access the APIs, you must include the id_token in the id-token header and the access_token in the Authorization header. See Access Punchh APIs Using Access and ID tokens

Body
application/json
  • authentication_token
    Type: string

    The authentication token of the user. You can retrieve this from the response of a successful sign-in API call or through the SSO process.

  • cc_last4
    Type: string

    Last 4 digits of credit card number

  • client
    Type: string
    required

    Client key of the business

  • employee_id
    Type: string

    Employee ID. In case of a system order, it can be a system-generated ID.

  • employee_name
    Type: string

    Employee who took the order. In case of a system order, it can the be name of the system.

  • external_uid
    Type: string

    Unique ID generated by your system. We use this to prevent duplicates in case the same transaction gets triggered twice.

  • menu_items
    Type: array Menu Items (Object)[]
  • receipt_amount
    Type: numberFormat: double

    Order amount before taxes, calculated as the sum of all item amounts minus any discounts. This is the amount used to calculate loyalty points/visits. The value of this parameter should match subtotal_amount. For example, if the order amount is $10, both receipt_amount and subtotal_amount will be 10. If a $2 discount is applied, both will be 8.

  • receipt_datetime
    Format: date-timeenum
    const:  
    YYYY-MM-DDThh:mm:ssZ

    Timestamp of the receipt as per ISO 8601, in YYYY-MM-DDTHH:MM:SSZ format

    • YYYY-MM-DDThh:mm:ssZ
  • subtotal_amount
    Type: numberFormat: double

    Order amount before taxes (sum of all item amounts minus any discounts). Same as receipt_amount. For historical reasons, include this parameter along with receipt_amount in the API request.

  • transaction_no
    Type: string

    Receipt number or transaction number on the receipt

Responses
  • 200
    Type: object
    • checkin
      Type: object
    • checkins
      Type: integer

      Total number of check-ins for this online order

    • first_name
      Type: string

      First name of the user

    • last_name
      Type: string

      Last name of the user

    • points
      Type: integer

      Total points earned for this online order

  • 400

    Sending missing/incorrect params, bad encoding etc

  • 401

    Sending invalid credentials

  • 412

    Sending invalid Signature

  • 422

    Sending invalid Entity

put/api/auth/checkins/online_order
{
  "first_name": "string",
  "last_name": "string",
  "checkins": 1,
  "points": 1,
  "checkin": {
    "bar_code": "string",
    "created_at": "string",
    "external_uid": "string",
    "checkin_id": 1,
    "pending_points": 1,
    "pending_refresh": true,
    "points_earned": 1
  }
}