Your X API Key (Consumer Key) from the X Developer Portal. Alternative to the twitterApiKey body parameter. When provided, the generated JWT URL will use your X Developer App for OAuth linking.
Your X API Secret (Consumer Secret) from the X Developer Portal. Alternative to the twitterApiSecret body parameter. Required when X-Twitter-OAuth1-Api-Key is provided.
Recommended: Pass your X credentials via headers (X-Twitter-OAuth1-Api-Key and X-Twitter-OAuth1-Api-Secret) for consistency with all other Ayrshare API endpoints. The twitterApiKey and twitterApiSecret body parameters are still supported for backward compatibility.
Automatically logout the current session. Recommend not to use in production since it affects the performance.See Automatic Logout of a Profile Session for more information.
Specify a URL to redirect to when the “Done” button or logo image is clicked. The URL will be automatically shortened in the returned JWT url. Redirect the origin opener window by adding the query parameter origin=true to the redirect URL.
If the private key is base64 encoded, set to true.Encode the private.key file in base64 and pass the single line String in the privateKey field.E.g in Linux: cat private.key | base64
Send a Connect Accounts email with a link for users to directly access their social linkage page.See Connect Accounts Email for more information.
When you include your X API credentials, the generated JWT URL will initiate OAuth linking using your own X Developer App. Your end-users will see your app name on the X consent screen.
Required: Before using this feature, you must add these callback URLs to your X Developer App settings (under Authentication settings > Callback URI / Redirect URL):
https://profile.ayrshare.com/social-accounts
https://app.ayrshare.com/social-accounts
Without these, the OAuth flow will fail with a 403 Callback URL not approved error.