Authentication

The Timelines Global API uses Bearer token authentication. Every request must include your API token in the Authorization header.

Getting your API token

Go to app.timelines.global

Open API settings

Navigate to Integrations → Public API

Copy your token

Your token is displayed on this page. Click Copy to copy it.

Using your token

Include the token in the Authorization header of every request:

Authorization: Bearer YOUR_API_TOKEN

Example request

curl -X GET "https://app.timelines.global/integrations/api/chats" \
  -H "Authorization: Bearer 4d2d0239-e28c-4f4a-8a4d-3a3ca40056b8"

const response = await fetch('https://app.timelines.global/integrations/api/chats', {
  headers: {
    'Authorization': 'Bearer 4d2d0239-e28c-4f4a-8a4d-3a3ca40056b8'
  }
});

import requests

response = requests.get(
    'https://app.timelines.global/integrations/api/chats',
    headers={'Authorization': 'Bearer 4d2d0239-e28c-4f4a-8a4d-3a3ca40056b8'}
)

Token security

Your API token provides full access to your workspace. Treat it like a password.

Best practices

Use environment variables

Never hardcode tokens in your source code. Use environment variables:

export TIMELINES_GLOBAL_API_TOKEN="your-token-here"

const token = process.env.TIMELINES_GLOBAL_API_TOKEN;

Don't commit tokens to Git

Add your environment files to .gitignore:

.env
.env.local
.env.*.local

Rotate tokens if compromised

If you suspect your token has been exposed, generate a new one immediately from the API settings page.

Use server-side only

Never expose your API token in client-side code (browsers, mobile apps). Always make API calls from your backend server.

Error responses

401 Unauthorized

If your token is missing or invalid:

{
  "status": "error",
  "message": "Invalid or expired token"
}

Common causes:

Missing Authorization header
Token copied incorrectly (check for extra spaces)
Token has been regenerated

403 Forbidden

If your token is valid but lacks permission:

{
  "status": "error",
  "message": "Access denied"
}

Common causes:

Attempting to access resources from another workspace
Feature not available on your plan

Token scope

Your API token has access to:

Resource	Access
Chats	Read & Write
Messages	Read & Write
Labels	Read & Write
Files	Read & Write
WhatsApp Accounts	Read only
Webhooks	Read & Write

All operations are scoped to your workspace. You cannot access data from other Timelines Global accounts.

Getting Started

Use Cases

Authentication

Authentication

Getting your API token

Using your token

Example request

Token security

Best practices

Error responses

401 Unauthorized

403 Forbidden

Token scope

​Authentication

​Getting your API token

​Using your token

​Example request

​Token security

​Best practices

​Error responses

​401 Unauthorized

​403 Forbidden

​Token scope

Authentication

Getting your API token

Using your token

Example request

Token security

Best practices

Error responses

401 Unauthorized

403 Forbidden

Token scope