Resource request procedure
Before you can send messages or make calls, you need communication resources: phone numbers, sender IDs, email domains, and channel-specific senders. You can request these through the Infobip web interface (best for manual setup and one-time requests) or programmatically through the API (best for automation at scale).
All resource requests follow the same six-phase procedure regardless of method. This page explains what happens at each phase so you know what to expect after submitting.
How a resource request is processed
Gather requirements
Identify all required information for your resource type and country before submitting. Some resources require additional documentation or data (known as data requirements). The web interface displays requirements dynamically based on your selections. Through the API, use the Get requirements endpoint to retrieve the full list.
Submit request
Submit your collected information through the web interface or API. Your data is validated against the requirements for your resource type. There may be a charge for certain requests depending on the resource type and country.
Receive feedback
Infobip validates your submission automatically. If validation passes, the request proceeds to internal review. Feedback is delivered through My requests notifications, email, or API webhooks (subscribe to RESOURCE_REQUEST_STATUS_UPDATE for real-time updates).
Respond to feedback
If validation fails or Infobip requests additional information, submit corrections. In the web interface, edit requests with Action required status from My requests. Through the API, use the Update resource request endpoint. Contact Support if you need help.
Processing
Infobip registers your resource with carriers, configures routing, and verifies all records.
Completion
Your resource is finalized, provisioned, and ready to use. Start sending messages through the web interface or API.
WhatsApp and RCS follow multi-step workflows that combine API and web interface operations. See Request resources through web interface for details.
Timeline expectations
Provisioning timelines vary by resource type, country, regulations, and network operators.
Phone numbers and alphanumeric senders
Check SMS coverage and connectivity for timelines by country, number type, and regulatory requirements.
How to speed up processing
- Submit complete documentation upfront
- Use clear, straightforward use cases
- Ensure all required information is accurate
- Respond quickly to any requests for additional information
Request resources through web interface
Step-by-step procedures for all resource types.
Request resources through API
Programmatic resource requests for automation.
Manage resources
Configure, manage, and route inbound messages after approval.