Sitata / issue_tracking

This repository is used for issue tracking with Sitata's clients
0 stars 0 forks source link

Unable to delete sitata travelers with email address #20

Open seanflynncontact opened 6 years ago

seanflynncontact commented 6 years ago

We are sometimes getting a bad response from Sitata while syncing a traveler. When that happens we don't save traveler id and token. The problem is the traveler gets created on the Sitata end. Because we don't have the traveler id we have no way to delete the traveler on the Sitata end.

astjohn commented 6 years ago

We will have the ability to interact with API under the partner endpoint based on email address within a few hours. We'll deploy it on staging for you to test.

astjohn commented 6 years ago

@seanflynncontact - Can you please try on our Staging servers? Using American Samoa (AS) might be a good way to try as we don't have that country in staging and so it should produce an error when creating the trip and allow you to try that logic flow. Any endpoint under /partner/travellers should now be able to use traveller id or email.

seanflynncontact commented 6 years ago

I added a backlog item to do this task along with other changes needed. Some recent changes to the app are being tested at the moment so my guess is it'll be worked on when the next version is deployed. I'll let you know we it is being worked on. Thanks.