Activate account

Activate your account

Create a FastPix account and start building your product.

Get authentication credentials

Make API requests to FastPix with access tokens.

Set up permissions

Allow to create and modify media or limit to read-only.

Activate your account

Before you can make API requests to FastPix, you need an active account and valid authentication credentials.

Sign up: If you don’t already have a FastPix account, create one here.
Access level: Make sure your account has admin privileges—only admins can create and manage API Access Tokens.

Once your account is ready, follow the steps below to generate your credentials.

Get your Access token ID and Secret Key

FastPix uses Access Tokens to authenticate API requests. These tokens serve as your API credentials, granting secure access to FastPix endpoints. All requests must include a valid Access Token and Secret Key via HTTP Basic Auth headers.

• Login to your FastPix dashboard
• Navigate to Org Settings > Access Tokens
• Click on Generate new token

As a next step, a pop-up will appear with required inputs to create your new Access Token.

• Add your Access Token name
• Select the Workspace where you want to generate a new Access Token.
• Give permissions as per the purpose of using the Access Token.
• Next, click the Generate access token button

This action will generate your new Access Token ID and Secret Key.

PLEASE NOTE

For security reasons, FastPix only shows the Secret Key once. Download it immediately in a (.env) file or store it securely. If you lose the key, you’ll need to create a new token.

The Access Token ID and Secret Key you receive act like a key-pair, allowing you to access FastPix APIs that require basic authentication.

The Access Token ID serves as the username, while the Secret Key functions as the password.

How authentication works

FastPix uses HTTP Basic Auth to verify each API request.

To authenticate:

1. Combine the Access Token ID and Secret Key as username:password
2. Base64 encode the string
3. Add it to the Authorization header

Example header format:

Authorization: Basic base64(username:password)

Most HTTP clients and libraries will handle this for you.

Example request with cURL

Here’s an example of authenticating a request:

curl -X POST 'https://v1.fastpix.io/on-demand'
   --user {Access Token ID}:{Secret Key} \
   -H 'Content-Type: application/json' \
   -d '{
   "inputs": [
      {
         "type": "video",
         "url": "https://static.fastpix.io/sample.mp4",
      }
   ],
   "accessPolicy": "public"
}'

PLEASE NOTE

You can handle the base64 encoding of the username and password in your server-side code, allowing the library to manage the header details.

Access token permissions

Make sure your token has the right permission level:

• Read and write permissions:
  If you need to create and modify resources (e.g., media, direct uploads, live streams), ensure your Access Token has both read and write permissions.

• Read-only permission:
  If your code primarily involves GET requests without creating resources, limit the Access Token to read-only permissions.

Selecting workspace for access token

Access tokens are workspace-specific. For example:

• A development token is meant for testing and experimentation and is not valid for requests in a production workspace.

• A production token is valid for live requests in a production environment and similarly can’t be used for a development workspace.

When generating an Access Token, ensure it aligns with your intended use case. Mixing up tokens could lead to unexpected results!

Revoke access token

In the unfortunate event of a leaked secret key (due to a security breach or accidental exposure), immediate action is necessary. Revoke the corresponding Access Token promptly. You can do this from the Org Settings page: Access Tokens. By revoking the token, you prevent unauthorized access and maintain the integrity of your FastPix account.

Admin-only access

Only admins can view and manage Access Tokens in your organization. Regular members won’t see this section in the dashboard. Admins are responsible for:

• Generating tokens
• Managing permission scopes
• Revoking compromised tokens