Connected Apps

BETA

Agent Gateway is in BETA, and we're continuing to expand its capabilities. Your feedback helps shape what we build next—reach out to us through Relewise Support.

Connected Apps use OAuth to let an interactive client access Agent Gateway through your My Relewise identity. You sign in to My Relewise, review the client name, and choose whether to approve the connection. The client never needs your My Relewise password or a Personal Access Token.

Before You Connect

You need:

• Access to My Relewise and Use Agent Gateway permission for the Dataset you want to use.
• An enabled Connection Method and the required Allowed Areas.
• An OAuth-compatible client that supports authorization code flow and S256 PKCE.

OAuth is supported for REST and MCP connections. The shared protected resource is https://my.relewise.com/agents, and the authorization server issuer is https://my.relewise.com/agents/oauth.

Connect

Start the connection from your client. The client discovers the Agent Gateway authorization server, registers or resolves its exact client identity, and opens My Relewise for sign-in and consent.

The consent page shows the client name. Review it carefully and approve only a client you recognize.

After approval, the client receives an access token and uses it as a bearer credential. It can call REST endpoints or MCP tools that are enabled for the user, connection, Dataset, and Area.

Manage a Connection

My Relewise records each Connected App separately for each user and exact client identity. You can review its Dataset access, block or unblock it when permitted, and disconnect it.

Disconnecting a Connected App prevents that connection from being used again and does not restore previously revoked credentials. Reauthorize the client to create a new connection. Protocol token revocation and Connected App disconnection are separate actions.

Changes to Dataset access also apply to existing connections. These changes do not grant access that your user or the Dataset's Agent Gateway Configuration does not allow.

Personal Access Tokens

Some clients do not support OAuth. Use a Personal Access Token in those clients and keep it in the client's secure credential storage. OAuth and Personal Access Tokens are alternatives; a Personal Access Token is not required when the client supports Connected Apps.

For connection failures, see Troubleshooting and FAQ.