Coming soon

REST API

A supported integration API is on the roadmap.

Interactive product demo

REST API

Planned preview

This is a non-operational product preview. It does not save, send, deploy, or call an API.

Proposed public API preview

Non-operational roadmap preview. Resource names are proposals only and do not describe current or private application routes.

Example data

All people, links, events, and metrics shown here are deterministic example data.

Coming soon

DrutoLink does not currently provide a supported public API.

  • Planned
  • Planned
  • Planned

What this feature does

A supported integration API is on the roadmap.

DrutoLink does not currently provide a supported public API. Scoped keys, versioned access, quotas, and integration documentation are planned.

Use this capability when you need more control than a basic short URL provides.

Implementation and operating details

The workflow stays attached to the short link, so you can manage the destination and its rules without replacing the URL already in circulation.

  • Planned
  • Planned
  • Planned

How it works

01

Create a scoped API key

The planned API will use revocable keys with explicit permissions instead of browser-session cookies.

02

Use the future public contract

Public link, campaign, and analytics access will be documented and versioned before integrations are supported.

03

Build integrations safely

Webhooks, SDKs, and automation connectors can follow once the authentication and public contract are ready.

Operational guide

How DrutoLink processes it

The preview illustrates a future supported contract with scoped keys, versioning, quotas, revocation, and documented resources. No supported public REST API or API keys exist today.

Understand the signals, processing order, fallback, and checks that matter before you rely on this capability.

Required inputs and signals

Configuration input
No public integration setup is available. Scoped API keys and a stable developer contract are planned.
Signals and connected controls
Planned

Decision, fallback, and common mistakes

Guest shortening and the web application are not substitutes for a public integration contract. Do not build against undocumented application behavior or preview request examples.

This capability is planned and cannot be used in the current product. The workflow below explains the intended direction, not a feature you can deploy today.

Implementation requirements preview

This capability is not available yet. Use this list to evaluate the planned workflow, not as current product instructions.

  1. 01 Create a scoped API key. The planned API will use revocable keys with explicit permissions instead of browser-session cookies.
  2. 02 Use the future public contract. Public link, campaign, and analytics access will be documented and versioned before integrations are supported.
  3. 03 Build integrations safely. Webhooks, SDKs, and automation connectors can follow once the authentication and public contract are ready.

Why teams use it

Scoped and revocable API keys planned
Stable public endpoint contract planned
Versioned integration documentation planned
SDKs and webhooks on the roadmap
Plan for authentication, rate limits, retries, idempotency, validation, and secret rotation before automating production link creation.

Measurement and reporting

Review click activity and the relevant link, campaign, audience, or variant breakdowns in DrutoLink analytics. Use consistent UTM parameters when results must also be reconciled with destination-side analytics.

What you can evaluate

Scoped and revocable API keys planned · Stable public endpoint contract planned · Versioned integration documentation planned

How to interpret results

A redirect click confirms that the link served a destination. It does not by itself prove a signup, purchase, or qualified visit. Compare the same date range and traffic definition before making a decision.

Current status and limitations

Coming soon

DrutoLink does not currently provide a supported public API.

This capability is planned and cannot be used in the current product. The workflow below explains the intended direction, not a feature you can deploy today.

Important boundary

Use the default destination and documented fallback behavior for cases where a rule cannot be evaluated. Test important links from representative devices and networks before broad distribution.

Do I need an SDK? DrutoLink does not currently provide a supported public API. Scoped keys, versioned access, quotas, and integration documentation are planned.

Best use cases

Practical examples

These are common situations where the capability can reduce manual link changes or make reporting easier to understand.

  • 01 Generating links from your own app
  • 02 Automating campaign link creation
  • 03 Integrating links into internal tools
  • 04 Connect a CMS, campaign workflow, internal tool, or publishing pipeline once the documented public API is available.

Is this the right fit?

Choose this feature when

You need one controlled short URL, a repeatable operating workflow, and reporting that stays connected to the link. Scoped and revocable API keys planned

Use another approach when

Your requirement depends on a capability marked partial or planned, requires identity-level certainty, or needs conversion attribution that must be measured in the destination product.

Frequently asked questions

Do I need an SDK?

DrutoLink does not currently provide a supported public API. Scoped keys, versioned access, quotas, and integration documentation are planned.

Can I use the API without an account?

No. Guest shortening is a browser workflow, remains separate from account links, and is not supported for scripts or third-party services.

Are API keys available?

No. API keys, documented endpoints, versioning, quotas, and compatibility guarantees are still planned.

Build a link that fits the job

Start with the free plan