Tumblr — how to connect

Posts text to your Tumblr blogs via the API v2 (Neue Post Format). Add your Tumblr OAuth app's consumer key and secret below, then connect with OAuth — each blog on the account is added as a separate channel.

Tumblr uses OAuth2: you first register a developer application to get an app-level consumer key/secret, then each blog owner connects via OAuth to grant posting access.

Before you start

A Tumblr account with at least one blog already created (the OAuth app cannot create a blog for the user — `basic` scope just reads the existing blog list).
A registered Tumblr OAuth app at tumblr.com/oauth/apps, with its OAuth Consumer Key and Secret entered into this integration's config fields (TUMBLR_CLIENT_ID / TUMBLR_CLIENT_SECRET) before starting Connect.
The app's registered Default Callback URL must exactly match the redirect URI this tool sends (scheme, host, path, and trailing slash all matter) — mismatches fail the authorize step before the user even sees a token.
Authorize with the scope `basic write offline_access` — omitting `offline_access` means no refresh_token comes back, so the connection silently stops publishing once the short-lived access token expires (no re-auth prompt, just failed posts).

Step by step

1
Log in and open the Tumblr apps page
Sign in to the Tumblr account that should own the integration, then go to the application registration page.
Open
2
Register a new application
Click Register application and fill in the app name, website URL, and a valid OAuth2 redirect URI (this must exactly match the callback URL this tool gives you).
3
Copy the OAuth consumer key and secret
After registering, copy the OAuth Consumer Key and click Show secret key to reveal the Secret Key.
4
Paste the key and secret into this app
Enter the OAuth Consumer Key as Consumer key and the Secret Key as Consumer secret in the Tumblr integration's config fields here.
5
Connect via OAuth
Click Connect Tumblr in this app and approve access with your Tumblr account; each blog on that account is added as a separate channel automatically.

App keys (set once in Settings)

Consumer key
tumblr.com/oauth/apps → your app → "OAuth Consumer Key". The app's registered callback URL must match this tool's redirect URI exactly.
Consumer secretsecret
Same app → click "Show secret key". Connecting requests basic + write + offline_access so posting keeps working after the token expires.

Good to know

Register the app at tumblr.com/oauth/apps while logged into the Tumblr account (or a blog member account) that should be able to post — the consumer key/secret are tied to that account.
The redirect URI you enter when registering the app must exactly match the callback URL this tool sends, or the OAuth authorize step will fail.
This integration requests scopes 'basic write offline_access'; offline_access is required to get a refresh_token so the connection doesn't need re-authorizing when the access token expires.
If the connected account has no blogs (rare), the tool falls back to the raw Tumblr username as the channel — normally each blog on the account shows up as its own channel.

Troubleshooting

Connect works once, then posts start failing after a few hours/days with 401s and no obvious cause.: The initial OAuth grant didn't include `offline_access`, so no refresh_token was issued. Disconnect and reconnect so the authorize URL requests `basic write offline_access`; verify the token response actually contains a refresh_token before treating the connection as durable.
Token exchange fails immediately with a 401/'unauthorized client' or 400 'invalid_request' during the OAuth callback.: Almost always a mismatched redirect_uri or wrong/rotated Consumer Key or Secret. Confirm TUMBLR_CLIENT_ID/SECRET in config exactly match the app at tumblr.com/oauth/apps, and that the app's registered callback URL is byte-for-byte identical to the redirect_uri this tool sends.
Publish call returns a 2xx-looking response but the post never appears, or returns an `errors` array with a 4xx like 'You do not have permission to post to this blog.': The target blogId (UUID) is stale or belongs to a blog the authenticated user no longer administers (renamed blog, removed member, or wrong blog picked when multiple blogs exist on the account). Reconnect to re-pull the current blog list, and always publish to the blog's UUID rather than its old hostname.
Posting works fine for a while then starts returning 429 Too Many Requests during bursts or bulk backfills.: Tumblr enforces per-consumer-key rate limits (roughly 1,000 calls/hour, 5,000/day per app, shared across all connected blogs using that Consumer Key). Space out scheduled posts and back off/retry on 429 instead of retrying immediately.

Tumblr developer docs

Before you start

A Tumblr account with at least one blog already created (the OAuth app cannot create a blog for the user — `basic` scope just reads the existing blog list).

A registered Tumblr OAuth app at tumblr.com/oauth/apps, with its OAuth Consumer Key and Secret entered into this integration's config fields (TUMBLR_CLIENT_ID / TUMBLR_CLIENT_SECRET) before starting Connect.

The app's registered Default Callback URL must exactly match the redirect URI this tool sends (scheme, host, path, and trailing slash all matter) — mismatches fail the authorize step before the user even sees a token.

Authorize with the scope `basic write offline_access` — omitting `offline_access` means no refresh_token comes back, so the connection silently stops publishing once the short-lived access token expires (no re-auth prompt, just failed posts).

Step by step

Open

Click Register application and fill in the app name, website URL, and a valid OAuth2 redirect URI (this must exactly match the callback URL this tool gives you).

Copy the OAuth consumer key and secret

After registering, copy the OAuth Consumer Key and click Show secret key to reveal the Secret Key.

Paste the key and secret into this app

Enter the OAuth Consumer Key as Consumer key and the Secret Key as Consumer secret in the Tumblr integration's config fields here.

Connect via OAuth

Click Connect Tumblr in this app and approve access with your Tumblr account; each blog on that account is added as a separate channel automatically.

App keys (set once in Settings)

Consumer key

tumblr.com/oauth/apps → your app → "OAuth Consumer Key". The app's registered callback URL must match this tool's redirect URI exactly.

Consumer secretsecret

Same app → click "Show secret key". Connecting requests basic + write + offline_access so posting keeps working after the token expires.

Good to know

Register the app at tumblr.com/oauth/apps while logged into the Tumblr account (or a blog member account) that should be able to post — the consumer key/secret are tied to that account.

The redirect URI you enter when registering the app must exactly match the callback URL this tool sends, or the OAuth authorize step will fail.

This integration requests scopes 'basic write offline_access'; offline_access is required to get a refresh_token so the connection doesn't need re-authorizing when the access token expires.

If the connected account has no blogs (rare), the tool falls back to the raw Tumblr username as the channel — normally each blog on the account shows up as its own channel.

Troubleshooting

Connect works once, then posts start failing after a few hours/days with 401s and no obvious cause.

The initial OAuth grant didn't include `offline_access`, so no refresh_token was issued. Disconnect and reconnect so the authorize URL requests `basic write offline_access`; verify the token response actually contains a refresh_token before treating the connection as durable.

Token exchange fails immediately with a 401/'unauthorized client' or 400 'invalid_request' during the OAuth callback.

Almost always a mismatched redirect_uri or wrong/rotated Consumer Key or Secret. Confirm TUMBLR_CLIENT_ID/SECRET in config exactly match the app at tumblr.com/oauth/apps, and that the app's registered callback URL is byte-for-byte identical to the redirect_uri this tool sends.

Publish call returns a 2xx-looking response but the post never appears, or returns an `errors` array with a 4xx like 'You do not have permission to post to this blog.'

The target blogId (UUID) is stale or belongs to a blog the authenticated user no longer administers (renamed blog, removed member, or wrong blog picked when multiple blogs exist on the account). Reconnect to re-pull the current blog list, and always publish to the blog's UUID rather than its old hostname.

Posting works fine for a while then starts returning 429 Too Many Requests during bursts or bulk backfills.

Tumblr enforces per-consumer-key rate limits (roughly 1,000 calls/hour, 5,000/day per app, shared across all connected blogs using that Consumer Key). Space out scheduled posts and back off/retry on 429 instead of retrying immediately.