Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
Advanced Search


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @AlexD, Could you confirm if the two assumptions I made in my response are correct? Is an ‘Order.Create’ webhook sent automatically on the 'Next Order' date or only when a subscription renewal payment is successful? Is the 'Next Order' date updated to the date a successful payment attempt is made or does it remain unchanged regardless of when payment is received? (assuming that one of the three payment attempts is successful before the subscription is cancelled after 10 days). Thanks
  2. Hi @AlexD, I've just re-read my last post and it's not the clearest of responses! If you need clarification on any of the points please just let me know. Thanks
  3. Hi @AlexD and @creedon. Please find below details on the use case for providing subscription information via the SQSP Orders API. My apologies in advance for the lengthly message, but I wanted to be clear on the requirement. I offer my customers services that are supplied on a monthly basis i.e. a SQSP subscription product that is set to ‘repeat every 1 months’. As with most subscription services, I do not want the customer to be impacted (i.e. the service to stop) if there is a small delay in the subscription renewal payment So when the subscription is renewed (i.e. a successful payment attempt is made), the service must continue to be provided from the subscription renewal date, not the date the payment was successful. For example: A customer orders a monthly subscription service on 24 June 2021. i.e. their subscription period is 24 June to 23 July 2021. On 23 July, SQSP makes a payment attempt to renew the monthly subscription, but it fails due to an expired credit card or insufficient funds. Payment is then successful on a subsequent attempt, let’s say 5 days later on 28 July. The renewed subscription period needs to remain 24 July to 23 August 2021, despite the Order notification from SQSP being received on the 28 July. The above example from an API perspective When the monthly subscription service order is placed on 24 June 2021, SQSP sends an Order.Create webhook to my API with the orderId. My API calls the SQSP Orders API with the orderId and retrieves the SQSP order information. My API uses the SQSP order information to start a monthly subscription service for that customer, from 24 June - 23 July 2021. When the monthly subscription service order is successfully renewed on 28 July, SQSP sends an Order.Create webhook to my API and my API retrieves the order information. As no subscription information is returned in the order information, my API is unable to determine that this order is a renewal and so creates a new monthly subscription service for 28 July to 27 August. This means that services will stop for the customer between 24 July and 28 July. If the 'Next Order' date was provided in the order information returned by the SQSP Orders API, then my API could use that to ensure the subscription renewal period remains in sync with the SQSP subscription period and there is no impact to my customers. I hope the above clarifies why providing subscription information via the SQSP Orders API is vital to successful automation of subscription order management. Please let me know if I’ve made any incorrect assumptions in the above, specifically, I’ve assumed an ‘Order.Create’ webhook is only sent when a subscription renewal payment is successful. i.e. it is not sent on the SQSP 'Next Order' date, regardless of whether payment was successful? I've assumed the SQSP 'Next Order' date is not updated to the date a successful payment attempt was made? i.e. In the example above, the 'Next Order Date' would become 24 August and not 28 August. Just in case it's not clear, the SQSP 'Next order' date' I'm referring to is in the 'Customer Details' panel, when you click on 'Recurring' and then click on the subscription Order (see attached image) Thanks again for your help with this. Also worth mentioning: After basic testing, it seems that when a subscription order is cancelled, either by the customer or due to failed payment, an 'Order.Update' webhook is not triggered, so there is also no way of managing subscription cancellations via the API. It's such as disappointment to find a quality ecommerce platform that supports product subscriptions natively, to only then find that its API does not appear to support them 😞
  4. Hi @AlexD, Given that the Next Order Date is clearly considered a requirement for subscription orders, as it is included in both the email to the customer and the email to the SQSP store owner when an order is placed, I think it is reasonable to state that this is key order information that should be included in an Order.Create webhook and be accessible via the API. Assuming you agree with the above it makes sense to consider this as an issue/fault rather than a feature. Can you arrange for this to be tracked as an issue and provide some indication as to when it will be resolved? Thanks
  5. Hi @AlexD, thanks for looking into this. The Squarespace 'Next Order Date' is located in the emails as per below... Order Confirmed #00005: ...Your Next Order will be charged on July 16, 2021... A New Order Has Arrived #00005: ...The payment method the customer provided will be charged next on July 16, 2021... So for the Order #00005, the Next Order Date is July 16, 2021. This is the value that I cannot seem to access from any API call and does not appear in the 'Create.Order' webhook payload, yet it is provided in both Order notification emails. Thanks again for your help with this.
  6. Site URL: https://lolamack.com.au Currently there appears to be no way to get the 'Next Order Date' for subscription orders from any API call or webhook subscription. This information is however provided in the email sent by Squarespace when a subscription order is placed. Whilst I appreciate the API is relatively new, to have an api that provides less information than generic system emails suggests the API implementation is incomplete, even for a v1. Can anyone from Squarespace confirm that the 'Next Order Date' for subscription orders is not available via an API call or a webhook and assuming that is the case, comment on when this essential data might be made available programmatically? Thanks in advance
  7. Hi @AlexD, thanks for the quick response. Can you advise why not returning the customer ID is an intended behaviour, so that myself and other devs can better understand the likelihood of this feature being implemented at some point? Cheers
  8. Site URL: https://lolamack.com.au When making a call to https://api.squarespace.com/1.0/commerce/orders/{id} to retrieve details on a specific order, a significant amount of information about the customer is returned. Almost every aspect of the profile is returned, except for what I would have thought would be the most common requirement - the id of the customer who placed the order! This forces a second call using the 'Retrieve all profiles' endpoint to get the customer id, using the email address to search. Is there a reason why the customer (profile) id is not returned in the 'Retrieve a specific order' call, or is this something that the SQSP team could look to address? Thanks
  9. Site URL: https://lolamack.com.au Hi, When using more complex email addresses in the 'filter' query of an HTTP request from a Microsoft Azure Logic App to 'https://api.squarespace.com/1.0/profiles' , no matching responses are returned. The email addresses I'm using in the 'filter' query are being correctly encoded e.g. 'example01customer+01@gmail.com' is encoded to 'example01customer%2B01%40gmail.com' When using less complex email addresses, the Microsoft Azure Logic App does return the expected response. Using the exact same values in a call via Postman (e.g. host, URI, bearer token, User Agent, filter query), I do get a matching response. I've tried using both the Azure Logic App built-in 'HTTP' connector and a custom connector, but see the same issue with both. I appreciate it seems highly likely that this is a Microsoft Azure issue, but I'm hoping someone on this forum may have seen a similar issue and found a solution. Any guidance appreciated. Thanks
  10. Ok great. Once the submit is sending data to the Azure endpoint I can take it from there, but I have no knowledge of javascript. Any thought's on the best place to find people who'd be interested in taking on small coding tasks like this one for a reasonable fee?
  11. Thanks for the response. The data will be submitted to an Azure Logic App HTTP endpoint. Could the script be triggered in the post-submit HTML so that the form will continue to handle validation and spam filtering?
  12. Site URL: https://lolamack.com.au Although the Squarespace form allows integration with MailChimp, Sheets and Zapier, I'm hoping there's a way to configure a form submission to POST an HTTP request to an API with all the form fields included in the message. Does anyone know if this is possible? I know Zapier supports webhooks, so i could connect the form to Zapier and then get it to send the HTTP request, but Squarespace is the only app I use that doesn't support HTTP requests natively and so I don't want to pay for Zapier just for one integration. Maybe pushing my luck here, but ideally the solution would avoid any script. Any guidance appreciated!
  13. Thanks for that Tom, much appreciated. You mentioned you'd 'looked at the code for an add to cart button' - can you advise how/where you were able to look at the button code so I can do some digging myself? I have a similar requirement for a 'Form' button, where I want to be able to have a button on several different sections and pages but that points visitors to a single, specific form, and so need to understand the code behind form buttons as well. Thanks again.
  14. Hi, I'm hoping someone can verify if the code I'm using for a manually added 'Add to Cart' button is valid and will not cause issues. The button code sits within a standard SQSP Markdown block. When clicked the button should add a specific 'Service' product, defined by 'data-item-id', to the cart. <div class="sqs-add-to-cart-button sqs-suppress-edit-mode sqs-editable-button" role="button" tabindex="0" data-product-type="1" data-item-id="70221edaf456fe6e9b6b675c" data-original-label="Add To Cart"><div class="sqs-add-to-cart-button-inner">Coming Soon</div></div> Also, I can't find any information about the 'data-product-type' to confirm if "1" is correct for a 'Service' product type. Does anyone know? Thanks
  • Create New...