Authentication
How to authenticate with the Productsup Stream API using Personal Access Tokens.
The Stream API authenticates every request with a Personal Access Token (PAT) sent as a bearer token.
Your main Productsup contact can arrange Stream API access, issue additional tokens, and revoke existing ones.
The following request lists your streams. It uses the Authorization: Bearer <token> header format:
curl --location --request GET 'https://stream-api.productsup.com/streams/124773' \
--header 'Authorization: Bearer <token>'Stream API authentication layer is set up based on the concept of PAT. The The Productsup platform links PATs to user accounts. A PAT currently grants full access; there are no finer-grained permissions.
Each request you make to the Stream API needs authentication. To receive authentication, you must send an authorization header with a bearer token. The following is an example of the header format:
Authorization: Bearer <token>
Unified authentication
The Stream API and the Platform API use separate tokens. Some Platform API endpoints, however, support unified authentication — your Stream API Personal Access Token works on them, so a stream integration does not need a second set of credentials.
Endpoints that support unified authentication:
- Process — trigger an import of stream data into a site
- Site stream data sources — link a stream to a site
Both appear in Getting started. See Platform API authentication for the Platform API side.
How is this guide?