Accounts

An account is a single platform presence: a TikTok or Instagram handle: owned by a creator. Tracking configuration (the handle, tracking_mode, and the tracked date window) lives on the account, and videos hang off accounts. Plan limits count accounts, since accounts are what actually get scraped. Deactivated accounts don't count.

Account fields#

Deactivation#

deactivation is null while an account is active. Once an org admin deactivates the account, or its creator, it is:

The raw columns (deactivated_at, deactivated_by, deactivated_via_cascade, deactivation_video_choice, deactivation_reason) are also returned. Prefer deactivation.

GET/api/v2/accounts#

List accounts across your organization.

curl -H "Authorization: Bearer tga_<key>" \
  "https://www.trackagoat.com/api/v2/accounts?project_id=<uuid>&platform=instagram"

Query parameters#

Returns a paginated array of account objects.

GET/api/v2/creators//accounts#

List all accounts belonging to a single creator (ordered oldest first).

curl -H "Authorization: Bearer tga_<key>" \
  https://www.trackagoat.com/api/v2/creators/<uuid>/accounts

Returns an array of account objects. 404 if the creator doesn't exist or isn't in your org.

POST/api/v2/creators//accounts#

Add a platform account to an existing creator and dispatch a scrape. Requires the write scope. Enforces the per-org account limit.

If the creator is deactivated, the new account is deactivated with them, with the same choices (deactivation.via_creator: true), and comes back when the creator is reactivated. If you add the handle of an account that was removed while it was deactivated, that is a fresh add: the account comes back active (deactivation: null), its frozen or stopped videos are tracked again (views they gained in the meantime are still not paid), and any payout pause it started ends.

curl -X POST \
  -H "Authorization: Bearer tga_<key>" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"platform": "instagram", "handle": "charli"}' \
  https://www.trackagoat.com/api/v2/creators/<uuid>/accounts

Body#

Responses#

GET/api/v2/accounts/#

Get a single account.

curl -H "Authorization: Bearer tga_<key>" \
  https://www.trackagoat.com/api/v2/accounts/<uuid>

Returns an account object. While the account is deactivated, deactivation also carries video_counts. 404 if not found.

PATCH/api/v2/accounts/#

Rename the handle or change tracking configuration. At least one field is required. Requires the write scope. Changing the handle dispatches a re-scrape of the account's profile and videos.

curl -X PATCH \
  -H "Authorization: Bearer tga_<key>" \
  -H "Content-Type: application/json" \
  -d '{"handle": "charlidamelio", "tracking_mode": "selective"}' \
  https://www.trackagoat.com/api/v2/accounts/<uuid>

Body#

Returns the updated account object. 404 if not found.

DELETE/api/v2/accounts/#

Soft-delete an account (its history and videos are preserved). This removes the account; it can't be undone through the API, but you can add the handle again. To pause it instead, deactivate it. Requires the write scope.

curl -X DELETE \
  -H "Authorization: Bearer tga_<key>" \
  https://www.trackagoat.com/api/v2/accounts/<uuid>

Returns { "deleted": true }.

POST/api/v2/accounts//scrape#

Trigger a manual scrape for a single account. Consumes from the org's daily manual-scrape quota. Requires the write scope.

curl -X POST \
  -H "Authorization: Bearer tga_<key>" \
  -H "Content-Type: application/json" \
  -d '{"job_type": "video_stats"}' \
  https://www.trackagoat.com/api/v2/accounts/<uuid>/scrape

The response echoes { job_type, account_id, job_id }.

POST/api/v2/accounts//deactivate#

Deactivate one account, for example a creator's Instagram while you keep tracking their TikTok. trackagoat stops looking for its new posts and updating its profile, and hides it from lists unless you ask for status=deactivated. The creator and their other accounts are not changed. The account keeps its campaign membership and you can reactivate it. While deactivated, it doesn't count toward max_accounts_per_org. To deactivate a whole creator, use POST /api/v2/creators/{id}/deactivate.

Requires the write scope, and the member the key acts as must be an org admin (403 insufficient_role otherwise). Accepts an Idempotency-Key header.

curl -X POST \
  -H "Authorization: Bearer tga_<key>" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"videos": "stop_tracking", "reason": "Personal account"}' \
  https://www.trackagoat.com/api/v2/accounts/<uuid>/deactivate

Body#

Response#

{
  "data": {
    "account": {
      "id": "uuid",
      "platform": "instagram",
      "handle": "someuser",
      "deactivation": {
        "deactivated_at": "2026-10-12T09:30:00Z",
        "deactivated_by": "uuid",
        "video_choice": "stop_tracking",
        "reason": "Personal account",
        "via_creator": false
      }
    },
    "result": { "account_id": "uuid", "creator_id": "uuid", "videos_frozen": 0, "videos_stopped": 14, "payouts": null }
  },
  "error": null,
  "meta": null
}

account is the full account object after the change (shortened here). result.creator_id is null for an account without a creator. result.payouts is pause or keep when the payout question applied, otherwise null.

POST/api/v2/accounts//reactivate#

Reactivate a deactivated account. New posts follow its tracking mode again, and a full check for posts made while it was deactivated runs with the next discovery cycle (usually within 12 hours). An account whose creator is deactivated can't be reactivated on its own: reactivate the creator with POST /api/v2/creators/{id}/reactivate. If the creator's payouts were paused, reactivating any one of their accounts starts them again from the next period.

The account counts toward max_accounts_per_org again, so reactivating needs room under the limit. If it doesn't fit, the call fails with 402 limit_reached and nothing changes.

Requires the write scope, and the member the key acts as must be an org admin. Accepts an Idempotency-Key header.

curl -X POST \
  -H "Authorization: Bearer tga_<key>" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"missed_posts": "ignore", "existing_videos": "keep"}' \
  https://www.trackagoat.com/api/v2/accounts/<uuid>/reactivate

Body#

Response#

{
  "data": {
    "account": { "id": "uuid", "deactivation": null },
    "result": {
      "account_id": "uuid",
      "creator_id": "uuid",
      "videos_resumed": 0,
      "videos_stopped": 0,
      "missed_posts_updated": 2
    }
  },
  "error": null,
  "meta": null
}

POST/api/v2/projects//accounts/bulk-deactivate#

Deactivate up to 100 accounts in one project, each exactly like POST /api/v2/accounts/{id}/deactivate, with one videos choice for all of them. Requires the write scope, and the member the key acts as must be an org admin. Accepts an Idempotency-Key header.

curl -X POST \
  -H "Authorization: Bearer tga_<key>" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"account_ids": ["<uuid1>", "<uuid2>"], "videos": "keep_tracking"}' \
  "https://www.trackagoat.com/api/v2/projects/<projectId>/accounts/bulk-deactivate"

Body: account_ids (1 to 100 UUIDs), videos, payouts and an optional reason. payouts is needed when the batch includes the last active account of a creator with payout structures assigned.

{
  "data": {
    "done": [{ "account_id": "uuid", "creator_id": "uuid", "videos_frozen": 0, "videos_stopped": 0 }],
    "skipped": [{ "id": "uuid", "reason": "not_found" }],
    "done_count": 1,
    "skipped_count": 1
  },
  "error": null,
  "meta": null
}

Skipped reasons: not_found (unknown, removed, its creator removed, or in another project), already_deactivated, or payouts_required (with assignments: the batch would leave a creator with payout structures assigned and no active account, and payouts was left out; every account of that creator in the batch is skipped). The rest go ahead. 404 if the project isn't in your org.

POST/api/v2/projects//accounts/bulk-reactivate#

Reactivate up to 100 accounts in one project, each exactly like POST /api/v2/accounts/{id}/reactivate, with one set of choices for all of them. Requires the write scope, and the member the key acts as must be an org admin. Accepts an Idempotency-Key header.

curl -X POST \
  -H "Authorization: Bearer tga_<key>" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"account_ids": ["<uuid1>", "<uuid2>"], "missed_posts": "inbox"}' \
  "https://www.trackagoat.com/api/v2/projects/<projectId>/accounts/bulk-reactivate"

Body: account_ids (1 to 100 UUIDs), missed_posts, existing_videos and an optional note. The response has the same done, skipped, done_count and skipped_count shape, and each done item is a reactivation result. Each account that can't be reactivated is returned in skipped with a reason, and the rest go ahead:

GET/api/v2/accounts//stats#

Get an account's follower/stat snapshot history. This series is append-only: snapshots are only ever inserted, never updated.

curl -H "Authorization: Bearer tga_<key>" \
  "https://www.trackagoat.com/api/v2/accounts/<uuid>/stats?from=2026-01-01&to=2026-03-31"

Query parameters#

Response fields#

Each element of the returned array: