If your team integrates with the Upfluence API, you can now authenticate using client credentials instead of your email and password. This is the standard way to handle machine-to-machine authentication, and it means you don't need to store personal login details in your integration or manually refresh tokens.
Create your client credentials
Go to Settings and open the API access tab.
Click Create client credentials.
Enter a Credential name (up to 255 characters) so you can identify this credential later, for example
my-api-client.Click Create credentials.
Once created, you'll see your client ID and client secret. Click the copy icon next to each to copy them to your clipboard.
Important: the client secret is shown only once. Make sure to copy and store it somewhere secure before closing this window, you won't be able to retrieve it again. If you try to close the window without copying it, you'll get a confirmation prompt asking if you're sure.
Use your credentials to get an access token
Once you have your client ID and secret, request an access token from the existing token endpoint using the client_credentials grant type:
POST https://[api-base-url]/token { "grant_type": "client_credentials", "client_id": "your_client_id", "client_secret": "your_client_secret", "token_lifetime": 900 }The response includes your access token, its type, and how long it's valid for:
{ "access_token": "eyJhbGciOiJIUzI1NiJ9...", "token_type": "bearer", "expires_in": 900 }This grant type doesn't require two-factor authentication, even if 2FA is enabled on your account, so it's fully suited for automated, unattended integrations.
Manage existing credentials
Your API access page lists every client credential you've created, including:
The credential name
The client ID (with a copy button)
When it was created
When it was last used (shows
–if it's never been used)
There's no limit to how many client credentials you can create.
Revoke access
If a credential is compromised or no longer needed, you can revoke it immediately:
From the API access list, find the credential and click Revoke access.
Confirm in the dialog that appears.
Revoking a credential immediately invalidates all access tokens generated with it. Other credentials and their tokens are not affected, and this action can't be undone.