ClickMagick API: which plan includes it, what it can do and where it stops

Does ClickMagick have an API? Yes, starting on the Starter plan

Yes. ClickMagick has a documented REST API, and its pricing page lists "API & Zapier Access" among the Starter plan features, which Standard and Pro build on. Starter costs $79 a month on monthly billing, or $790 a year on yearly billing, as read on 3 October 2026. The reference is labeled version 1.0 and uses the base address api.clickmagick.com/v1. Every call needs an API key sent in the X-APIKEY header. To create one, open Integrations in the account menu, choose API, then Generate API Key. We read the documentation and have not called the API ourselves.

The eight sections of the ClickMagick API reference

Stats and logs can be requested under five attribution models: first click, last click, linear, position based and time decay. Stats reports are asynchronous: the first call returns a report ID, and you poll it until the report is ready. For what connects to ClickMagick without code, see ClickMagick integrations.

ClickMagick API limits: rate limiting, page size and permanent deletes

• No fixed quota is published. Rate limiting is dynamic and based on how much work your requests caused over the past 5 minutes.
• A limited client gets HTTP 429 with a Retry-After header giving the wait in seconds. Send nothing more until it has passed.
• Logs are paged. Log endpoints return at most 100 items per page, with a cursor for the next page.
• Smart Link stats reports accept up to 20 link IDs per request.
• Large pulls trigger it. The documentation names fetching a lot of click or conversion data in a short time as the most common cause of rate limiting, and advises small pulls every hour or day.
• Scripting the web app is not allowed. Automated requests must go through the API.

Warning: delete calls are permanent. Deleting a Project through the API removes it together with all of its clicks, actions, engagements and sales, and deleting a Smart Link removes its clicks. Check every ID twice before a script sends a delete.

What the ClickMagick API does not cover, and what to use instead

The reference has no sections for billing, team members or ad platform connections, so those stay in the web app. The postback URL guide explains the server-to-server route in detail.

Worked example: a daily sales export on the Starter plan

[your business] wants yesterday's sales in a spreadsheet each morning. A scheduled job calls the sales log endpoint with a start and end time covering the previous day and a limit of 100, then follows the cursor until no next page is returned. At 250 sales a day that is 3 requests. This is the small, regular pull the documentation recommends. A job that asks for months of click data in one go is the pattern the documentation says will almost certainly be rate limited. Starter keeps 6 months of data, so a daily export also gives you a copy that outlasts that window.

Who the ClickMagick API suits and who needs something else

The API suits a marketer or developer who wants ClickMagick numbers in their own dashboard, needs to create Smart Links from a script, or is moving links in from another tool, which ClickMagick's import article says is done through the API. It is a poor fit if you need a guaranteed request quota, because none is published. If you want no code at all, use Zapier or webhooks. If you want a tracker built around redirect campaigns, see ClickMagick vs BeMob.