Platform

Infobip's Two Factor Authentication API for OTP (One Time Passcode) delivery and verification. OTPs can be delivered over SMS, Voice or Email. Learn more about the workflow and setup. You can use SDKs and other available tools to help you with integration.

Manage your Infobip account details, such as individual users and api keys.

Applications and Entities are designed to be flexible and modular to give you the opportunity to define your business environment, use cases, applications, customers, assets, etc. on the Infobip platform, so you don't have to manage the complexity of a CPaaS execution.

Applications and Entities share some similarities. You can apply the same types of configuration and resources to them. The difference between the two is that they represent different "actors" or "objects" in your ecosystem.

You can use them separately or together, according to your business needs. Applications and Entities can be associated to whatever Resources you own. Resources, in this context, are things you purchase or register through Infobip, such as Short Codes, VLNs, US 10-Digit-Long-Codes, Alphanumeric Senders, Email domains, and ChatApp IDs.

Concepts Explained

Applications - represent a concept of application, environment, or use case on your system on the Infobip Platform. For example, a Production and Test environment could be two different Applications, or a Marketing and an E-Commerce use case could be two different Applications.

Entity - represents an "actor" or an "object" in your system within the Infobip platform. For example, it could represent one of your customers, or a department, or a cost centre within your organization.

Resource Associated - When Resources have been obtained and Applications and/or Entities have been created, you can then associate a Resource to an Application and/or Entity. You can query a list of all resource associations or query on a specific resource. ResourceAssociations are only used to group resources (senders) for usage in Smart sending strategies.

Numbers are essential for two way communication and your branding. Buy and manage your numbers to send and receive messages and voice calls.

Subscriptions are a way to manage notifications sent to your webhooks by Infobip. It is a useful feature if you want to narrow down the list of events to be notified about or specify different webhooks for different use cases. It will also allow you to set up authentication settings for your endpoint.

If you want mutual TLS on the webhook you will receive notification events, you can upload and manage the certificate that Infobip will present to you in order to verify Infobip's authenticity. For details see documentation.

Metrics API is a way to access aggregated traffic information. By integrating this API, you can retrieve analytics related to your communications and build your own reporting facilities.

Sending Strategy represents one type of configuration for your sending resources. This configuration in its simplest form allows you to set manipulation for your senders on a country level for a specific channel (SMS/MMS) on an Entity or Application-Entity level (read more about Entity and Application here). Sending Strategies have additional functionalities on top of sender manipulations, like Sticky sender (same sender used for all messaging towards the same destination) and Geolocated sender (sender picked based on the local area code of the customer receiving the message). More about Sending Strategy Management, available features, and future development can be read here.

Sending Strategy types:

• Application-level Sending Strategy (also called the Default Sending Strategy)
  • A strategy that distributes sending across the pool of senders that are automatically fetched based on the definition you specified in Resources Associations.
• Entity/Application-level Sending Strategy
  • A strategy used for client-specific setup. You can define different rules, features, and limitations for each client of yours.
• Additional features
  • Geolocated Sender - by turning on this feature, traffic will be sent from one of the defined senders that have the same local area code as the customer receiving the message. Customers are more likely to positively react to a message if it comes from a number from their local state. Note: Geolocated sender can be used for terminating messages in North America only.
  • Sticky Sender - by turning on this feature, when a customer receives a message from one of the defined senders then the same sender will be used for all further messages sent to that customer. Customers are more likely to positively react to a message if it comes from a consistent number connected with some brand/company.
  • Note: A geolocated sender and a Sticky sender can be used in combination.
  • Sender Type Priority - enables you to define the priority of your senders in case you have more than one sender for a destination country.
  • Coming soon:
    • Default Sender - enables you to define a sender that would be used in case a message does not pass with your Entity-specific sender/s. This can be defined per each Entity differently or can be defined as a default sender on the Application level.

Note: When the "from" field (sender) is defined along with application and/or entity in the sending API call, it overrides the Sending Strategy configuration and sender manipulations will not apply

Phone numbers and email addresses (referred to as destinations) that no longer want to be contacted are stored inside a Blocklist (also known as Do Not Contact List)

This platform feature is used to make sure that no communication is sent to recipients who have opted out of your communication campaigns.

With the Blocklist API, you are able to programmatically manage and track the list of recipients who want to stop receiving communication from your company while remaining compliant with important personal data regulations, such as GDPR.

Create and manage your catalogs to use with other Infobip solutions. Catalogs are similar to databases, you can store and retrieve data sets.

Concepts explained

• Catalog - a set of records. Each record can be for a product or service.
• Item - a record within a catalog. An item could be a product or service.
• Field - define the data structure for the items in the catalog.

The Messages API integrates multiple messaging channels into one interface. Instead of using a separate API for each messaging channel, use only one API for multiple channels and message types.

Signals is a solution for detecting and blocking artificially generated traffic.

Each mobile device has a unique identifier assigned to it. It's called a Mobile Station International Subscriber Directory Number.

Use this API to create a list of trusted MSISDNs and add/remove numbers from it.

Numbers added to a MSISDN list are excluded from blocking.

The Resources API is a set of endpoints designed to manage and request communication resources, such as alphanumeric senders and numbers. Automate resource registration, validation, and provisioning to reduce manual workload.

The Resources API contains the following sections:

• Resource Management – Get the resources you have already, check SMS coverage for alphas and numbers, and manage inbound configuration
• Resource Request – check the necessary requirements, then submit and track requests for new resources, and receive request status updates on a webhook