Skip to main content

Troubleshooting Auto-Boost and the Boost API

This page covers every problem with an Auto-Boost rule, with keys and webhooks on the Developer page, and with replies to requests made with an API key. Find the message you see, or the thing that is not working.

Other Boost problems are on two sibling pages:

Arming an Auto-Boost rule​

These messages appear under the Arm a new rule form on the Auto-Boost page after you press Arm Auto-Boost. Unless a card says otherwise, no rule was created and nothing was charged.

Messages that can appear on any Boost page, such as a dropped connection, too many attempts or Boost being paused, are on Troubleshooting Boost.

"Pick the service to run on every new post."​

  • Where you see it: Auto-Boost, under the Arm a new rule form, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: A field in the form is empty or zero. The sibling messages name the other fields: "Enter the channel to watch (its @username or link).", "Enter the quantity per post." and "Enter a starting budget in USD."
  • How to fix it: Fill in the field the message names, then press Arm Auto-Boost again.

The Service list reads "No services available right now"​

  • Where you see it: Auto-Boost, in the Service list of the Arm a new rule form (website).
  • Plans affected: Every plan.
  • Why it happens: The service list has not loaded yet, or there is no service your account can order at the moment.
  • How to fix it: Reload the page. If Start a boost also shows no services, Boost has nothing on sale right now. Try again later.

"Connect your Telegram first — Auto-Boost watches your channel through the bot."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: Your account has no Telegram account connected. The bot notices new posts in your channel, so a rule cannot run without it.
  • How to fix it: Connect Telegram by following Connecting your Telegram, then arm the rule again.
  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: You entered an invite link in Channel. An invite link belongs to a private channel, and a rule can only watch a public one.
  • How to fix it: In Telegram, give the channel a public username. Then enter that username, or the channel's public t.me link, in Channel.

"We couldn't access that channel. Make it public, then try again."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: The channel is private or does not exist under that name. If the text is not a username or a link at all, you see "Enter a valid channel @username or t.me link." instead.
  • How to fix it: Check the spelling of the username. Make sure the channel is public, then press Arm Auto-Boost again.

"Channel checks are temporarily unavailable — please try again in a few minutes."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: We could not check your channel just now. The problem is on our side, not with your channel.
  • How to fix it: Wait a few minutes, then press Arm Auto-Boost again.

"This channel can't be used on Onflow Ads for Auto-Boost."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost, Resume or Top up (website). The full message continues: "If you believe this is a mistake, reply to the email we sent you about it, or open a support request quoting the reference." It can end with a reason.
  • Plans affected: Every plan.
  • Why it happens: Our team has blocked this channel. A rule that already watches it is held paused.
  • How to fix it: If you think the block is a mistake, reply to the email you received about it. You can also open a support request at https://onflowads.com/support and quote the reference from the message. To get a held rule's budget back, press Cancel on that rule.

"Per-post quantity must be between minimum and maximum."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: The number in Quantity per post is outside the range the chosen service accepts.
  • How to fix it: Enter a quantity inside the range the message gives, then press Arm Auto-Boost again.

"Fund at least the cost of one post — one post costs that much."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: The amount in Starting budget (USD) is less than one post costs at your quantity. The line under the form shows the cost per post.
  • How to fix it: Raise the starting budget to at least the amount in the message, or lower Quantity per post.

"You need the amount in wallet cash to fund this subscription's budget."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: Your wallet balance is lower than the starting budget. A rule is funded from your wallet only. Boost credit cannot fund a rule.
  • How to fix it: Add funds to your wallet, or enter a smaller starting budget, then arm the rule again.

"You have reached your Auto-Boost limit."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost or Resume (website). On every plan except Ultimate, a notification with the same title and an Upgrade button also slides in. It adds "Upgrade to run more rules at once."
  • Plans affected: Every plan.
  • Why it happens: You already run as many active rules as your plan allows. Paused, cancelled and expired rules do not count.
  • How to fix it: Press Pause or Cancel on another rule, then try again. To run more rules at once, upgrade your plan. The limit for each plan is on Boost limits by plan.

"This boost is over your order limit."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website). On every plan except Ultimate, a notification with the same title and an Upgrade button also slides in.
  • Plans affected: Every plan.
  • Why it happens: One post at this quantity would cost more than the largest single order your plan allows.
  • How to fix it: Lower Quantity per post, or upgrade your plan. The largest order for each plan is on Boost limits by plan.

"This channel already has an Auto-Boost for this service. Add budget to that one instead. Nothing was charged."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: A running or paused rule already exists for the same channel and the same service. Pressing Arm Auto-Boost twice in a row gives the same message.
  • How to fix it: Find the existing rule under Your rules and press Top up to add budget to it.

"That service is temporarily unavailable. Please try again later."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website). Sibling wordings: "That service isn't available.", "That service is temporarily unavailable." and "This service can't be ordered right now."
  • Plans affected: Every plan.
  • Why it happens: The service you chose was withdrawn, or it cannot be priced at the moment.
  • How to fix it: Choose another service in the Service list, or try the same service again later.

"We couldn't reach the server, so we can't tell whether that rule went through. Reload this page and check before trying again — retrying could charge you twice."​

  • Where you see it: Auto-Boost, under the form after Arm Auto-Boost, or under Your rules after Top up, where it says "top-up" in place of "rule" (website). After the first, Arm Auto-Boost stays switched off. After the second, every Top up button is switched off, and pointing at one shows "Reload the page to check whether your last top-up went through."
  • Plans affected: Every plan.
  • Why it happens: Your connection dropped while the request was on its way. The page cannot tell whether the money moved, so it keeps the button switched off on purpose until you reload.
  • How to fix it:
    1. Reload the page.
    2. Look at Your rules and at Balance to see whether the rule or the top-up is there.
    3. Only if it is not there, try again.

"Couldn't arm that rule."​

  • Where you see it: Auto-Boost, after pressing Arm Auto-Boost (website).
  • Plans affected: Every plan.
  • Why it happens: The request failed and no reason came back. Normally nothing was created or charged.
  • How to fix it: Reload the page and check Your rules before you press Arm Auto-Boost again, so you do not arm the same rule twice.

A rule that is running, paused or ended​

These problems appear on a rule's row under Your rules on the Auto-Boost page, or as a notification on the website, in the bot and by email. A rule's budget is never lost: Cancel returns whatever is unspent to your wallet.

"No Auto-Boost rules yet. Arm one above and every new post is boosted automatically."​

  • Where you see it: Auto-Boost, under Your rules, in place of the list (website).
  • Plans affected: Every plan.
  • Why it happens: There is no rule on your account to list. Nothing is wrong, and no new post is being boosted for you.
  • How to fix it: Fill in the Arm a new rule form above the list and press Arm Auto-Boost. Auto-Boost rules for new posts has the steps. If you expected to see a rule here, reload the page.

"Paused: Insufficient budget — top up to continue."​

  • Where you see it: Auto-Boost, on the rule's row (website). The notification "Auto-Boost paused" arrives on the website, and in the bot and by email by your notification settings.
  • Plans affected: Every plan.
  • Why it happens: The rule's budget could not cover the next post and auto-renew was off. It also happens when auto-renew was on and your wallet could not pay for the renewal.
  • How to fix it: Press Top up and add budget. The rule starts again. Posts published while the rule was paused may not be boosted. To stop instead, press Cancel and the unspent budget returns to your wallet.

"Paused: No provider can deliver this service right now"​

  • Where you see it: Auto-Boost, on the rule's row, with an "Auto-Boost paused" notification (website; bot and email by your notification settings). A sibling wording is "Paused: Service unavailable at the provider".
  • Plans affected: Every plan.
  • Why it happens: The rule's service cannot be delivered at the moment. The budget is untouched, including the amount set aside for the post that could not be boosted.
  • How to fix it: Press Resume later. If the rule pauses again, press Cancel to get the budget back and arm a new rule with another service.

"Paused: This service is no longer offered — start a new rule with another service. Cancel this rule to get the unspent budget back."​

  • Where you see it: Auto-Boost, on the rule's row, with an "Auto-Boost paused" notification (website; bot and email by your notification settings). The row has no Resume or Top up button.
  • Plans affected: Every plan.
  • Why it happens: The service was removed from Boost, so this rule cannot run again. Its budget is untouched.
  • How to fix it: Press Cancel to return the unspent budget to your wallet. Then arm a new rule with a service that is on sale.

"Paused: The provider raised this service's price — start a new rule to boost at today's rate. Cancel this rule to get the unspent budget back."​

  • Where you see it: Auto-Boost, on the rule's row, with an "Auto-Boost paused" notification (website; bot and email by your notification settings). The row has no Resume or Top up button while the price stays higher.
  • Plans affected: Every plan.
  • Why it happens: A rule keeps the price per post it had when you armed it. The service now costs more than that, so the rule stopped instead of charging you a price you did not agree to.
  • How to fix it: Press Cancel to return the unspent budget to your wallet. Then arm a new rule. The line under the form shows today's cost per post before you confirm.

"Paused: Each post is now above this account's per-order limit — start a new rule with a smaller per-post quantity. Cancel this rule to get the unspent budget back."​

  • Where you see it: Auto-Boost, on the rule's row, with an "Auto-Boost paused" notification (website; bot and email by your notification settings).
  • Plans affected: Free, Lite, Plus, Elite and Master, after a move down from a higher plan.
  • Why it happens: Your plan ended or you moved to a lower one. One post at this rule's quantity now costs more than the largest single order your current plan allows.
  • How to fix it: Choose one:
    1. Renew or upgrade your plan. Resume is offered again once your plan covers the cost of one post.
    2. Press Cancel to get the budget back, then arm a new rule with a smaller Quantity per post.

"Paused: This channel can't be used on Onflow Ads"​

  • Where you see it: Auto-Boost, on the rule's row (website). Resume and Top up answer with the longer message that starts with the same words.
  • Plans affected: Every plan.
  • Why it happens: Our team has blocked the channel this rule watches. The rule is held paused. It is not renewed and nothing is charged while the block stands.
  • How to fix it: Reply to the email you received about the channel, or open a support request and quote the reference from the message. Cancel returns the rule's unspent budget to your wallet at any time.

Resume answers with the pause reason again​

  • Where you see it: Auto-Boost, under Your rules after pressing Resume, usually on a page that has been open for a while (website). The support assistant gives the same answer if you ask it to resume the rule. Example: "The provider raised this service's price — start a new rule to boost at today's rate."
  • Plans affected: Every plan.
  • Why it happens: The reason the rule was paused still holds, so resuming would only pause it again on the next post. Nothing was charged.
  • How to fix it: Do what the sentence says. In most cases that means pressing Cancel to get the budget back and arming a new rule.

"That rule's month has run out — start a new one, or cancel it to get the unspent budget back."​

  • Where you see it: Auto-Boost, after pressing Resume or Top up on a paused rule, or on a page that has been open for a while (website). After Top up the sentence reads "That rule's month has run out — cancel it to get the unspent budget back, or start a new one."
  • Plans affected: Every plan.
  • Why it happens: A rule runs for 30 days. Pausing a rule does not stop that clock, and this rule's 30 days have ended. Nothing was charged, and the leftover budget is still on the rule.
  • How to fix it: Press Cancel on the rule to return the leftover budget to your wallet. Then arm a new rule.

The rule shows Expired​

  • Where you see it: Auto-Boost, as the badge on the rule's row with the line "Expired date" (website). The notification "Auto-Boost expired" arrives on the website, and in the bot and by email by your notification settings.
  • Plans affected: Every plan.
  • Why it happens: The rule reached the end of its 30 days with auto-renew off, or the renewal could not be paid from your wallet. A rule you paused yourself is not renewed either. New posts are no longer boosted.
  • How to fix it: Any budget left on an expired rule does not return by itself. Press Cancel on the expired rule to move it back to your wallet, then arm a new rule.

The button reads "Auto-renew: off" although I switched it on​

  • Where you see it: Auto-Boost, on the rule's row (website). No message is sent when this happens.
  • Plans affected: Every plan.
  • Why it happens: When the renewal came due, your wallet could not cover it. Auto-renew was switched off and nothing was charged. The rule now ends on the date in its "Ends date" line. Adding funds later does not renew it by itself.
  • How to fix it: Add funds to your wallet. Then press Auto-renew: off to switch it back on. You can only do this before the rule's end date.

"Can't resume a subscription that isn't paused."​

  • Where you see it: Auto-Boost, after pressing Pause, Resume, Top up or Cancel on a page that is out of date, for example with the page open in two tabs (website). The support assistant can give the same answer. Sibling wordings: "Can't pause a subscription that isn't active.", "That subscription is already cancelled.", "That subscription is cancelled." and "Subscription not found."
  • Plans affected: Every plan.
  • Why it happens: The rule changed after the page was drawn, so the button you pressed no longer applies. Nothing happened, and a cancelled rule's budget is returned once only.
  • How to fix it: Reload the page. The badge on the row shows the rule's real state.

"Enter an amount in USD, e.g. 10."​

  • Where you see it: Auto-Boost, in the Top up this rule prompt (website). A sibling wording is "Enter an amount of at least $0.01 to add to the budget."
  • Plans affected: Every plan.
  • Why it happens: The amount is empty, zero or not a number. Nothing was charged.
  • How to fix it: Type a number greater than zero, without a currency sign, and press Add to budget.

"Not enough wallet cash for that top-up."​

  • Where you see it: Auto-Boost, after pressing Add to budget in the Top up this rule prompt (website).
  • Plans affected: Every plan.
  • Why it happens: Your wallet balance is lower than the amount you entered. Boost credit does not count toward a rule's budget. Nothing was charged.
  • How to fix it: Add funds to your wallet first, or top up the rule with a smaller amount.

"The budget was added, but the rule stays paused"​

  • Where you see it: Auto-Boost, after a top-up that went through (website). The full message reads: "Auto-Boost rule ID updated. The budget was added, but the rule stays paused: you already run the most Auto-Boost rules you can at once. Pause or cancel another rule, then resume this one."
  • Plans affected: Every plan.
  • Why it happens: A top-up normally restarts a rule that was paused for budget. This time you already run as many active rules as your plan allows. The money left your wallet and is in the rule's budget, but the rule did not restart.
  • How to fix it: Press Pause or Cancel on another rule, then press Resume on this one. To run more rules at once, upgrade your plan.

"That subscription is no longer active — nothing was charged."​

  • Where you see it: Auto-Boost, after a top-up (website).
  • Plans affected: Every plan.
  • Why it happens: The rule was cancelled while your top-up was on its way, so the top-up was not taken.
  • How to fix it: Reload the page. If you still want new posts boosted, arm a new rule.

"Couldn't update that rule."​

  • Where you see it: Auto-Boost, under Your rules after Pause, Resume or Cancel (website). Sibling wordings: "Couldn't top up that rule." and "Couldn't change auto-renew."
  • Plans affected: Every plan.
  • Why it happens: The request failed and no reason came back. Normally nothing changed.
  • How to fix it: Reload the page and check the rule's row before you try again.

A post was not boosted​

  • Where you see it: In your channel, or on the Orders page, where no order appears for that post (website).
  • Plans affected: Every plan.
  • Why it happens: Nothing was spent on that post. The usual reasons:
    1. The rule was paused or out of budget when the post went up. A post that is already old when the rule starts again is not boosted.
    2. The post was published before you armed the rule.
    3. The provider could not accept an order for that post.
    4. The channel is no longer public.
    5. Several photos or videos sent together count as one post, so they get one order.
  • How to fix it: Check the rule's row for a "Paused:" line and fix its cause. To boost the missed post, order it by hand from Start a boost.

The budget jumped back to full, or "Auto-Boost renewed" arrived early​

  • Where you see it: Auto-Boost, in the "amount of amount left" figures on the rule's row (website). The notification "Auto-Boost renewed" arrives on the website, and in the bot and by email by your notification settings.
  • Plans affected: Every plan.
  • Why it happens: The rule renewed. With auto-renew on, a rule renews shortly before its 30 days end. It renews early if its budget runs out first. Each renewal takes the starting budget from your wallet again and adds 30 days to the rule.
  • How to fix it: Nothing is wrong. If you do not want early renewals, press Auto-renew: on to switch it off. The rule then pauses when its budget runs out.

API keys on the Developer page​

These messages appear on the Developer page, on or under the API keys card. Keys are part of Elite, Master and Ultimate.

"The Boost API is not available on this account"​

  • Where you see it: Developer, as a card at the top of the page (website). Under the title it reads: "API keys and webhooks are off here. Everything else on this page stays available."
  • Plans affected: Free, Lite and Plus.
  • Why it happens: API keys are included from Elite. On your plan the API keys and Webhooks cards are hidden. Quick start and Full API reference stay visible, and the rest of Boost is not affected.
  • How to fix it: Upgrade to Elite or above. See Upgrading your plan.

"No API keys yet. Create one to call the Boost API from your own code."​

  • Where you see it: Developer, on the API keys card, in place of the list of keys (website).
  • Plans affected: Elite and above.
  • Why it happens: No key has been created on your account yet. A key you revoked stays in the list, so this line shows only before your first key.
  • How to fix it: Press Create a key, then copy the key from the dialog before you close it, because it is shown once. The Boost API and developer keys has the steps.

"Onflow Ads support has blocked API access for this account, so a new key would be blocked as well."​

  • Where you see it: Developer, under the list of keys after pressing Create a key (website). The page can also word it "…so new keys would be blocked as well." Both versions continue with "Contact support to have the block reviewed." You also receive a notification titled "Developer API key blocked" or "Developer API access blocked". A request made with a blocked key is answered "This API key was disabled by Onflow Ads support."
  • Plans affected: Elite and above.
  • Why it happens: Our team has blocked one key or every key on your account. Requests made with a blocked key are refused. Revoking the key and creating another does not help.
  • How to fix it: Open a support request at https://onflowads.com/support and ask for the block to be reviewed. Quote the Key ID shown on the key's row, which looks like OFBK-000-0000. Never send the key itself.

"New API keys cannot be created right now. Your existing keys keep working."​

  • Where you see it: Developer, on the API keys card, after pressing Create a key (website).
  • Plans affected: Elite and above.
  • Why it happens: Creating keys is switched off for everyone for a short while. The keys you already have are not affected.
  • How to fix it: Keep using your existing keys and try Create a key again later.

"You have reached your API key limit."​

  • Where you see it: Developer, after pressing Create a key (website). On Elite and Master a notification with the same title and an Upgrade button also slides in. It adds "Upgrade to run more keys at once."
  • Plans affected: Elite and above.
  • Why it happens: Every key your plan includes is in use. The API keys card shows the count as "Active keys: used of allowed". A key our team has blocked still counts until you revoke it.
  • How to fix it: Press Revoke on a key you no longer use, then press Create a key. On Elite or Master you can also upgrade for more keys.

"Couldn't copy the key. Select it and copy it yourself before closing."​

  • Where you see it: Developer, in the Your new API key dialog after pressing Copy key (website). The Webhook signing secret dialog shows the same sentence with "secret" in place of "key".
  • Plans affected: Elite and above.
  • Why it happens: Your browser did not allow the page to copy for you. Nothing was copied, but the value is still on screen.
  • How to fix it: Select the text by hand and copy it. Paste it somewhere safe before you press Done, because it is not shown again.

I closed the dialog without copying the key​

  • Where you see it: Developer, after pressing Done in the Your new API key or Webhook signing secret dialog (website).
  • Plans affected: Elite and above.
  • Why it happens: A key and a webhook signing secret are each shown once, when they are created. They cannot be shown again, by you or by support.
  • How to fix it: For a key, press Revoke on its row and then Create a key. For a webhook, press Delete on its row and add it again to get a new signing secret.

"Couldn't create a key."​

  • Where you see it: Developer, under the list it belongs to (website). Sibling wordings: "Couldn't revoke that key.", "Couldn't add that webhook." and "Couldn't delete that webhook."
  • Plans affected: Elite and above.
  • Why it happens: The request failed and no reason came back. Normally nothing changed.
  • How to fix it: Reload the page and check the list of keys or webhooks before you try again.

Webhooks on the Developer page​

A webhook sends a message to a web address of yours each time one of your orders finishes, is refunded or is cancelled. Adding one is part of Master and Ultimate. These messages appear on the Webhooks card of the Developer page.

"New webhooks are not available on this account."​

  • Where you see it: Developer, on the Webhooks card, in place of the form (website).
  • Plans affected: Elite. Also Free, Lite and Plus accounts that still hold webhooks from an earlier plan.
  • Why it happens: Your plan does not include adding webhooks. Webhooks you already have stay listed, keep working and can be deleted.
  • How to fix it: Upgrade to Master or Ultimate to add a webhook. See Upgrading your plan.

"New webhooks can't be added right now."​

  • Where you see it: Developer, on the Webhooks card, in place of the form (website). If you press Add webhook on a page that was already open, the line under the form reads "New webhooks can't be added right now. Webhooks you already have stay listed here."
  • Plans affected: Master and Ultimate.
  • Why it happens: Webhooks are switched off for everyone for a short while. Nothing is sent to any webhook meanwhile, and nothing is deleted.
  • How to fix it: Wait. Until the form returns, follow your orders on the Orders page.

"The webhook URL must be https."​

  • Where you see it: Developer, on the Webhooks card after pressing Add webhook (website). Sibling wordings: "That is not a valid URL.", "That URL has no host.", "That host could not be resolved." and "That address is not reachable from the public internet." An empty address box is refused as well, with a line asking you to enter the address.
  • Plans affected: Master and Ultimate.
  • Why it happens: The address is empty, does not start with https://, is mistyped, or is not a public address on the internet. The webhook was not added.
  • How to fix it: In the address box, enter the full public address of your own server, starting with https://. Check that it opens from outside your own network, then press Add webhook.

"You already have 10 active webhooks. Remove one first."​

  • Where you see it: Developer, on the Webhooks card after pressing Add webhook (website).
  • Plans affected: Master and Ultimate.
  • Why it happens: Your account already holds the largest number of active webhooks. The new one was not added.
  • How to fix it: Press Delete on a webhook you no longer need, then add the new one.

"Switched off after repeated failed deliveries"​

  • Where you see it: Developer, on the webhook's row on the Webhooks card (website). The line can name the last reply your server gave. It ends by telling you to fix your address, delete the webhook and add it again.
  • Plans affected: Master and Ultimate, and any account that still holds webhooks.
  • Why it happens: Your address kept failing to accept our messages. No more order updates are sent to it. Your orders are not affected.
  • How to fix it:
    1. Fix your server so the address accepts messages again.
    2. Press Delete on the switched-off row.
    3. Add the address again with Add webhook. A new signing secret is shown once. Copy it into your code.

"No webhooks yet. Add one to receive delivery events as they happen."​

  • Where you see it: Developer, on the Webhooks card, in place of the list of webhooks (website).
  • Plans affected: Elite and above. Adding a webhook needs Master or Ultimate.
  • Why it happens: Your account has no webhook. Nothing is wrong: your orders run the same with or without one, and every update is still on the Orders page.
  • How to fix it: On Master or Ultimate, enter the public address of your own server in the address box and press Add webhook. On Elite the form is replaced by "New webhooks are not available on this account."; see that card above.

Requests made with an API key​

These messages come back in the reply to a request your own code makes with an API key. They do not appear on a dashboard page. The full reference for requests is inside the dashboard: open Developer and press Full API reference.

"Invalid API key."​

  • Where you see it: In the reply to a request made with an API key.
  • Plans affected: Elite and above.
  • Why it happens: The key is missing, mistyped or revoked. The Key ID that starts with OFBK- and the short prefix on the key's row are labels, not the key. The request was refused and nothing was charged.
  • How to fix it: Send the full key exactly as it was shown when you created it. If you no longer have it, press Revoke on its row and create a new key.

"Your plan no longer includes the developer API."​

  • Where you see it: In the reply to a request made with an API key.
  • Plans affected: Free, Lite and Plus, after a move down from Elite or above.
  • Why it happens: Your plan ended or you moved to a plan without the API. Every request is refused, but your keys are kept.
  • How to fix it: Renew or upgrade to Elite or above. The same keys work again straight away. See Upgrading your plan.

"Rate limit exceeded."​

  • Where you see it: In the reply to a request made with an API key. A second message says the key's daily limit has been reached and when it resets.
  • Plans affected: Elite and above.
  • Why it happens: The key sent more requests in a minute than it may. The API keys card on the Developer page shows how many requests a minute each of your keys may make. An account with a low reliability score can be allowed fewer. The daily message means our team has set a limit on that key. Nothing was charged.
  • How to fix it: Send requests more slowly, and ask about several orders in one request instead of one request per order. For the daily message, wait for the reset or ask support to review the limit. Quote the Key ID.

"Your account has been suspended."​

  • Where you see it: In the reply to a request made with an API key. Sibling wordings: "Your account is suspended until the date." and "This account cannot use the API right now."
  • Plans affected: Elite and above.
  • Why it happens: Your account is suspended, so every request is refused. The key itself is fine and does not need replacing.
  • How to fix it: Resolve the suspension. Account standing explains what a suspension means, and Appealing a penalty explains how to ask for a review.

"Your wallet is the amount overdrawn. Top up to clear it and your account unlocks — every credit, including anything you earn, comes straight off the balance first."​

  • Where you see it: In the reply to a request made with an API key. The same sentence appears on the Auto-Boost page after pressing Arm Auto-Boost or adding budget with Top up (website). A later variant says the time to clear the amount has passed. A reply can also read "This account's wallet is overdrawn. Top up to clear it — the API unlocks the moment the balance is back to zero."
  • Plans affected: Every plan on the Auto-Boost page. Elite and above for API requests.
  • Why it happens: Your wallet balance is below zero. No new rule or top-up can start, and every API request is refused, until it is cleared.
  • How to fix it: Add funds until the balance is back to zero. Requests and new rules are accepted again at once. Owing money explains how a balance goes below zero.

"Your account is under review while an open fraud concern is resolved."​

  • Where you see it: In the reply to a request made with an API key. The message continues: "You can finish anything already in progress, but can't start a new deal until it's cleared — see your reliability page." A different reply says that API access needs a higher reliability score, and gives your own score.
  • Plans affected: Elite and above.
  • Why it happens: There is an open review on your account, or your reliability score is too low for the API at the moment. Requests are refused until the review is closed or the score has recovered.
  • How to fix it: Open your reliability page to see where the account stands. Wait for the review to finish, or appeal through support. A low score recovers as you complete deals cleanly. Account standing explains the process.

"The API is temporarily unavailable. Please try again later."​

  • Where you see it: In the reply to a request made with an API key. Sibling wordings: "This action is temporarily unavailable. Please try again later.", "Service unavailable." and "The request could not be completed."
  • Plans affected: Elite and above.
  • Why it happens: The API, or the one action you asked for, is switched off for a short while, or something failed on our side. Nothing was charged.
  • How to fix it: Try again later. Before you repeat an order request, read the part of the Full API reference about repeating a request safely, so the order is not placed twice.

"You already have N orders in progress, which is the limit for the plan name plan."​

  • Where you see it: In the reply to a request to place an order with an API key. Sibling wordings: "That order is the order total, above the limit per-order limit on the plan name plan.", "That service needs the plan name plan.", "That service is for members only" and "Drip-feed is a premium feature". A reply can end with "Nothing was charged." or with a sentence that names the plan which raises the limit.
  • Plans affected: Elite and above.
  • Why it happens: The order ran into a limit of your plan: the number of orders in progress at once, the largest single order, or a service or option your plan does not include. On the website the same refusal is shown as a short sentence with an Upgrade notification. No order was placed and nothing was charged.
  • How to fix it: Wait for running orders to finish, send a smaller quantity, or choose a service and options your plan includes. Every figure is on Boost limits by plan. To raise a limit, see Upgrading your plan.

"The order could not be placed."​

  • Where you see it: In the reply to a request made with an API key. Sibling wordings for the other actions: "The order could not be cancelled.", "The cancellation could not be requested.", "The refill could not be requested." and "The refill status could not be read."
  • Plans affected: Elite and above.
  • Why it happens: The action failed and no more exact reason was available. An order that could not be placed is not charged. A cancel or refill that could not be requested leaves the order exactly as it was.
  • How to fix it: Ask for the order's status first, or find it on the Orders page, so you know its real state. Then send the request again later. Before you repeat an order request, read the part of the Full API reference about repeating a request safely.

A request seemed to succeed but no order appeared​

  • Where you see it: In your own code or logs, after a request to place an order. No new order appears on the Orders page.
  • Plans affected: Elite and above.
  • Why it happens: A reply can arrive normally and still carry a refusal instead of an order ID. The refusal is the same sentence the dashboard would show for that order, for example a short balance, a plan limit or a quantity outside the service's range. No order was placed and nothing was charged.
  • How to fix it: Make your code read the message in every reply, not only whether a reply arrived. Then fix the cause the message names. The Full API reference explains how to have refusals reported more clearly. To look up a message, search this page and Troubleshooting Boost orders.

A request is answered with a message about an unknown action or an incorrect order ID​

  • Where you see it: In the reply to a request made with an API key. Examples: "Incorrect order ID", "Refill not found", "This order can't be refilled.", "The N-day refill window has passed.", "This order can no longer be cancelled.", "A refill for this order was just requested." and "That guarantee length isn't available." Other short replies say that a value is required, must be a whole number or is outside the range the action accepts.
  • Plans affected: Elite and above.
  • Why it happens: The action name is misspelled, or a value the action needs is missing or in the wrong form. It also happens when the order or refill does not belong to your account, or the order is not in a state that allows the action. Only that one item is refused. Other orders in the same request are handled normally.
  • How to fix it: Check the action names in the Full API reference inside the dashboard. Send each Order ID exactly as it was returned when the order was placed. It looks like OFB-000-0000. To see what an order allows right now, find it on the Orders page.

Still stuck?​

The fastest way to reach support is https://onflowads.com/support. It opens the support chat whether you are signed in or not. Include these four things so we can find the problem quickly:

  • What you were doing, for example arming a rule or creating a key.
  • The exact message you saw, copied word for word.
  • The ID shown on screen: the rule ID on the rule's row (it looks like OFBS-000-0000), the Key ID on the key's row (OFBK-000-0000), or the Order ID (OFB-000-0000).
  • The date and time it happened.

For an API problem, send the Key ID only. Never send the key itself or a webhook signing secret, to support or to anyone else. More ways to reach us are on Help and support.

Last updated on