0 tips - $0.00
My Tips
No Tips!
The Tipalink API can be used to add tipping features to websites, web applications, and mobile apps.
Give your users the ability to monetize their content on your platform by integrating with the Tipalink API.
Contact us to inquire further.
This API is organized around REST.
API endpoints accept JSON-encoded request bodies and return JSON-encoded responses.
The API uses standard HTTP response codes, authentication, and verbs.
All API requests must be made securely over HTTPS.
All API POST body requests must be encoded as JSON and sent with the "Content-Type: application/json
" header.
API requests must be made over HTTPS and JSON-encoded.
A valid API key is required to access the API and a user token is required to identify and authenticate user sessions.
The API key must be provided in an Authentication header using HTTP Basic authentication - use your API key as the username.
API keys must be kept secret and secure; do not share them publicly. Use them only in server-side requests.
DO NOT use API Keys in client-side code!
The user token must be provided in an Authentication header using HTTP Basic authentication - use the token as the password.
Unless otherwise noted*, requests must include a user token.
Use HTTP Basic authentication to pass your API Key and a user token.
Example of an API request using Basic authentication:
curl -G https://www.tipalink.com/api/v1/account \
-u '[YOUR API KEY]:[USER TOKEN]'
* - a user token is not required for POST requests to 'api/v1/login', 'api/v1/account', and 'api/v1/profiles'; nor GET requests to 'api/v1/profiles', 'api/v1/countries', and 'api/v1/zones'.
Each API key is allowed no more than 3,600 requests are per hour and 300,000 requests per month.
You may opt-in to IP whitelisting for your API key.
All API responses are encoded as JSON and returned with the "Content-Type: application/json
" header.
API responses are encoded and returned in JSON format.
All responses to invalid requests are formatted as follows:
{
"status": [three digit HTTP Response Code, Integer],
"error": [error message, String]
}
All responses to valid requests are formatted as follows:
{
"status": [three digit HTTP Response Code, Integer],
"token": [base64 encoded user token, String or Null],
"data": [response data, Object],
"requests": [rate limit info, Object]
"error": [error message, String or Null]
}
All API responses to valid API requests include a user token, which is updated periodically for security purposes. Therefore, it is important to check the value of the `token`
parameter returned in each API response for a potential update before sending the next request.
User Tokens are updated periodically.
All responses to valid API requests include the following rate limit information returned under the `requests`
parameter for the API key supplied in the request:
{
"used": [number of requests used this month, Integer],
"remaining": [number of requests remaining this month, Integer],
"resets": [date and time when counter resets in Atom format, String]
}
All responses to invalid API requests include an error message that contains an HTTP status code and a description.
Excessive invalid requests* will result in a temporary ban!
* - i.e. those returing a 400-level status code
Select an API endpoint below to learn more.
Contact us to inquire further about using the Tipalink API.