Read API
The API is designed to read useful account, campaign and short-link data from an internal tool, reporting workflow or automation. Write access remains deliberately more cautious.
Developer solution
API and webhooks to automate your links
Teams that want to connect Linka Factory to reporting, CRM or automation can read key objects through the API and receive click events by webhook.
Useful for
- Internal reporting
- CRM, Make, Zapier and BI
- Teams that need careful automation
Business impact
- Read account, campaigns and links.
- Click events sent in the background.
- HMAC signatures and controlled retries.
Guardrails
- Read API in beta.
- Management reserved to the owner.
- Anti-abuse validation for webhook endpoints.
Outgoing webhooks
Webhooks send click events to a customer receiver with HMAC signature, retries and delivery logs. The goal is to connect Linka Factory to a CRM, Make, Zapier, BI or internal tool.
Integration guardrails
Keys, scopes and endpoints stay isolated by account. Team members do not manage these sensitive settings, and webhook URLs are validated to reduce network abuse.
Connect without opening too many rights
A healthy integration starts with limited scopes, a separate key and controlled receiving endpoints. The goal is not to give a third-party tool the whole account, but to send useful data to the right place.
Webhook as an asynchronous signal
A public click should not wait for a CRM or automation tool. Linka Factory records the click, then delivers the event in the background with signature, retries and delivery logs.
Related guides
Continue with the closest workflows.
For the next step, see read click analytics.
For the next step, see URL routing by country, device and source.
For the next step, see documentation.
For the next step, see API documentation.
Official references
When should you use API and webhooks?
When a published link must not become frozen: an already launched campaign, a printed asset, a destination to correct, a weak source to cut or analytics to make readable.
What is the concrete gain?
Less manual rework, less lost traffic, more visibility on clicks and a better ability to correct without rebuilding the whole distribution.
Next reading