Plung API Notice: Authorization Bearer Tokens Are Now Required for Current API Authentication

Current authenticated Plung API requests must send API keys in the Authorization header using the Bearer scheme.

Effective immediately, the required request format is:

Authorization: Bearer your_api_key_here

The prior legacy custom API-key header format is retired and should no longer be used for current authenticated API traffic.

What Changed

Plung has standardized authenticated API requests on the Authorization header with the Bearer scheme.

This is a request authentication transport update. It does not change the underlying credential model. Your API key remains your API key. The required change is how that key is transmitted with each authenticated request.

The supported request header is now:

Authorization: Bearer <api_key>

The previous non-standard header format is no longer supported for current authenticated API usage.

Operational Impact

Any integration, script, client library, automation flow, gateway rule, or shared request utility that still transmits API keys through the retired header format should be updated without delay.

Teams operating production integrations should treat this as a configuration and request-format requirement. Authentication behavior should be validated at the edge of the calling system, including API clients, middleware, service wrappers, deployment templates, and integration test fixtures.

This update improves alignment with standard authorization handling across developer tooling, proxies, gateways, and managed infrastructure environments.

Required Actions

Existing integrations should complete the following actions:

1. Keep using the same active API key.
2. Replace the retired custom request header with Authorization: Bearer <api_key>.
3. Verify that every authenticated request path sends the Bearer-formatted header consistently.
4. Review shared utilities and templates first so dependent services inherit the updated request format automatically.

Migration Example With curl

curl -X POST https://api.plung.co/v2/shorten \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer your_api_key_here" \
  -d '{"url":"https://example.com"}'

Migration Example With fetch

const response = await fetch("https://api.plung.co/v2/shorten", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "Authorization": "Bearer your_api_key_here"
  },
  body: JSON.stringify({
    url: "https://example.com"
  })
});

const data = await response.json();
console.log(data);

Documentation

For current authentication guidance and request examples, refer to Authentication and Developer Documentation.