Finalize the API data transfer from dntrade to wordpress

#1 Additionally, what we noticed from the previous volume of changes: There are several clients who booked "Discovery Calls," but did not receive the invitation link from Calendly, just like us. Furthermore, the event did not appear in our MS Outlook calendar. This was set up initially. Can you fix this? The last two times we sent emails ourselves to provide clients with the meeting link. Please connect the MS Outlook calendars at sebastian leap-key.com and mj leap-key.com to Calendly. And send the confirmations for booked meetings to these same email addresses. #2 Another similar issue concerns invoices from WIX. I see on WIX that the last invoice has number 5, but there should be two more: #6 and #7. WIX was set up to create an invoice and send it to the client's email address and to our email address (sebastian leap-key.com), but this is not happening. It is important that both clients and we receive invoices directly. Exceptions will be those products with individual prices, for which we will use WIX to generate invoices. - The prices for product #4 are set individually, so I need to issue invoices for them. Products #1, 2, 3 have fixed prices, and invoices for them can be generated automatically. - I tried to go through the entire process by booking a meeting for products #1, 2, 3 from my personal email address svuinovich gmail.com, but I did not receive an invoice. It seems I received an email with confirmation of the booked meeting. I don't remember now. - Confirmation and invoice should be sent to the client, as well as to the addresses sebastian leap-key.com and mj leap-key.com. Invoices were not sent to either Sebastian or MJ from Leap Key, nor to me as a client at my personal email address.

I need an online casino, a website or a Telegram app, it doesn't matter what options are available, please suggest. I only work through the website and without prepayments, prices up to $1000.

Below is an example of a detailed technical specification for the development of a mobile application. Text composition Technical specification Project Mobile application for random communication (roulette) Platforms: Android iOS 1. Purpose of the project Create a modern mobile application for dating, communication, and finding conversation partners based on random selection (Chat Roulette), with the ability to filter users by specified criteria. The application must support: text chat; voice chat; video chat; instant switching to the next conversation partner; search by interests; search by country; search by language; search by gender; search by age; advanced filters; moderation system; administrative panel. 2. Types of communication Text chat Features: message exchange; sending Emoji; GIF; stickers; photos; videos; documents; voice messages; message deletion; message editing; reply to message; forwarding messages; pinning messages. Voice chat Features: call to one user; random voice partner; Next switch; microphone mute; volume adjustment; call recording (if permitted); noise cancellation; HD Voice. Video chat Features: Full HD 2K 4K (if device supports) Functions: camera switching; background blur; virtual background; video off; screen sharing; recording; screenshot; picture-in-picture mode; instant Next switch. 3. Roulette principle The user presses the button Start After which the system automatically selects a random conversation partner. There are buttons Next Pause Stop If there are no matches, a message is displayed "Searching for a partner..." 4. Search filters Age 18–25 25–35 35–45 45+ Gender male female any Country Any country in the world City Optional Language All major languages Interests music movies travel sports programming cars games animals medicine business politics education any custom tags Online currently online recently online Type of communication text voice video 5. Registration Registration methods Email Google Apple ID Facebook Telegram phone number anonymous mode Verification Email SMS CAPTCHA 6. User profile Photo Video Name Nickname Age Gender Country City Interests Languages Description Status Registration date Last online Verification Rating 7. Personal account Communication history Favorite users Black list Settings Notifications Premium subscription Purchases Payment history 8. Premium No ads Priority search Region selection Advanced filters Unlimited likes Unlimited switches HD video VIP badge Invisible mode 9. Monetization Subscription One-time purchases VIP Gifts Coins Advertising 10. Administrative panel User management Blocking Deletion Photo moderation Video moderation Message moderation Viewing complaints Statistics Online Income Payments Push notifications News Banners Application settings Logs Backup 11. Complaint system Report Reasons: spam fraud insults pornography violence minors advertising other 12. Security SSL HTTPS Message encryption Two-factor authentication CAPTCHA Anti-spam Anti-bot VPN/Proxy detection Automatic moderation AI moderation 13. Push notifications New message Missed call New partner Response to complaint News Updates 14. Technologies Frontend Flutter or React Native Backend Node.js NestJS Database PostgreSQL Redis File storage Amazon S3 Video and voice WebRTC Push Firebase Cloud Messaging Apple Push Notification Service Admin panel React Vue.js 15. Performance Time to find a partner up to 3 seconds. Support for at least 1,000,000 registered users. Up to 100,000 users online simultaneously. 16. Additional features Real-time message translation Voice translation AI assistant Automatic speech recognition Automatic subtitles Augmented reality (AR) masks Background blur Virtual rooms Group video chats Streaming Create your own rooms Invite friends Profile QR code Dark and light themes Multilingual interface Built-in analytics system 17. Compliance requirements The application must comply with the requirements of Google Play and Apple App Store, as well as ensure the protection of personal data (GDPR) and support user consent for data processing. This technical specification serves as a basis for commercial development. If necessary, it can be expanded into a full document of 100–150 pages with UX/UI prototypes, database architecture, API, screen layouts, user roles, moderation system, monetization, AI matching of partners, and detailed descriptions of each section.

Landing page in 3 languages - English, German, and Czech. Business - manufacturing and installation of ventilation systems. Main blocks - there is a vision of design and content, there is a layout. Version - desktop and mobile. SEO setup - needed, we will agree after the design is finalized.

A separate CRM system needs to be developed for the centralized processing of all retail orders from various sales channels (Prom, Rozetka, own websites, and manual orders). Main requirements: A unified order registry from all sources, preserving information about the source and its status. A separate internal CRM status that operates independently of the status on the marketplace or website, with two-way synchronization of statuses where supported. Flexible integration with 1C: for each source, the administrator can separately enable or disable automatic order export. Integration with carriers for automatic creation of shipping documents, saving their numbers in the CRM, and transmitting the shipping document numbers to Prom and Rozetka. Integration with Checkbox for creating receipt projects, using customizable payment method matching, with subsequent fiscalization control. Support for manual order creation (phone, Viber, Telegram, Direct, etc.) with a complete subsequent processing cycle through the CRM. All API keys and integration settings must be managed by the administrator through the CRM interface without the involvement of a programmer. A complete action log and integration logging for system operation control. Main goal The manager must be able to fully process orders in one CRM interface — from receiving the order to creating a document in 1C, shipping document, receipt project, and completing the order, without the need to access the cabinets of Prom, Rozetka, websites, carriers, or Checkbox.