Create a Connect token for a user
Your app will initiate the account connection flow for your end users in your frontend. To securely scope connection to a specific end user, on your server, you retrieve a short-lived token for that user, and return that token to your frontend. See the Connect tokens docs for more information. When using the Connect API to make requests from a client environment like a browser, you must specify the allowed origins for the token. Otherwise, this field is optional. This is a list of URLs that are allowed to make requests with the token. For example:Documentation Index
Fetch the complete documentation index at: https://pipedream.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
A short-lived OAuth access token for server-side requests. Generate one via the Generate OAuth Token flow or automatically when initializing the SDK client.
The environment in which the server client is running
development, production The project ID, which starts with proj_.
^proj_[a-zA-Z0-9]+$Request object for creating a connect token
Your end user ID, for whom you're creating the token
List of allowed origins for CORS
URI to redirect to on error
Token TTL in seconds (max 14400 = 4 hours). Defaults to 4 hours if not specified.
Space-separated scopes to restrict token permissions. Defaults to 'connect:*' if not specified. See https://pipedream.com/docs/connect/api-reference/authentication#connect-token-scopes for more information.
URI to redirect to on success
Webhook URI for notifications
When true, end users may authorize a subset of the app's OAuth scopes; only the app's functional scopes (needed for the post-OAuth test request) are enforced. Defaults to false.
connect token created