Getting Started

This guide takes you from zero to your first Bizgate Partner API call.

Use it to understand what Bizgate is, how authentication works, how to obtain credentials, and how rate limits and errors behave before you explore the full API Reference.

Base URL (production): https://partner.gupshup.io/partner/bizgate

Introduction to Bizgate

Bizgate is Gupshup’s partner platform for WhatsApp Business API integrations. It gives partners APIs and portal tools to onboard customers, manage WABA apps, send messages, and operate at scale.

With Bizgate you can:

• Integrate Bizgate Partner APIs into your own product or branded UI
• Manage apps, templates, profiles, wallets, and onboarding via REST
• Use the Bizgate Partner Portal for operational workflows
• Optionally offer a white-labeled Bizgate Partner Customer Portal to your customers

Partners are typically Independent Service Providers (ISVs) or Tech Providers (TPs) building WhatsApp solutions on top of Gupshup.

Path to your first API call

1. Authentication

Every authenticated Bizgate request must carry a Universal Token in the Authorization header:

Authorization: Bearer <Universal Token>

Public routes (for example login, signup, and Swagger/docs surfaces) do not require auth.

2. Obtaining API Keys

After you have a UT:

1. Pick an endpoint from the Bizgate API Reference
2. Send a request to https://partner.gupshup.io/partner + the endpoint path
3. Include the Authorization: Bearer <UT> header

Example:

curl -X GET \
  "https://partner.gupshup.io/partner/bizgate/app/{appId}/profile" \
  -H "Authorization: Bearer <Universal Token>" \
  -H "Accept: application/json"

Replace {appId} and <Universal Token> with your values.

3. Rate Limits

Bizgate applies per-endpoint, per-caller sliding window rate limits. When a limit is exceeded, the API returns 429 Too Many Requests.

Design retries with backoff when you receive 429. Endpoint-specific limits may also be documented on individual API reference pages.

4. Error Codes

All error responses share this shape:

{
  "status": "error",
  "message": "<human-readable>"
}

5. Webhooks Overview

Webhooks are HTTPS callbacks that deliver inbound WhatsApp messages and message status events to your platform in real time.

When a customer messages your WhatsApp Business number — or when a message you sent is sent, delivered, read, or fails — Gupshup posts an event to the callback URL configured for that app.

Why set up webhooks

How to configure

1. Expose a publicly reachable HTTPS endpoint that can receive POST requests
2. Create a subscription for your app with a callback URL — see All subscription APIs
3. Choose the event modes/versions your integration needs
4. Acknowledge each notification quickly, then process the payload asynchronously

Common subscription operations:

All of these require Authorization: Bearer <UT>.

Webhook requirements

Next steps