- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.4k
Add new API V3 connector #1440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new API V3 connector #1440
Conversation
| Dear partner, We apologize for the delay you might be experiencing while we are working on a high volume of connector requests. Rest assured that we are doing everything we can to address this volume. We are taking measures like improving our processes and hiring additional team members to guarantee resolving your connector requests in a timely manner. Please let us know if you have any questions in the meantime. | 
| Hello @Amjed-Ayoub I hope you're doing well. Do you have any update regarding our PR or an ETA for when you'll process it ? Thanks for your help. Regards, | 
| Hi @FloxoS, | 
| Hello @sriyen-msft, Thanks for your review, I've taken into account all your feedbacks. I replaced all my files in previous Tilkee folder, however as it is a major update, it now generates the following error: As we don't have any customer using this previous connector in production, that's not an issue for us to break it. I'm not sure of how we should proceed in such case, can you explain me what to do? Thanks for your help! | 
| Hey @FloxoS. Hope you are doing well. We noticed that you removed some actions from your connector. Four operations have been deleted. We need to make sure that no clients will be affected by these changes. Can you confirm that no connector users will be affected by these operation removals? | 
| Hi @v-eisljami. Let me know if you need more information. Regards, | 
Hello!
We built a new API @Tilkee and we built a new connector based on it.
We will look to deprecate the previous one after this one has been published.
Let me know if I missed something or did something wrong.
Regards,
Florian
When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.
apiDefinition.swagger.json, by runningpaconn validatecommand.apiProperties.jsonhas a valid brand color and doesn't use an invalid brand color,#007ee5or#ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.