DEVELOPER NOTES · Q2

What changed
in Forge API

One breaking change, three new endpoints, and a deadline worth putting in your calendar.

BREAKING CHANGE · 60 DAYS LEFT

v1 auth sunsets on June 30.

Keys issued on v1 stop working that day. Requests with v1 auth headers will get a 401, with no grace period.

# Authorization header

- Token fk_v1_4f9a…

+ Bearer fk_live_4f9a…

Moving to v2 bearer tokens takes about twenty minutes for most integrations. The guide covers the three setups we see most.

NEW IN V3

Three new endpoints

GET

/v3/usage

Per-key usage in one call, without paging through events.

POST

/v3/exports

Starts an async export and pings your webhook when it's ready, so you stop polling.

PATCH

/v3/webhooks

Change a webhook's URL without deleting and recreating it. Asked for since launch.

Also worth knowing

Rate limits doubled

Per-region status

1,000 requests a minute on Pro, up from 500. No action needed.

The status page now shows latency by region instead of one global number.

$ forge help

Migration questions?

The developer support channel is staffed on weekdays, by the people who wrote the API.

You're receiving this because you have a Forge developer account.

123 Example St, Suite 100, San Francisco, CA 94104