Getting started
Authentication
AppLink APIs do not use tokens or Authorization headers. Every request is a POST that carries its own credentials in the JSON body: applicationId and password.
Your credentials
applicationId is the unique identifier generated when you provision an application, in the form APP_000001. password is the API key sent to your registered email address on the platform once the application is approved.
Requests must also originate from an IP address that has been provisioned for your application.
Authenticating a request
Send the credentials alongside the rest of the payload. Every endpoint uses the same base URL and content type.
application/json;charset=utf-8
curl -X POST https://api.applink.com.bd/sms/send \
-H "Content-Type: application/json;charset=utf-8" \
-d '{
"version": "1.0",
"applicationId": "APP_999999",
"password": "your-api-key",
"message": "Hello",
"destinationAddresses": ["tel:+8801959979376"]
}'When authentication fails
AppLink reports failures in the response body rather than through HTTP status codes. Check statusCode on every response.
JSONstatusCode
{
"statusCode": "E1313",
"statusDetail": "Authentication failed. No such active application with applicationId APP_999999, or no active service provider or the given password in the request is invalid."
}E1303 | IP address from which this request originated is not provisioned to send requests to application <application-id>. Please use a provisioned system to send requests or contact system admin to provision the new IP. |
|---|---|
E1312 | Request is invalid. <specify_the_reason> Refer the TAP NBL API Developer Guide for the mandatory fields and correct format of the request. |
E1313 | Authentication failed. No such active application with applicationId <application-id>, or no active service provider or the given password in the request is invalid. |