Reference

Moving from the old API

Code written for the old email API at /api/v1 keeps working for seven days after pidgeon.ai moves to the new Pidgeon, then answers 410. What still answers, what does not, and the call to use instead.

Seven days, then 410

When pidgeon.ai moves to the new Pidgeon, your account, addresses, mail and API keys move with it. A key that reached only some addresses reaches only those inboxes. For seven days https://pidgeon.ai/api/v1 keeps answering the calls below with the same paths, keys, request and response shapes and error codes, on the new services. After that every /api/v1 call answers 410 gone.

Every answer says when: Deprecation is the day it was deprecated and Sunset the moment it stops (RFC 9745 and RFC 8594). A call with no equivalent answers 410 gone already, with a message pointing here.

Response
HTTP/1.1 200 OK
Deprecation: @1795521600
Sunset: Tue, 01 Dec 2026 12:00:00 GMT
Link: <https://pidgeon.ai/docs/old-api>; rel="deprecation"; type="text/html"

Note

Your old keys answer /api/v1 until the sunset. For /v1, make a key in the dashboard (API keys) and move to SDK 2.0 (@pidgeon-ai/sdk, pidgeon): see SDKs.

What still answers, and its new call

Old callNew call
GET /meGET /v1/email/inboxes lists what the key reaches
GET /identities, GET /identities/{id}GET /v1/email/inboxes, GET /v1/email/inboxes/{id}
POST /messages (from an address)POST /v1/email/inboxes/{id}/messages
POST /messages/{id}/reply, /reply-allPOST /v1/email/inboxes/{id}/messages with reply_to
POST /messages/{id}/forwardPOST /v1/email/inboxes/{id}/messages
GET /messages/{id}GET /v1/email/messages/{id}
GET /messages?thread_id=, GET /threads/{id}GET /v1/email/threads/{id}
GET /threads, GET /mailboxes/{folder}GET /v1/email/threads?inbox_id=&folder=
PATCH /messages/{id}, POST /messages/actionsPATCH /v1/email/threads/{id} (folder, starred), PATCH /v1/email/messages/{id} (seen)
PATCH /threads/{id}PATCH /v1/email/threads/{id}
DELETE /mailboxes/trashDELETE /v1/email/threads/{id}
GET /eventsGET /v1/events, or a webhook
GET /messages/await, GET /mailboxes/changesGET /v1/events from your last cursor, or a webhook
GET /messages/search, POST /messages/check, GET /metrics, GET /api-keysAnswered here until the sunset; on /v1, the list and read calls above

How they differ while they last: the new Pidgeon files conversations, not single messages, so moving or starring one message moves or stars its conversation. List rows carry no preview. send_at, data, reply_to and grant_ids on a send, and delete_forever, answer 410. A sync_cursor from before the move answers 410 resync: read the folder again and start from its new one.

Everything else

Every other /api/v1 call answers 410 gone from the move: webhooks, domains, labels, drafts, calendars, contacts, pods, keys, app passwords, agent cards and the card log. Their new calls are in the API reference.