Meta Marketing API error 100: Invalid parameter
Meta error 100 means one value in the request is wrong or missing. Retrying will not fix it. Read the rest of the message to find which field. Steps.
Not serious, and not a problem with your account, but retrying will not fix it. Error 100 means one of the values sent to Meta is wrong, missing or no longer allowed. The rest of the message usually names the field, so read that first.
Sources: Meta’s developer docs, checked November 2026.
Try this, in order
- Read the whole error, not just “Invalid parameter”. Look for a longer sentence or a field name such as budget, targeting or image.
- Fix that one thing in the ad, ad set or campaign and save again.
- Using a tool? Try the same change by hand in Ads Manager. Ads Manager usually marks the field at fault.
- If you copied an old campaign, check its targeting. Options that Meta has retired cause this error.
If that did not work
Match the message to the cause:
- “The category you selected is no longer available.” A targeting option was retired. Remove it and pick a current one.
- “Image wasn’t downloaded.” Meta could not fetch the image from the link given. Make sure the image link opens for anyone, with no login, and is not blocked for automated visitors.
- “Unsupported post request.” A permission problem in disguise. A developer’s system user (a non-human login) is missing from the ad account. In Business Settings, open the ad account, choose Add people, and add it.
- “This Task Combination Is Not Supported.” The mix of roles being assigned to a person is not allowed. Choose a permitted set.
- A report request fails. The report asks for too much at once. Shorten the date range or ask for fewer columns.
When to stop and contact Meta
Contact the tool’s support first if a tool sent the request: they can see exactly what was sent. Contact Meta through the Business Help Center only if the same change also fails in Ads Manager with no field marked.
The detail
| Code | Meta’s wording |
|---|---|
| 100 | “Invalid parameter.” |
| 100, subcode 33 | “Unsupported post request.” Meta adds that this may occur if the access token is not added as a system user with permissions on the ad account that owns a Custom Audience |
| 100, subcode 1487694 | “The category you selected is no longer available.” |
| 100, subcode 1752129 | “This Task Combination Is Not Supported.” |
| 100, subcode 3858258 | “Image wasn’t downloaded.” |
| 100, subcode 1487534 | Too much data requested in one report call. Narrow the dates, IDs or metrics |
From Meta’s Marketing API error reference and Insights best practices.
For developers, three parts of the response find the field faster than the code does:
error_user_msg: the message meant for the person, in their language.error_subcode: narrows the cause.error_data.blame_field_specs: names the field at fault. Meta’s example flagsdaily_budgetfor a budget that is too low.
Look-alikes: error 200 is missing permission, error 190 is an expired login, and error 1 is usually temporary. Error 100 is the only one of these fixed by changing what you sent.
Related
- Meta Ads error 1885272: Budget is too low
- Meta Marketing API error 200: Permission error
- All troubleshooting pages
While the request is fixed, you can still see what competitors are running. Proxy reads the public ad libraries from your AI assistant. It does not manage ad accounts and cannot fix this error.