
Getting started with WhatsApp Business API involves more than creating an account or obtaining an API token. Before your business can use WhatsApp messaging in production, you need to understand the relevant Meta account setup, sender phone number, customer permissions and technical responsibilities.
This guide explains the WhatsApp Business API requirements to review before onboarding with MoceanAPI. It covers business verification, WhatsApp Embedded Signup, opt-in and messaging policies, and the steps between account setup and a working integration. Requirements depend on your accounts and intended use, so not every business follows identical steps.
Separate what you can prepare now from account-specific checks.
Readiness item | What to do | Status |
Messaging purpose | Choose a legitimate use case and intended message types | Prepare |
Business details and account owner | Gather accurate details and identify authorised representatives | Prepare |
Meta business assets and WABA | Check the business portfolio and WhatsApp account setup | Verify |
Sender phone number | Choose a number and check its eligibility and current registration | Verify |
Business verification | Check whether Meta requests verification for your account or intended use | Conditional |
Customer permission | Establish WhatsApp opt-in and opt-out processes | Prepare / Verify |
API integration | Assign a technical owner, account access and testing plan | Prepare |
Prepare means planning work you can begin now. Conditional means an action depends on your circumstances. Verify means checking current instructions or your actual Meta and MoceanAPI account status.
Decide whether you need customer notifications, transactional updates, support replies, authentication codes or permitted marketing communication. For example, an online shop planning order updates should identify who maintains order data, when messages are triggered and whether approved templates are needed.
These are potential uses of the MoceanAPI WhatsApp API, not built-in workflows.
Several accounts and systems may be involved. Understand their roles before onboarding.
Business organisation: Owns the communication purpose, business information, customer permissions and applicable legal responsibilities.
Meta Business Portfolio: Meta’s business environment for organising relevant business assets and access. An authorised person needs appropriate permissions to manage the assets involved in onboarding.
WhatsApp Business Account (WABA): The WhatsApp Business Platform account associated with the organisation’s messaging assets. It is different from the standalone WhatsApp Business mobile application.
WhatsApp sender number: The phone number registered for business messaging. MoceanAPI’s current API documentation uses a registered WhatsApp Business sender number for outgoing messages.
MoceanAPI: The programmable messaging provider through which the organisation’s application accesses supported WhatsApp functionality.
Business application or backend: The organisation’s software that decides when to message customers and what happens after a reply or delivery event.
Conceptual relationship: Business organisation → Meta Business Portfolio → WABA → WhatsApp sender → MoceanAPI → business application.
This shows responsibility and connection, not a universal order of manual setup steps. Some assets may be created or connected during the supported onboarding flow.
Meta controls business verification. MoceanAPI’s business-verification guidance describes it as an important step, particularly when considering account capabilities and messaging limits. However, verification status and the steps available can vary with the account and intended production use. Do not assume that every organisation must complete exactly the same checks before any sandbox test.
Useful information to prepare includes your registered business name, address, contact details, website or other business presence, and access for an authorised representative. Meta may request documents. Check MoceanAPI’s verification instructions and your Meta account. Approval is not guaranteed.
Before selecting a sender, confirm who controls the number, whether it already uses WhatsApp, and whether it is connected to another business account or provider. Existing registration may introduce preparation or migration questions.
MoceanAPI’s current phone-number FAQ states that a number registered for its WhatsApp Business Platform service cannot simultaneously be used in the WhatsApp mobile app.
This is MoceanAPI’s stated guidance, not a universal rule about every Meta coexistence arrangement. If you plan to reuse a number, check the supported path with MoceanAPI before changing anything. Do not assume eligibility, migration steps or uninterrupted service.
WhatsApp Embedded Signup is a Meta-provided onboarding process that supported providers can include in their customer onboarding experience. MoceanAPI confirms that its dashboard provides this process through the WhatsApp Getting Started area.
Its purpose is to help connect or establish the relevant WhatsApp business assets with the provider. Embedded Signup is not the same as business verification, customer opt-in or writing the API integration.
Before: Define the messaging use case, prepare business details, identify the intended sender and ensure the authorised Meta account holder is available. Check whether verification or existing-number issues need attention.
During: Follow the current Meta and MoceanAPI instructions to create or connect relevant supported assets and complete the account or sender actions presented for your situation.
After: Confirm the WABA and sender setup, identify any outstanding account checks, and hand over to the team responsible for credentials and integration.
For the actual dashboard procedure, use MoceanAPI’s Embedded Signup FAQ. Completing the flow does not guarantee Meta approval or immediate production access.
The current WhatsApp Business Messaging Policy says a business may contact someone on WhatsApp when the person has provided their mobile phone number or username and has opted in to receive subsequent WhatsApp messages or calls from the business. The opt-in should make it clear that the person is agreeing to receive messages from the business and should clearly identify the business by name. Current WhatsApp guidance does not require the opt-in itself to be WhatsApp-specific, although the business remains responsible for meeting applicable legal permission requirements.
Choose a permission method that meets applicable rules; there is no universal checkbox design. Explain expected messages, such as order updates or offers, and how preferences can change.
For instance, a customer entering a mobile number to arrange delivery has not automatically agreed to unrestricted future marketing on WhatsApp. Consider recording when and how permission was obtained, particularly where your applicable laws require evidence.
WhatsApp requires businesses to honour requests to stop, block or opt out of communications, whether those requests arrive inside or outside WhatsApp. Your organisation should have a workable method to update customer preferences and prevent further unwanted contact.
MoceanAPI provides messaging API functionality; this does not mean it supplies a native consent or preference-management platform. The business must arrange its own suitable process.
Compliance has three distinct layers that should be reviewed before sending live messages.
This is practical preparation guidance, not jurisdiction-specific legal advice.
Under the current WhatsApp Business Messaging Policy, businesses can reply with non-template messages within 24 hours of the customer’s last message. Outside that customer-service window, an approved message template is required. Business-initiated messaging also uses approved templates.
Think about your template needs before launch. WhatsApp supports Marketing, Utility and Authentication categories for different messaging purposes. If you intend to send OTP or two-factor authentication messages, include Authentication messaging in your plan. Template creation, approval and authentication implementation are separate technical tasks.
Onboarding complete does not mean application integration complete. Once the business and sender setup is ready, your technical team still needs to connect the relevant application or backend to MoceanAPI.
Current MoceanAPI API documentation uses Bearer API-token authentication for WhatsApp requests. Protect credentials and plan the outbound messages, inbound replies and delivery events your application needs.
MoceanAPI also provides a WhatsApp Sandbox for trying supported sending and receiving with configured test numbers and trial templates. Test message behaviour, credentials, templates, permission handling and the application’s response to events before production.
A successful sandbox test does not automatically mean the business or sender is approved for live use.
There is no universal completion time. Business details, Meta account status, verification and number history can affect the timeline. MoceanAPI cannot guarantee Meta-controlled reviews
Use Prepare for work your team can organise, Conditional for account-dependent steps and Verify where current requirements need checking.
Area | Final readiness check | Status |
Business | Legitimate use case, accurate information, onboarding owner and authorised people identified | Prepare |
Meta / WABA | Relevant Business Portfolio, WABA access, onboarding path and verification status checked | Verify / Conditional |
Sender | Number controlled, eligibility reviewed and any existing-provider or mobile-app issues resolved | Verify / Conditional |
Messaging policy | Appropriate opt-in, opt-out handling and current WhatsApp policy reviewed | Verify |
Templates and law | Required templates identified; applicable privacy and marketing obligations assessed | Conditional / Verify |
Technical | Backend owner, protected API access, outbound/inbound needs and testing plan established | Prepare / Verify |
Production | Account/sender readiness confirmed; intended messages, permissions and application behaviour tested | Verify |
Understanding WhatsApp Business API requirements helps your team avoid account, permission and integration surprises. Once your business, sender and messaging processes are ready, move to the current MoceanAPI API Documentation for implementation details. For broader product information, explore MoceanAPI WhatsApp API.

MoceanAPI identifies verification as an important onboarding consideration, but the requirements and timing depend on your Meta account and intended use. Check your actual status rather than assuming the same process applies to every business or sandbox test.
It depends on the number's current registration and MoceanAPI's supported onboarding path. Its existing guidance says a number registered for its WhatsApp Business Platform service cannot also be used in the WhatsApp mobile app. Confirm any migration or coexistence options before making changes.
No. It helps with relevant onboarding and account connection. Business verification, sender readiness, policy requirements and technical implementation may still need attention.
It should clearly identify the business and make clear that the person is opting in to receive messages from that business. The person must also have provided their mobile phone number or username. Current WhatsApp guidance does not require the opt-in itself to be WhatsApp-specific, although applicable legal requirements still apply.
No. Template approval relates to the content and platform messaging rules; it does not replace recipient opt-in or applicable legal permission. Check both before contacting customers.