General Info What I'm building: Connecting the PayPal toolkit to an agent, using our own live PayPal REST API credentials (S2S OAUTH2 / client-credentials). What's not working: Creating the auth config fails on submit — it never gets created. Steps to reproduce: Dashboard → PayPal toolkit → Create Auth Config Authentication Method: S2S OAUTH2 Paste live Client ID + Client Secret, set Environment = live, leave Scopes empty Click Create Paypal Auth Config → 400 error Searched first: No matching open/closed GitHub issues or forum posts (token endpoint hostname, fixed domain suffix, ConnectedAccount_BadRequest, paypal all return nothing). Failed on auth-config creation submit. Full error: 400 {"error":{"message":"Token endpoint hostname templates must preserve a fixed domain suffix in production and foundry environments.","code":600,"slug":"ConnectedAccount_BadRequest","status":400,"request_id":"f899946a-3a03-49e8-8bdd-6c87243ce224","suggested_fix":"Keep the provider domain outside template placeholders, for example https://{{subdomain}}.example.com/oauth/token."}} There is no token-endpoint field in the auth-config form, so this template appears to be internal to the PayPal toolkit. Screenshots available on request. Composio web dashboard (no SDK involved — reproduced entirely in the UI) Org/project: appy-ai-aaron Browser OS: macOS Auth & Credentials Using our own PayPal REST credentials (not Composio defaults). PayPal shows "Composio Managed App Available? No", so custom credentials are the only path. Credentials independently verified working: POST https://api-m.paypal.com/v1/oauth2/token with grant_type=client_credentials returns HTTP 200 with a valid token + full scopes — so this is not a credential problem. This looks like a defect in the PayPal toolkit's live token-endpoint template failing the production fixed-domain-suffix validation. Can the toolkit team take a look, or advise a workaround? Support ticket: support/th_01KVQXSMRM60TMARARWJD7P9YN

Hi there, Thanks for the very thorough writeup, your diagnosis is right: this isn't a credential problem. The error is coming from validation on our side, not from PayPal or anything you entered. For PayPal's S2S OAUTH2 setup, the toolkit currently builds the token endpoint with the entire hostname as a template value, and our production environment rejects a fully templated hostname, so the auth config 400s before your credentials are ever used. This is why there's no token-endpoint field in the form for you to adjust, and it affects both the Live and Sandbox settings. We've confirmed this on our side and logged it internally as a toolkit defect. I don't have a timeline to share yet, and unfortunately there isn't a reliable self-serve workaround since the template is internal to the toolkit. Just reply here if anything changes on your end or you'd like us to flag your project when it's addressed. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.