Application and Entity Management
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.
Application
Get a paginated list of applications.
Create an application associated with the specified applicationId
.
Get an application for the specified applicationId
.
Modify a resource name
property.
Delete an application associated with the specified applicationId
.
Deleting an application will reset all resources that were linked to that application to application = default and entity = null. You should ensure that any configuration (like resource associations, inbound message configurations, subscriptions, bots, API Keys etc) related to given application are appropriately reassigned to other applications before attempting to delete the application.
Entity
Get a paginated list of entities.
Create an entity associated with the specified entityId
.
An entity attached to a submitted message will get auto created if it doesn't exit yet. It will get the entityId and entityName being the value passed on a message.
Get an entity for the specified entityId
.
Modify a resource name
property.
Delete an entity associated with the specified entityId
.
Deleting an entity will reset all resources that were linked to that entity to application = default and entity = null. You should ensure that any configuration (like resource associations, inbound message configurations, subscriptions, bots, API Keys etc) related to given entity are appropriately reassigned to other entities before attempting to delete the entity.
Resource association
Get a paginated list of resource associations.
Create a resource association.
Delete a resource association.
Get an exact resource association.
Need assistance
Encountering issues
What's new? Check out
Unsure about a term? See