Sign in with the provider.
Hosted consent, managed provider applications, encrypted credentials and token refresh. Your users don’t need to create OAuth apps.
Managed connections · Developer preview
Your users sign in. Your application gets a connection ID.
pxy handles authorization while you call the APIs you know.
# A human approves the account in their browser
$ pxy connect gmail --external-user user_123
# Call the provider through that connection
$ pxy proxy CONNECTION_ID GET /gmail/v1/users/me/profileHosted consent, managed provider applications, encrypted credentials and token refresh. Your users don’t need to create OAuth apps.
Methods, paths, query strings and payloads stay familiar. Forward uploads, downloads and streaming responses through one transport.
Connections belong to a project, environment and external user. Choose a connection explicitly, with scoped access and durable lifecycle state.
Build the integration. Keep the interface.
pxy serves independent applications through company-owned managed registrations. Each provider becomes available after its required setup, review and live validation.
Talk to the team →