JustPush.io
  • Introduction
  • New? Start Here
  • The Glossary
  • USER MANUAL
    • Getting Started
    • API Key
    • JustPush Email
  • OBJECTS
    • Messages
      • Title
      • Topic
      • Message
      • Priority
      • Sounds
      • Images
      • Acknowledgements
      • Buttons
      • Button Groups
      • Expiry TTL
    • Topics
      • Title
      • Avatar
  • DEV TOOLS
    • API reference
      • Messages
      • Topics
    • OpenAPI
    • Rapid API
    • Postman
    • SDKs
    • Changelog
Powered by GitBook
On this page
  • Use Cases
  • Requirements
  • Example Request
  • Mobile App
  • Frequently Asked Questions
  1. OBJECTS
  2. Messages

Button Groups

Button groups let you bundle up to 4 groups of related buttons, each with its own name, CTA, and action requirement. Inside a group, you can have up to 10 buttons, each with its own CTA and URL. 🚀


Sometimes, a single button just doesn’t cut it. Button groups allow you to categorize multiple actions under a single section, making notifications more organized and user-friendly.

  • Up to 4 groups per message.

  • Each group has a name (e.g., "Response Options").

  • Each group has a CTA (max 25 characters) to describe its purpose.

  • Action Required Option: Decide if a group must be used before dismissing the notification.

  • Each group contains up to 10 buttons.

  • Each button has its own CTA (25 char max) and unique URL.

Use Cases

Some actions naturally belong together. Button groups make it easy for users to pick the right one without clutter.

Good Use Cases

✅ Incident Response: "Server Down! Choose an action"

  • "🔧 Restart" | "📅 Schedule Fix" | "❌ Ignore"

✅ Order Management: "Order #12345 - What next?"

  • "🚚 Ship Now" | "🔄 Change Address" | "🛑 Cancel Order"

✅ Survey or Feedback: "How was your experience?"

  • "😀 Great" | "😐 Okay" | "😞 Bad"

Bad Use Cases

❌ Cramming all possible actions into one group. (Too much choice = confusion.) ❌ Using long CTAs. ("Click this button if you want to approve the request immediately") ❌ Mixing unrelated actions. ("Call Support" and "Delete Account" in the same group? Yikes.)

Requirements

Attribute
Data Type
Validation Criteria

buttons_groups

array

max 4 items

buttons_groups.*.name

string

max 150 characters

buttons_groups.*.cta

string

max 25 characters

buttons_groups.*.action_required

boolean

sets a pending action

buttons_groups.*.buttons

array

max 10 items

buttons_groups.*.buttons.cta

string

max 25 characters

buttons_groups.*.buttons.url

string

a valid url

Example Request

curl -X "POST" "https://api.justpush.io/messages" \
     -H 'Content-Type: application/json' \
     -d $'{
  "user": "<< USER KEY>>",
  "message": "A simple test message",
  "title": "A simple title",
  "button_groups": [
    {
      "buttons": [
        {
          "cta": "Button1",
          "url": "https://www.action1.com",
          "requires_action": false
        },
        {
          "cta": "Button2",
          "url": "https://www.action2.com",
          "requires_action": true
        }
      ],
      "name": "Group 1",
      "cta": "Group 1 Cta",
      "action_required": true
    }
  ]
}'

Mobile App

Below you see an example of how this displayed as a push message and within the app.

Push Message

JustPush.io App


Frequently Asked Questions

Can I mix standalone buttons with button groups?

Yes! You can use both in the same message. Go wild!

What happens if action_required is true?

Users must interact with at least one button from the group before the notification can be dismissed.

Do buttons inside a group share the same URL?

Nope! Each button can have its own unique URL.

Can I have more than 4 groups?

No, the max is 4 groups per message with up to 10 buttons each—keep things tidy!

PreviousButtonsNextExpiry TTL

Last updated 1 month ago

Push Message with Title and Message
Message with a button group
The button group openend