payram-auth

To authenticate with a PayRam instance using JWT bearer tokens, you log in with your email and password to obtain an access token, then include that token in the authorization header for subsequent API calls. This enables secure merchant dashboard access.

When your merchant API token expires and returns a 401 error, you should use the token refresh flow to request a new access token using your refresh token. This keeps your session alive without requiring you to re-enter your login credentials.

Yes, you can extract a JWT bearer token from your browser session for automated PayRam workflows. This allows agents and automated scripts to securely access merchant dashboard APIs for analytics, payouts, and payments without manual login steps.

Yes, PayRam authentication supports automatic token refresh for long-running API workflows. The system enforces token lifecycle requirements and automatically refreshes expired tokens, ensuring continuous access to analytics and payment endpoints without interruption.

Handling 403 forbidden responses from the PayRam merchant API involves checking user permissions and token validity. The authentication skill provides clear guidance for troubleshooting these common 401/403 errors, ensuring proper access rights for the requested endpoints.

To securely log out and terminate an active PayRam API session, you use the documented logout workflows provided by the authentication skill. This ensures your JWT bearer token is properly invalidated, preventing unauthorized access to your merchant account.