API Documentation

The Netify REST API lets you send messages, upload media, and read runtime configuration. All endpoints are served under the /api base path.

Authentication

Protected endpoints use Sanctum bearer tokens. Send the token in the Authorization header:

Authorization: Bearer {your_token}

Create tokens for your agents from the dashboard. Never share your token.

1. Send a message

Request body

{
  "to": "91XXXXXXXXXX",        // recipient phone number with country code
  "template_name": "welcome",  // optional: approved template
  "language": "en_US",         // required when using template_name
  "body": "Hello!"             // optional free-form text (conversation type)
}

2. Upload media

3. Runtime configuration

Public, no authentication required. These never expose secrets.

• GET /api/v1/meta/public-config — Meta connection presence & app config for the client.
• GET /api/v1/app/public-config — app name, base URL, locale, timezone, maintenance flag.

4. Webhooks

Meta Cloud API verification and event delivery.

• GET /api/webhook — hub verification handshake (challenge token).
• POST /api/webhook — receives signed events; validates X-Hub-Signature-256 and stores events idempotently.

5. Authenticated user

• GET /api/user — returns the authenticated user's profile.

Embedded Signup (in-app)

The embedded signup flow runs inside the authenticated tenant web app and is CSRF protected. Endpoints are exposed under /api/v1/meta/connect/start, .../connect/complete, and /api/v1/meta/connections for listing, status, reconnect, and disconnect.