Earlier quoted context omitted.
Absolutely, I get the concern about the docs looking like a placeholder. We're putting a lot of effort into crafting the best SDKs for major languages, so for now, the most comprehensive guide is at https://docs.postack.dev/api-reference/introduction . Regarding A2P messaging, it's pretty standard: create your brand and campaigns, typically with a 72-hour turnaround. We're streamlining compliance by auto-generating l…
Not meant as a nitpick but lots of links to docs are "dead" or redirect to that placeholder. quick example: on your home page both compliance links go nowhere.
Show HN: Postack – SMS API for Developers
11–15 of 15 posts
Re: Show HN: Postack – SMS API for Developers
#12Earlier quoted context omitted.
you should tell us what "per segment" means. Never heard of it. I use twilio mostly.
Twilio also charges per segment, they are probably not transparent. So a segment means 160 characters (It’s a bit more complicated than that). So if you want to send an 320 characters long SMS. You are sending two segments. Let me know if it makes sense?
Re: Show HN: Postack – SMS API for Developers
#13Earlier quoted context omitted.
Twilio also charges per segment, they are probably not transparent. So a segment means 160 characters (It’s a bit more complicated than that). So if you want to send an 320 characters long SMS. You are sending two segments. Let me know if it makes sense?
that makes sense. you should put a * with a defintiion or something
Re: Show HN: Postack – SMS API for Developers
#14Re: Show HN: Postack – SMS API for Developers
#15Are you running on top of twilio? Where do you get your numbers from?
Numbers are sourced from DID wholesalers.