Public API
Postman collection
Every Public API endpoint as a pre-filled Postman request, organized by resource folder. Import once, set eight variables, and explore the surface in your favorite HTTP client.
sigfollow-public-api.postman_collection.json
Postman Collection v2.1 · 5 folders · 19 endpoints
How to import
- Click Download above to save the JSON file.
- In Postman, open File → Import (or press
Ctrl/Cmd+O) and drop the file. - Open the imported collection's Variables tab and fill in the eight collection-level variables (see below).
- Pick a request, hit Send. The Bearer token at the collection level picks up
{{api_key}}automatically.
Collection variables
| Variable | What to set |
|---|---|
| {{base_url}} | Gateway base URL. Default https://api.sigfollow.com. |
| {{api_key}} | Plaintext API key with prefix sflo_live_. |
| {{phone_number_id}} | Meta phone number ID used by messaging / media endpoints. |
| {{waba_id}} | WABA ID used by template endpoints. |
| {{contact_id}} | Contact CUID used by contact endpoints. |
| {{tag_id}} | Contact tag CUID used by tag assignment endpoints. |
| {{blacklist_id}} | Blacklist row CUID used by patch / delete. |
| {{Recipient-Phone-Number}} | Target WhatsApp recipient phone in E.164 form without the leading +. Used by messaging / blacklist / contact lookup endpoints. |
Updating the collection
The downloaded file is a snapshot at publish time. New endpoints land in the same file at the same path — clients can re-import to refresh. Endpoint URLs are versioned under /v1 and are backwards-compatible within the major version, so existing requests in your local copy keep working as we add new ones.
If you need OpenAPI / Swagger format instead, the Public API surface is described inline in the docs (Quick start and the per-resource references). An OpenAPI 3.1 export is on the roadmap — until then this collection is the authoritative machine-readable artifact.