#josula_api

1 messages ¡ Page 1 of 1 (latest)

rich flowerBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1458829107914739944

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

tawdry frigate
#

these fields should be displayed ON the quote pdf. so I am not talking about metadata

finite rivet
#

hi there, looking into this now. to be clear, these aren't separate line items you're talking about, but just additional text to display on the Quote?

tawdry frigate
#

exactly

#

it would be something like
"Internal Reference Partner": "John Doe"

finite rivet
#

the description field sounds like it may meet your needs, but I'd recommend testing it out in sandbox mode to see

tawdry frigate
#

yeah but thats just rendered as text

#

header and footer is not what we need

#

ok I will try

#

on another note: there seems to be no API call to SEND the quote after it has been finalised via stripe? Is that correct?

finite rivet
#

that's correct, you would convert it to a PDF with this API method and then attach it to an email and send it yourself

tawdry frigate
#

ahh ok. intersting! thanks

finite rivet
#

sure thing, let me know if you have any further questions

tawdry frigate
#

what would be the recommended flow from your site then?

  1. we create a draft quote and finalise it
  2. we send it to the customer
  3. the customer should be able to accept the quote from the email or via link inside the email
  4. the customer would be forwarded to a stripe payment link / checkout (?), note we are using stripe invoices
  5. the customer would finish the quote. I would assume we accept the quote then, create an invoice, finalise it and then notify our backend via webhook?

Do you have an opinion about the flow in which order we should do what etc?

#

sorry but we are not super familiar with this flow and thought maybe you have a best practice guide when exactly we would create the invoice etc.

finite rivet
#

our best practice guide can be found here: https://docs.stripe.com/quotes/create

I don't believe there is a way to have the customer accept the quote and convert it automatically. once the customer responds that they accept the quote, you would manually accept it (either through dashboard or via this API method) which would then convert the Quote into an Invoice

tawdry frigate
#

ah but what i see is that the accept quote method returns an invoice?

"invoice": "in_1Mr7YtLkdIwHu7ixzgJJpJ3L",?

#

so i could automate this?

finite rivet
#

yes, the accept quote method automatically generates an invoice and returns the invoice id

tawdry frigate
#

ok, is the invoice populated from the quote already?

finite rivet
#

yes, based on the line items and other properties you define on the Quote

tawdry frigate
#

ok great

#

ill check it out! Thanks