Connect your own system to your publisher catalog, backlink orders and saved-link monitoring. Build a request, choose its permissions and follow the real result in your account.
No credit charge
Send the key in the Authorization: Bearer header over HTTPS. Keep it on your server, never in public browser code or URLs. Examples read API_KEY from the environment.
curl --fail-with-body --request GET 'https://panel.starbacklink.com/api/v1/credits' \
--header "Authorization: Bearer ${API_KEY}"Send the key in the Authorization: Bearer header over HTTPS. Keep it on your server, never in public browser code or URLs. Examples read API_KEY from the environment.
60 requests per key per minute, 120 per account per minute and 10,000 per account per UTC day. Usage totals cover 30 days; the latest 500 records per key are retained for up to 30 days.
Catalog names and domains are hidden at zero balance. Publisher details for your own paid links remain visible. Catalog metrics are supplier observations, not fresh analytics reports.
HTTP 202 means accepted for processing, not published. Inspect your order or monitor to see the current result.
Refunds do not reset a key’s daily spending counter. Accepted order responses are retained for safe retries; repeated requests do not create another charge.
This API provides your account data and checks known source/destination pairs. It does not discover every backlink on the web or supply a third-party link index.
Create a key in Developer API. Start with credit, catalog, order and monitor read permissions. Set an expiry and keep the secret on your server.
Choose an operation and language below. For a paid order, copy the publisher ID and current price from the catalog, select the months and review the cost.
For a write, choose one UUID and keep it with the exact request body. Send the request from your server, save its receipt and read the order or monitor for progress.
02 / Worked example
Example: a publisher priced at 2 credits per month costs 6 credits for a three-month placement. A key with a daily limit of 5 rejects it with DAILY_CREDIT_LIMIT; a limit of 6 permits it if your verified account has enough credits and stock is available. Retrying the accepted request with the same UUID reserves no additional credits.
03 / How to read the results
60 requests per key per minute, 120 per account per minute and 10,000 per account per UTC day. Usage totals cover 30 days; the latest 500 records per key are retained for up to 30 days. This API provides your account data and checks known source/destination pairs. It does not discover every backlink on the web or supply a third-party link index.
This API provides your account data and checks known source/destination pairs. It does not discover every backlink on the web or supply a third-party link index. Catalog names and domains are hidden at zero balance. Publisher details for your own paid links remain visible. Catalog metrics are supplier observations, not fresh analytics reports.
Choose a UUID once for each new write and reuse it for retries. The same successful request returns its original result; different data with that UUID returns 409. Check the order endpoint for current status. Refunds do not reset a key’s daily spending counter. Accepted order responses are retained for safe retries; repeated requests do not create another charge.