0bull API | 0bull

Automate your phone farm over HTTP: manage TikTok, Instagram and YouTube accounts, publish videos to any of them, and drive phones directly.

Platforms

Accounts and submissions both take a platform of tiktok, instagram or youtube. It defaults to tiktok everywhere, so a client written before this parameter existed keeps working unchanged.

Account ids are UUIDs and identify their own platform, so GET, PATCH and DELETE on /v1/accounts/{account} need nothing but the id.

What differs per platform:

TikTok — username, password and slot are required when creating an account.
Instagram and YouTube — only handle is required. Credentials are optional: supply them and the account is queued for login on the phone; leave them out and it is recorded as already signed in on the handset.
Captions — TikTok and Instagram take a caption of up to 2200 characters. YouTube takes a title of up to 100, because the flow types it into the Short's title field. A title is required for YouTube: an untitled Short is named after the date it was posted.

Authentication

Every request needs an API token. Create one under Settings → API tokens on 0bull.net and copy it straight away — the token is shown once and cannot be retrieved later. If you lose it, revoke it on that same page and create another.

Send the token as a bearer token on every request:

Code
Authorization: Bearer YOUR_TOKEN

A token carries the full access of the account that created it, and only ever sees that account's own data. Revoking it cuts off every client using it immediately.

Conventions

Rate limit — 60 requests per minute. Over that you get a 429 with a Retry-After header.
Pagination — list endpoints return one page at a time; pass ?page=2 to walk through the rest.
Async work — anything that touches a phone or a platform is queued rather than done inline. The call returns as soon as the work is accepted, so poll the account or submission to see how it actually turned out.
Errors — failures come back as JSON with a message; invalid input adds a field-keyed errors object.

Working from an AI assistant?

0bull also exposes an MCP server covering the same ground, with no token to create or rotate. Set it up under Settings → MCP server.

Platforms

Accounts and submissions both take a platform of tiktok, instagram or youtube. It defaults to tiktok everywhere, so a client written before this parameter existed keeps working unchanged.

Account ids are UUIDs and identify their own platform, so GET, PATCH and DELETE on /v1/accounts/{account} need nothing but the id.

What differs per platform:

TikTok — username, password and slot are required when creating an account.

Instagram and YouTube — only handle is required. Credentials are optional: supply them and the account is queued for login on the phone; leave them out and it is recorded as already signed in on the handset.

Captions — TikTok and Instagram take a caption of up to 2200 characters. YouTube takes a title of up to 100, because the flow types it into the Short's title field. A title is required for YouTube: an untitled Short is named after the date it was posted.

Authentication

Send the token as a bearer token on every request:

Code

Authorization: Bearer YOUR_TOKEN

A token carries the full access of the account that created it, and only ever sees that account's own data. Revoking it cuts off every client using it immediately.

Conventions

Rate limit — 60 requests per minute. Over that you get a 429 with a Retry-After header.

Pagination — list endpoints return one page at a time; pass ?page=2 to walk through the rest.

Async work — anything that touches a phone or a platform is queued rather than done inline. The call returns as soon as the work is accepted, so poll the account or submission to see how it actually turned out.

Errors — failures come back as JSON with a message; invalid input adds a field-keyed errors object.