We built our API to be open and ready to serve new ideas as fast as our brilliant customers can dream them up.
First and foremost, our API documentation can be found here.
API Best Practices
To make the most of the API, BL.INK recommends the following as best practices.
Each user should use a unique account and API key for every integration
Each time the API is used for a new purpose (ex. social publishing tool integration, a sharing tool on a website, etc.), create a dedicated BL.INK account for that API integration.
Each account will be assigned a unique API key, which can be found on the My Account page. This will make reporting simple and straightforward in the long run since it’s easy to see which integrations generated which links.
For instructions on how to find the API key, check out this article.
Sign up for API notifications
Sign up for API notifications on the API documentation page. This will enable us to send important information on updates we make to our API.
Use a different API key for each domain
If a user has multiple domains in the BL.INK account (ex. go.mywebsite.com, mywebsite.me, etc.), users will need to use a different API key for each domain. These can be found by navigating to the My Account page and toggling between the domains in the drop-down menu at the top of the page.
Use SSL for all requests
Never publish the API key or share it insecurely
Do not send API keys in emails, or share them publicly in any way. If you feel the API key has been potentially compromised, please let us know and we will generate a new one.
Feel free to contact BL.INK support via email at firstname.lastname@example.org if you have any additional questions about our API.