---
Source: https://docs.microblink.com/platform/release-notes/basic-auth
Title: API update: Basic Auth
---

# API update: Basic Auth

Starting with April 23, 2026, the [Agent API](/platform/api) supports [HTTP Basic Auth](https://datatracker.ietf.org/doc/html/rfc7617) as its primary authentication scheme.

### New behavior

This means that any keys generated after this date **cannot** be used with the previous Bearer scheme.
If you use [our transaction proxy](https://github.com/MicroblinkPlatform/microblink-platform-transaction-proxy) and you generate new keys, you **must** update to v2.0.0 of the proxy.

If you don't use our proxy, and you generate new keys, make sure that the mechanism you use to contact the Agent API now uses basic authentication:

```
Authorization: Basic {base64(client_id:client_secret)}
```

**Client IDs in new keys are prefixed with `sa_`.**

### Support for old keys

**The Agent API is backwards compatible.**

If you have keys that you have generated before April 23, 2026, they will continue working with the Bearer token scheme.

If you use [our transaction proxy](https://github.com/MicroblinkPlatform/microblink-platform-transaction-proxy) with old keys, keep using v1.0.0 of the proxy.
The v2.0.0 of the proxy **is not backwards compatible**.
Do not upgrade to it unless you also create new keys.

If you don't use our proxy, and use old keys, your authentication scheme remains unchanged.

:::tip[Our recommendation: upgrade]

If you already have API keys, we recommend that you delete them and reissue them, and that you upgrade your integration with the Agent API to use Basic Auth.

The new keys are better supported and offer more stability.

:::