ORVIXIN DEVELOPMENTConnect through the platform’s official login. Your account credentials belong on its website, never in an ORVIX password form.
Channel-aware authorization, metadata preparation and an existing publishing queue are implemented. Uploads and schedules require the correct channel and valid permissions.
Existing-user functionality; public commercial OAuth availability is a separate release requirement.
Instagram Login and a separate OAuth broker have been implemented. A developer test connection has been recorded. Independent connection checks still need stabilization.
TEST ONLY — NOT FOR COMMERCIAL RELEASE. The temporary tunnel is not permanent infrastructure. Public availability requires the appropriate Meta review and access.
The developer application and Sandbox exist. Login Kit and Content Posting API form selections are prepared, but required website information and desktop OAuth implementation are not complete.
Saving application details is not approval, and Sandbox is not public production access.
The commercial design is: choose a platform → official browser login → consent → return to ORVIX. Developer registration, shared secrets and server configuration are the product owner’s responsibility, not a requirement for each customer.