Seeing this error?

INVALID_SCREEN_DATA
Property 'example' is allowed only as a top level property of data model. Invalid entry: '(path to error)'.

That means you've placed the __example__ field inside a nested schema, which is not allowed in WhatsApp Flows.

The Fix (TL;DR):

Move the __example__ property to the top level of your data model — not inside properties or nested objects.

Correct:

"data": {
  "initial_values": {
    "type": "object",
    "properties": {
      "number": {
        "type": "number"
      }
    }
  },
  "__example__": {
    "initial_values": {
      "number": 8553906697
    }
  }
}

Incorrect:

"properties": {

  "number": { "type": "number" },

  "__example__": { "number": 8553906697 }

}

Why This Happens

WhatsApp Flows uses __example__ for previewing and testing data, but it only supports it at the root level of the data object. Nesting it inside properties or any sub-object results in an invalid schema.

In your original schema:

"initial_values": {
  "type": "object",
  "properties": {
    "number": { "type": "number" },
    "__example__": { "number": 8553906697 } // Invalid
  }
}

This usage breaks the schema validation.

Best Practices

  • Always define __example__ alongside your top-level data fields, not inside nested objects.

  • Structure it to match the shape of your data model for clear previews and debugging.

  • Keep your schema clean by separating structure (type, properties) from sample data (__example__).

This error is all about placement. Once you know that __example__ belongs only at the top, it’s a quick fix. Keep your data model clean, and your Flow will stay error-free. For more troubleshooting insights related to WhatsApp Business API, check out heltar.com/blogs.