Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 1752041: Duplicate request

Error 1752041 is a duplicate-request refusal during onboarding: the business has already been invited to onboard by a partner, so a second invitation isn't accepted.

1752041
Code
Duplicate request
Meta's name
Migration and onboarding
Type
400
HTTP status
On a set-up call, not a send
Where you see it
No, don't resend
Retry

Quick answer

The business was already invited to onboard. Meta says no further action is needed: all its eligible WhatsApp accounts are onboarded automatically.

What WhatsApp error 1752041 means

Meta documents 1752041, "Duplicate Request", with HTTP status 400: a client has already been invited to onboard by a partner. Onboarding requests are limited to one per business customer, and only the first partner to call the intent API succeeds. When a client is onboarded, all their eligible WhatsApp accounts are included automatically, so no further steps are needed.

Why error 1752041 happens

Onboarding and migration errors come from the state of the number or the account you're moving. Usually one of these:

  • Your onboarding flow sent the intent request twice.
  • Another partner working with the same business already sent it.
  • A retry after a timeout, when the first request had in fact succeeded.

How to fix error 1752041

There is no request change that gets this message delivered; the work is in your data and your audience.

  • Check whether your own system already sent the request; if so, treat 1752041 as a success.
  • If another partner sent it, the business's eligible accounts are onboarded regardless.
  • Make the onboarding call idempotent so a retry after a timeout isn't sent as a new request.
  • Confirm the business's account shows as onboarded before going further.
  • Tell partners and your team who started onboarding, so a second invitation isn't sent.

Should you retry after 1752041?

Don't retry: Meta says the onboarding request has already been made and all eligible accounts will be onboarded without extra steps.

How error 1752041 shows up in InfiQ

Error 1752041 comes from a set-up call, not a message send: creating or changing a template, registering a number or onboarding an account. InfiQ's template endpoints return Meta's error object for it with an InfiQ_traceid; for number registration and onboarding, which InfiQ's team runs with you, share the code and the details text with support.

Send it through InfiQ

Frequently asked questions

Does error 1752041 mean onboarding failed?+
No. It means the request was already made. Meta says that once a client is onboarded, all their eligible WhatsApp accounts are included automatically.
Can two partners onboard the same business?+
Only one onboarding request per business customer is accepted, from the first partner to call the intent API.
Should my code treat 1752041 as an error?+
Treat it as "already done". Record it, confirm the business is onboarded, and stop retrying.
Which partner ends up onboarding the business?+
Meta says only the first partner to call the intent API succeeds; later requests from anyone return 1752041.