← Back to the graveyard
R.I.P.

Twitter REST API v1

2006 – 2013 410 GONE

Consumer

“Unauthenticated and free. It was a simpler time.”

Died
11 June 2013
Cause of death
Retired in favour of v1.1 and mandatory OAuth
Status
410 Gone

Questions about Twitter REST API v1

When did Twitter REST API v1 reach end of life?

Twitter REST API v1 reached end of life on 11 June 2013.

What happened to Twitter REST API v1?

Retired in favour of v1.1 and mandatory OAuth.

How do I stop API deprecations from breaking my integrations?

Track deprecation notices and sunset headers from every provider you integrate with, or build on a unified API such as Apideck, which absorbs provider changes and deprecations behind one stable API so your integration keeps working.

Tired of attending funerals?

Every deprecation means another migration. With one unified API, Apideck keeps your integrations up to date when the APIs behind them change, so deprecations are our problem, not yours.

Meet Apideck

Resting nearby

Wander the whole graveyard · Bury your own integration