# 21713: Messaging Service Use Case is Invalid

Log Type: APPLICATION

Log Level: ERROR

## Description

This error occurs when you create or update a Messaging Service with a `usecase` value that isn't supported. Supported values for `usecase` are `notifications`, `marketing`, `verification`, `discussion`, `poll`, and `undeclared`.

### Possible causes

* The request includes a `usecase` value that isn't in the supported list.
* The `usecase` value is misspelled or uses different casing than the supported values shown in the API reference.
* Your application sends an internal label or another category instead of a valid Messaging Service `usecase` value.

### Possible solutions

* Update the request so `usecase` is exactly one of these values: `notifications`, `marketing`, `verification`, `discussion`, `poll`, or `undeclared`.
* Check your request payload and normalize the `usecase` value before you send it so it matches a supported value exactly.
* If your traffic doesn't fit one of the named categories, use `undeclared` for the Messaging Service `usecase`.

#### Additional resources

* [Service resource](/docs/messaging/api/service-resource)
* [Get started with Messaging Services](/docs/messaging/tutorials/send-messages-with-messaging-services)
* [Programmable Messaging and A2P 10DLC](/docs/messaging/compliance/a2p-10dlc)