---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/api/errors/13234#article
headline: "13234: Dial->Conference: Invalid waitMethod"
url: https://www.twilio.com/docs/api/errors/13234
inLanguage: en
dateModified: 2026-06-08T11:29:20.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# 13234: Dial->Conference: Invalid waitMethod

Log Level: WARNING

## Description

Set `waitMethod` on `<Conference>` to `GET` or `POST` only. Twilio uses this attribute when requesting `waitUrl` before the conference starts. If you specify `waitUrl`, the default method is `POST`. If you do not specify `waitUrl`, Twilio requests the default hold music with `GET`. Use `GET` when `waitUrl` points directly to a static WAV or MP3 file so Twilio can cache it.

### Possible causes

* The `<Conference>` noun sets `waitMethod` to a value other than `GET` or `POST`.
* Your application generates TwiML with an unsupported HTTP method for `waitUrl`.
* You configured `waitUrl` for pre-conference audio or TwiML, but the associated `waitMethod` value is not valid.

### Possible solutions

* Update the `<Conference>` noun so `waitMethod` is set to `GET` or `POST`.
* Use `GET` when `waitUrl` points directly to a static WAV or MP3 file.
* If `waitUrl` returns TwiML, make sure your application accepts the same `GET` or `POST` method you configured in `waitMethod`.
* If you do not need custom hold music or pre-conference TwiML, remove the custom `waitUrl` and let Twilio use the default hold music behavior.

#### Additional resources

* [TwiML `<Conference>`](/docs/voice/twiml/conference)
* [TwiML `<Dial>`](/docs/voice/twiml/dial)
* [Conference Participants API](/docs/voice/api/conference-participant-resource)