B-LINK API
Connect your pages to a CRM, spreadsheets and automations: read leads and statistics, create pages and blocks from your own code.
What the API is for
- Leads from the «Lead form», «Booking», «Quiz» and other blocks land straight in your CRM, Google Sheet or Telegram via n8n, Make or Zapier.
- View and click statistics — in your own dashboards and reports.
- Bulk creation of pages and blocks: agencies and franchises set up dozens of pages by script, not by hand.
How to get a key
The key is issued on the BUSINESS plan under «Account → API». It gives full access to your account — never publish it or put it into page code. If it leaks, regenerate it in the same place.
How to make requests
Every address starts with the base URL. The key is sent in the Authorization header as a Bearer token. Responses are JSON; the limit is 60 requests per minute (429 when exceeded). Lists are paginated with page and results_per_page; the response carries meta with the total.
| Base URL | https://b-link.cc/api | |
| Authorization | header | Bearer {api_key} |
| Content-Type | header | application/json или application/x-www-form-urlencoded |
Example
curl "https://b-link.cc/api/user" \
-H "Authorization: Bearer {api_key}"Errors
On error you get an HTTP code and JSON like {"error": {"message": "…"}}: 401 — missing/invalid key or the plan has no API; 404 — object not found or not yours; 429 — rate limit; 400 — invalid parameters (message says which).
Resources
User
Your account and plan details.
Pages
Your pages, creating them, changing address, status and settings.
Page blocks
Blocks of a given page: list, add a block of a type with settings, update and delete.
Leads
Everything visitors left in forms, bookings, quizzes and polls — the same as the «Leads» section.
Statistics
Page views and clicks by day, country, device and source.
QR codes
Your QR codes: list, create, update, delete.
Pixels
Meta, TikTok, Google and other pixels you attach to pages.
Domains
Your connected domains.
Payments
Your plan payment history.
Sign-in log
Account sign-ins: date, device, city.
Page blocks — Example
The block type is a catalog key (hero, link, socials, contacts, catalog, booking, faq …). The settings field takes the same keys as the block form in the editor; unknown fields are dropped, images cannot be uploaded through the API.
curl -X POST "https://b-link.cc/api/biolinks-blocks" \
-H "Authorization: Bearer {api_key}" \
-H "Content-Type: application/json" \
-d '{"link_id": {link_id}, "type": "link", "settings": {"name": "Записаться", "icon": "fa fa-calendar-check"}, "location_url": "https://t.me/yourname"}'Leads — Example
curl "https://b-link.cc/api/data?link_id={link_id}&results_per_page=50" \
-H "Authorization: Bearer {api_key}"No-code integrations
In n8n, Make or Zapier add an «HTTP Request» step: GET, the leads address (see «Leads»), header Authorization: Bearer YOUR_KEY. Run it on a schedule every 5–10 minutes and pass new records on — to a CRM, a sheet or a messenger. Ready-made lead notifications to Telegram and email already exist under «Account → Notifications», no code needed.