Permanent token request for API use in ETL processes
I
Ignacio Cofré
Hello AB Tasty team,
I'm working on implementing an ETL process that requires consuming data from its Data Explorer API:
According to current documentation, this call can only be made using the session token available at:
Flagship → Settings → Integrations → Tokens
However, this token expires at the end of the session, which presents an important limitation for automating continuous data extraction and analysis processes.
We need a persistent token (that doesn't expire) or a secure authentication alternative that allows programmatic access to the transaction detail data that we send to the tests. The objective is to mark each sale in our database with the corresponding campaign and variation, which would allow us to generate more detailed reporting for the analytics team regarding the performance and characteristics of each variation in the experiments.
I appreciate if you can guide us on how to enable an appropriate authentication flow for this purpose, or if there is another recommended solution for automating access to this API.
P
Product Team
Hiya Ignacio Cofré, thanks for this post! I have a few more questions for you:
- What is the expected frequency of the ETL process that requires API access?
- Are there any specific security protocols or compliance requirements that need to be considered for the persistent token?
- Can you provide more details on the types of data and reports you aim to generate using the API?
I
Ignacio Cofré
Hello!
I answer your questions
- We generally run our processes every 45 minutes to an hour
- No, I just need the token to not expire (or to expire very rarely)
- basically I need this (attached image), to get the sales (transactionid) that we recorded for each customer (customerid) and the variation (variationid) that the customer was in.