API-First Platform

API-first ticket management with a unified inbox

A modern, developer-friendly support platform where every operation is an API call. Tickets, unified inbox, webhooks, email pipeline, and 157 REST endpoints — all automatable.

GoPimi dashboard with ticket management and analytics
// List tickets with filters
GET /api/v1/workspaces/1/tickets?status=open&priority=high

{
  "data": [
    {
      "id": 142,
      "subject": "Ticket #142 - Login page not loading",
      "status": "open",
      "priority": "high",
      "contact": { "name": "Jane Cooper", "email": "[email protected]" },
      "agent": { "name": "Alex Chen" },
      "tags": [{ "name": "bug", "color": "#ef4444" }],
      "sla": { "first_response_due": "2026-03-09T14:00:00Z" },
      "created_at": "2026-03-09T10:32:00Z"
    }
  ],
  "meta": { "current_page": 1, "total": 47 }
}

Built for teams that automate

SaaS Teams Dev Agencies Startups MSPs Solo Developers
157
API Endpoints
24
Database Models
616
Automated Tests
4
Background Job Queues
Core Philosophy

API-First, Everything Automated

Every operation in GoPimi is available through a clean REST API. Create tickets, manage contacts, assign agents, run bulk actions — all programmatically. Unlike traditional helpdesks that bolt on APIs as an afterthought, GoPimi was designed API-first from day one. Every feature in the dashboard has a corresponding API endpoint, making it straightforward to integrate with your existing tools, build custom workflows, or automate repetitive support tasks.

  • 157 REST endpoints with personal access token authentication
  • Interactive API documentation with try-it-now
  • Bulk actions API (assign, close, spam, trash)
  • Contact management with 7 custom field types
  • Canned responses with template variables, tags, and organizations
  • Webhooks with HMAC-signed payloads and retry logic
  • Resource quotas and usage tracking per workspace
API-first server architecture powering ticket management
Email Pipeline

Emails In, Tickets Out

Inbound emails automatically become tickets or conversations. Agent replies go out as emails. CC recipients are tracked per message. Attachments are handled. Proper Message-ID and In-Reply-To threading keeps everything organized in your customers' email clients. Connect your existing email addresses via custom domain DNS, email forwarding, or MX records — no need to switch providers.

  • Automatic ticket creation from inbound email
  • Proper Message-ID/In-Reply-To/References threading
  • Per-message CC with Reply All support
  • File attachments up to 25 MB per file
  • Custom domain email addresses with DKIM verification
  • Email forwarding — no MX records or provider changes needed
  • Smart forwarding: one rule handles multiple workspace emails
  • SLA tracking with automated breach detection and alerts
Email pipeline converting inbound emails into tickets
Multi-Tenancy

One Account, Multiple Workspaces

Run separate support operations for different products, clients, or teams from a single account. Each workspace is fully isolated with its own tickets, contacts, email addresses, tags, and settings. Invite team members with role-based access — owners manage configuration, members handle day-to-day support. Resource quotas keep usage in check across workspaces.

  • Workspace-scoped data isolation
  • Owner and member role-based access control
  • Token-based team invitations with accept/decline
  • Custom domain email addresses per workspace
  • Independent tags, contacts, organizations, and settings
  • Plan-based resource quotas with per-workspace overrides
Multiple workspaces with isolated data and team collaboration
Three Workflows, One Platform

Tickets, Shared Inbox & Personal Inbox

Not every email needs a ticket. GoPimi gives you three distinct workflows in one platform: structured ticket support with SLA tracking, a shared inbox for team conversations visible to all members, and a personal inbox for private conversations owned by individual users. Each workspace email is purpose-routed automatically — support@ creates tickets, info@ lands in the shared inbox, and your own address goes straight to your personal inbox.

  • Purpose-based routing: tickets, shared inbox, or personal inbox per email address
  • Shared inbox: team conversations visible to all workspace members
  • Personal inbox: private conversations owned by and visible only to one user
  • Personal conversations auto-assigned to the inbox owner
  • Targeted notifications: personal emails notify only the owner; shared emails notify the team
  • Compose, reply, and Reply All across all workflows
  • Contact linking across tickets and conversations
  • Draft messages — auto-save on blur, continue from any device, full API support
  • Tags, spam detection, trash, and bulk actions on all list pages
Tickets, shared inbox, and personal inbox in one platform
Developer Experience

Built by Developers, for Developers

Clean API design, personal access tokens, predictable responses, and auto-generated OpenAPI documentation. Every endpoint follows the same patterns — consistent JSON responses, standard pagination, and predictable error handling. Generate API tokens from the dashboard and start making requests in seconds. The interactive docs let you test endpoints directly in your browser.

  • Auto-generated OpenAPI 3.1 docs with 157 endpoints
  • Personal access token authentication
  • Consistent JSON response format with error codes
  • Pagination, filtering, and search on all resources
  • Activity log and immutable audit trail
  • 616 automated tests covering the full API surface
cURL
# Create a ticket via API
curl -X POST https://api.gopimi.com/v1/workspaces/1/tickets \
  -H "Authorization: Bearer your_token" \
  -H "Content-Type: application/json" \
  -d '{
    "subject": "Login page not loading",
    "description": "Users report a blank screen...",
    "contact_id": 42,
    "priority": "high"
  }'
Webhooks, Notifications & SLA

Real-Time Events, Never Miss a Deadline

Build automations with webhooks that fire on every ticket, conversation, and contact event. Define SLA policies that track first response and resolution times per priority level. GoPimi checks for breaches every 5 minutes and alerts your team automatically. Email notifications cover ticket assignments, replies, conversation messages, status changes, and SLA breaches — each configurable per workspace with secure one-click unsubscribe.

  • Webhooks with 15 event types and HMAC-SHA256 signatures
  • Automatic retry with exponential backoff and delivery logs
  • SLA policies with configurable targets per priority
  • First response and resolution time tracking
  • Automated breach detection every 5 minutes
  • 5 notification types with per-workspace toggles
  • Secure HMAC-signed one-click email unsubscribe
SLA tracking with automated notifications and breach alerts

Simple, Transparent Pricing

Start small, scale as you grow. All plans include the full API.

Lite

$9 / mo
14-day free trial · billed monthly
  • 1 workspace
  • 2 team members
  • 5 email domains
  • 50 contacts
  • Full REST API access
  • Email notifications
Start Free Trial

Business

$79 / mo
14-day free trial · billed monthly
  • 3 workspaces
  • 20 team members
  • 25 email domains
  • 500 contacts
  • 2 GB storage
  • Everything in Pro
Start Free Trial

Frequently Asked Questions

Is GoPimi free?
GoPimi starts at $9/mo for the Lite plan with 1 workspace, 2 team members, and 5 email domains. All plans include a 14-day free trial. Pro ($29/mo) adds more workspaces, 10 email domains, SLA policies, and 100 contacts. Business ($79/mo) gives you 20 team members, 25 email domains, and 500 contacts. See pricing for details.
How is GoPimi different from Zendesk or Freshdesk?
GoPimi is API-first. While traditional helpdesks are UI-first with APIs bolted on, GoPimi treats the API as the product. Every feature is designed to be automated and integrated, with a lightweight dashboard for operations.
Can I use my own email domain?
Yes. GoPimi supports custom email domains with full DNS verification. You can also use email forwarding if you don't want to change your MX records — just forward your existing email to a GoPimi address. Inbound emails automatically create and update tickets with proper threading.
What's the difference between tickets, shared inbox, and personal inbox?
GoPimi has three workflows. Tickets are for structured support — they have status, priority, agent assignment, and SLA tracking. The shared inbox handles team conversations visible to all workspace members, ideal for general inquiries on a shared address like info@. The personal inbox is private to an individual user — conversations route there when an email address is assigned to a specific user, auto-assign to that person, and only they receive notifications. Each workspace email is purpose-routed automatically — one platform for all three workflows.
Can I manage multiple brands or products?
Absolutely. GoPimi's multi-workspace model lets you run isolated support operations for each brand, product, or client from a single account.

View all FAQs →

Ready to automate your support?

Join the waitlist and help shape the future of API-first ticket management.

Start Free Trial