How can I set the expiration time for twilio's authy OTP sent via SMS. I don't see how to change the default expiration time anywhere in the docs. I would like the OTP to remain valid for 30 min.
Twilio developer evangelist here.
I'm afraid you cannot change the expiration time for the OTP with Authy.
30 minutes seems like a riskier length of time to allow for one token to be active. There is some drift with tokens, you don't need to enter it within 30 seconds, but half an hour is not among any recommended lengths of token expiration time.
Related
I implemented auto renewing subscription in my app with grace period. I did code all the logics required to provide subscription service while the grace period but I could not find any way to test the grace period in Sandbox environment. Can someone help me with testing grace period feature in Sandbox environment.
I'm afraid it's impossible on iOS: you'll have to test it directly in production!
If you start implementing In-App Subscriptions on Google Play Store, it will be possible to test the grace period since you'll be able to change your payment method to the "Test card, always declines".
Enabling the billing grace period in App Store Connect doesn't change the expiration date corresponding to the grace period. But, it avoids revenue loss if Apple can recover the subscription within the grace period. See this graphic (explaining the renewal behavior without grace period) and this (explaining it with grace period). The difference is, that when Apple can renew the subscription within the grace period, the billing date doesn't change and therefore you do not lose revenue.
Source
Since the grace period doesn't change the expiration date, it is your responsibility to ensure that users can access the paid content after their subscription expired (when you have the grace period option enabled):
you’ll need to update your entitlement logic to ensure you are providing service to customers within the grace period
Source
Keeping that in mind, it is possible to test the grace period => grant access to your content after the subscription expired.
Unfortunately, without a server, you can't access a field telling you when the grace period ends. Therefore, you have to "calculate" it yourself corresponding to the subscription duration your user has. See this table showing the length of the grace period for each subscription duration.
I have created a Zap to send an SMS to a mobile number every time a new email, with a specific subject, is received.
I've created two tasks:
1st. Zapier Filter, filters the emails by the right subject.
2nd. Twilio send this email as SMS.
I find that it takes up to 10 minutes or more for that email to be sent as an SMS, and time is very relevant in this automation. Is there a way to speed up the process so Twilio sends the SMS as soon as the email arrives and Zapier has filtered it?
I am not 100% sure where us this delay happening. Zapier or Twilio?
Thanks,
Aitor
There is a Twilio You Tube Tutorial which shows you how to set-up email to SMS, this could be another way to set-up the same requirement.
How to forward email to text messages using Twilio and SendGrid
To identify your current issue, you can send the email, record the time, and then check the Twilio Console messaging logs to find the SMS message associted with that email and record the time; then compare the time differences.
This delay is only happening because of the plan you have on zapier.
If you upgrade your plan, their event listeners can run <1 minute, but on the lower tier plans, you can except 5-10 minute delays. Check out their pricing page & look at the update time:
Zapier pricing
If you want this to run faster & don't want to upgrade zapier plans, the option above is a great choice.
Having issues creating a subscription, specifically setting the expirationDateTime field in the beta API.
According to the docs maximum expiration time is '4320 minutes (3 days)' on the contacts resource.
When I make the request, I receive an error message of Subscription expiration can only be 4230 minutes in the future. Obviously this conflicts with their documentation. Now, if I adjust the expirationDateTime attribute I am sending to make a subscription request from 4320 minutes to 4230 minutes, it works as expected.
Is this a documentation issue or a mistype in their API source?
Resources:
https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/resources/subscription
https://developer.microsoft.com/en-us/graph/docs/api-reference/v1.0/resources/subscription
This is an issue in the documentation. It is being updated now. The maximum lifetime is 4230 minutes.
We get the user cancels in the next 30 days from our database and we call to Apple one to one
https://buy.itunes.apple.com/verifyReceipt
We want to call for a list of user cancels in the next 365 days which can be a huge list.
I look for that in the documentation and in google but I couldn't find if there is a limit on the number of requests to Apple.
Does anyone know that?
After contact Apple's support, there are not query limits.
I have this endpoint implemented several months ago and I make a huge number of requests every day without any problem.
It's the only way to verify the status of each receipt because their webhook doesn't seem reliable.
Regarding Getting Started with Twilio Video
both me and the other side will require token form the server, right ?! , will this cost money or the calling video after start (in pricing they Room Participant Programmable Video's Rooms connect your users in a multi-party voice or video session cost $0.01 per hour for one participant ) ,
am not sure about other-name in invitation method meaning the other side token you mean ?! or what
This isn't really the place to talk about pricing, but I'll go ahead and answer it anyway:
The token from the server does not cost anything (you generate that on your own backend for the users to connect). Once you get the access token, you would then connect to the room. Each user that connects to the room will be charged the initial $0.01 charge (the per hour charge).
Example:
Two users talk in a room for 20 seconds: Cost is $0.02.
Two users talk in a room for 59 minutes: Cost is $0.02.
Two users talk in a room for 1.5 hours: Cost is $0.04.
Twilio also has TURN (you can disable this), which would kick-in if the WebRTC peer to peer is not functioning. If you choose to use it, it is charged per GB regionally. Current pricing details for TURN are here.