For the API,
POST /api/v2/outbound/contactlists/{contact list id}/export
Do the resulting Download URLs that will be generated have a life span? Will these download URLs 'exist' until the GET method is performed on the same API, or will the download URLs provided in the payload eventually 'die' if not acted upon by the GET in a timely manner? Sorry if the question seems ridiculous, but it is a serious inquiry.
Thank you,
Chris
Hi Chris,
I haven't seen any documentation to suggest the URLs expire after a certain time or downloads so I would assume they will work indefinitely.
Hello,
As a matter of fact, there is a timer/life span on the contact list export.
Apologize for the delay updating this post but I was running a test to make sure I had the correct duration.
The download url will expire after one day (24 hours).
I mean that with POST /api/v2/outbound/contactlists/{contact list id}/export, you will request to prepare an export of the contact list.
When the contact list export is ready (at time T), you can retrieve the download url using GET /api/v2/outbound/contactlists/{contact list id}/export
The download url is pointing at our download service (/api/v2/downloads/xxxxxxxx) [which will allow to be redirected to an AWS S3 repository with a generated token/signature to access the file].
After 24 hours (T + 24 hours), both GET /api/v2/outbound/contactlists/{contact list id}/export and the download url (/api/v2/downloads/xxxxxxxx) will return an HTTP 404.
The file is also automatically deleted from the AWS S3 repository a little bit after (at midnight - GMT time).
Regards,
Jerome,
Makes sense that they would expire, just had no idea when.
Thank you,
Chris
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.