Skip to content
NOWScale
Search the docs
Open NOWScale

Quickstart

Create an API key, check it, and schedule your first post.

1. Create a key

In NOWScale, open Settings, choose your Workspace and open API keys. Select Create key, give it a name, pick what it can do (the Publishing preset covers this guide) and copy the key. It is shown once.

Keep the key on your server, in an environment variable:

export NOWSCALE_API_KEY="ns_live_..."
Never put a key in a browser, a mobile app or a public repository. Anyone with the key can act as it.

2. Check the key

GET /v1/me returns the key, who it acts as and your plan's limits.

curl https://api.nowscale.com/v1/me \
  -H "Authorization: Bearer $NOWSCALE_API_KEY"
{
  "object": "api_key",
  "kind": "workspace",
  "scopes": ["accounts:read", "media:write", "posts:write", "posts:publish"],
  "acting_as": { "type": "workspace" },
  "workspace": { "id": "...", "name": "Studio", "type": "business" },
  "limits": { "requests_per_minute": 300, "active_keys": 25, "webhook_endpoints": 16, "sandboxes": 5 }
}

3. Find a Project and an account

Posts belong to a Project and publish to its connected accounts.

curl "https://api.nowscale.com/v1/projects" -H "Authorization: Bearer $NOWSCALE_API_KEY"
curl "https://api.nowscale.com/v1/accounts?project_id=PROJECT_ID" -H "Authorization: Bearer $NOWSCALE_API_KEY"

4. Schedule a post

Send an Idempotency-Key with every create, so a retry never makes a second post.

curl https://api.nowscale.com/v1/posts \
  -H "Authorization: Bearer $NOWSCALE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: launch-2026-12-01" \
  -d '{
    "project_id": "PROJECT_ID",
    "title": "We are live",
    "caption": "Our new collection is out today.",
    "media_ids": ["MEDIA_ID"],
    "scheduled_at": "2026-12-01T15:00:00Z",
    "targets": [{ "account_id": "ACCOUNT_ID" }]
  }'

The response is the post, with one target per account. Each target's status moves from pending to published (or failed with an error_code). Follow it with GET /v1/posts/{post_id} or, better, a webhook.

Next steps