Authenticate Wahdx Connection API Requests

Wahdx Connection API requests use an X-API-Key header. Treat this key like a production credential: store it in a trusted backend, serverless function, or private integration layer, never in browser JavaScript or mobile client bundles. This authentication model keeps publishing requests controlled while giving teams a clear path for backend integrations.

Get Started Free View Docs Hub

Required header

Send the API key with each server-to-server request. The key should be loaded from your environment variables or secret manager.

const headers = {
  'X-API-Key': process.env.WAHDX_API_KEY
};

import os

headers = {
    'X-API-Key': os.environ['WAHDX_API_KEY']
}

curl -H "X-API-Key: $WAHDX_API_KEY" "https://api.wahdx.com/api/content/accounts"

Server-side request pattern

Use a backend route, serverless function, or internal worker to call Wahdx Connection. This prevents credentials from being exposed to users.

const API_BASE_URL = 'https://api.wahdx.com';
const API_KEY = process.env.WAHDX_API_KEY;

await fetch(API_BASE_URL + '/api/content/accounts', {
  method: 'GET',
  headers: {
    'X-API-Key': API_KEY
  }
});

import os
import requests

API_BASE_URL = 'https://api.wahdx.com'
API_KEY = os.environ['WAHDX_API_KEY']

response = requests.get(
    API_BASE_URL + '/api/content/accounts',
    headers={
        'X-API-Key': API_KEY,
    },
    timeout=30,
)

response.raise_for_status()
print(response.json())

curl -X GET "https://api.wahdx.com/api/content/accounts" \
  -H "X-API-Key: $WAHDX_API_KEY"

Key handling checklist

Secure key handling reduces risk when building social publishing workflows.

Store API keys in server-side environment variables.
Never place API keys in browser code, public repositories, or mobile bundles.
Rotate keys immediately if a key is exposed.
Route client actions through your backend or server-side proxy.

FAQ

Common questions about this API topic.

Can I use the API key directly from the browser?

No. API keys should only be used from trusted server-side environments so they are not exposed to users.

Which header authenticates requests?

Use the X-API-Key header on each request that calls Wahdx Connection API endpoints.

What should I do if my key is leaked?

Rotate the key immediately and remove the exposed value from code, logs, and public history where possible.

Related docs

Continue with another integration topic.

List Connected Social Accounts with the Public API

Use GET /api/content/accounts to list TikTok, Instagram, Threads, and Facebook accounts connected to a Wahdx Connection workspace using an API key.

Video Requirements for Social Publishing API Workflows

Review recommended video formats, size, duration, aspect ratio, and thumbnail settings for Wahdx Connection publishing workflows.

Photo Carousel Publishing API Guide

Learn how to prepare photo carousel posts, cover images, title fields, and media arrays for Wahdx Connection publishing workflows.

Track Social Post Status with Wahdx Connection API

Check individual or batch post status for social publishing workflows and monitor queued, processing, published, or failed content.