INinfobip
platform
application-entity
resource-association

Create resource association

Create a resource association.

post/provisioning/1/associations

Request

  • Base URL
    https://api.infobip.com (the document declares no server; this is the origin it was published from)
  • Auth
    • API key in header Authorization
    • or API key in header Authorization
    • or HTTP basic
    • or OAuth 2
      Client credentials
      Token URL: https://api.infobip.com/auth/1/oauth2/token

Request body

resourceType'NUMBER' | 'DOMAIN' | 'ALPHA' | 'RCS_RESOURCE' | 'APPLE_RESOURCE' required

The type of resource to be used.

channel'SMS' | 'MMS' | 'EMAIL' | 'WHATSAPP' | 'RCS' | 'APPLE' required

The channel for which the resource will be used.

applicationIdstring required

The unique identifier of the application. This ID will be a URL path parameter. We recommend using values that do not need URL encoding for easier interaction with other API endpoints.

entityIdstring required

The unique identifier of the entity. This ID will be a URL path parameter. We recommend using values that do not need URL encoding for easier interaction with other API endpoints. If no entity is associated with this resource, set the entityId to null.

resourceIdstring required

The unique identifier of the resource. It depends on both the resourceType and channel.<br/>Use numberKey for the NUMBER resourceType.<br/>Use domainName for the DOMAIN resourceType, which is available only for the Email channel.

Example request

{
  "applicationId": "test-application",
  "entityId": "test-entity",
  "resourceId": "test-resource"
}

Response

Created

Changes

No recorded changes to this operation across all 1 revision of this API.