London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
Hello Skyler,
A little more information would help here. But if you need to persist a key for a period of time across multiple requests / jobs that run separate to each other, then look at using the ISynchronizedObjectInstanceCache to persist the API key.
Hello -
I want to start by saying I'm brand new to development and brand new to Optimizely, so bear with me.
We have a custom API that we use for other purposes, and we would like to implement it in our B2B site to retrieve information. Our vision is to create an integration connection that points to our API root URL and stores the
x-api-key
in the header. Then, we want to create subsequent jobs that build off of that connection and target specific endpoints, such asgetCustomers
andgetOrders
.The vision is for it to work the way it does in Postman.
We are using Configured Commerce if that makes a difference.
Thank you.