# E01034 — WhatsAppKeywordCatalogueUnavailable

The WhatsApp keyword catalogue could not be read, so these rules were refused rather than returned without the keywords Bird ships.

- **HTTP status**: `503`
- **Type**: `service_unavailable_error`
- **Name**: `WhatsAppKeywordCatalogueUnavailable`

## What to do

Retry with backoff over the next five minutes, then stop and contact support with the `request_id`. Every workspace inherits Bird's opt-out and opt-in keywords, so an empty list would misreport them as absent; each instance reloads the catalogue on a five-minute cycle, so a retry budget shorter than that can expire before the next attempt to load it.

## Related

- [E01xxx — Infrastructure](/docs/api/errors/E01xxx): every code in this range
- [Errors](/docs/api/errors): the full wire contract, status mapping, and error catalog
- [Error handling](/docs/guides/errors): branching on `type` and `code`, validation details, and `vendor_code`

## Related resources

- [Should I use a Bird SDK or call the API directly?](/explained/platform/should-i-use-an-sdk-or-call-the-api-directly) (answer)
- [Build your first integration](/learn/paths/integration) (course)
- [Send your first email](/docs/get-started/send-your-first-email) (docs)

[Get an implementation brief](/learn/workspace?topic=api-basics)