API Reference

Managani exposes a REST API at /api/v1/ for sites, customer engagement, product growth, automation, public surfaces, account settings, and team administration.

Base URL

https://app.managani.com/api/v1

Authentication

API endpoints require one of:

• Bearer Token — Authorization: Bearer <token>
• Access Token — Authorization: Token <access_token>

See Authentication for details.

Core Resources

Resource	Purpose
Sites	Product configuration, knowledge sources, public theme, widget settings, AI, and email templates
Feedback	Admin feedback lists, moderation, comments, reactions, and bulk actions
Roadmap	Roadmap lists and feedback card assignment
Changelog	Draft, improve, publish, and delete release notes
Surveys	Survey creation, targeting, responses, and reset flows
Tours and Highlights	In-app guidance, page rules, targeting, import, and export
Web Messages	Targeted in-app messages, actions, frequency rules, and metrics
Chat	Customer conversations, replies, assignment, status, notes, and transcripts
Tracking and Customers	Product events, analytics, signed customer profiles, and history
Social Monitoring	Monitor configuration, public signals, status, scoring, and actions
Content Strategy	Site analysis, keywords, opportunities, content generation, and publishing
AI Automation	Chat AI, lifecycle agents, rules, email identities, accounts, and conversations
Integrations	LinkedIn, Bluesky, Todoist, Ghost, and Streamient configuration
Widget	Public config, signed-user activity, customer tools, guidance, search, and tracking

Interactive Reference

The generated OpenAPI reference is available in the sidebar under OpenAPI Reference.

Prepare an Integration

Choose the resource and operation that match the action you need, then inspect its individual reference page. Review path parameters, request fields, security requirements, and documented responses before sending a request. Some routes represent public or browser-session workflows and should not be treated as ordinary token-authenticated resource calls.

Start with a read against a known test record and confirm the returned account or site context. Test write operations with data you can safely change before connecting them to production workflows. Use the endpoint's response definition to decide when an action is complete; an accepted background task may still need subsequent status checks.

When diagnosing an integration, keep a sanitized example of the request and response together with the selected operation. Record the method and resource identifier without including secrets. This makes it easier to distinguish an authentication problem, a schema mismatch, and an unexpected resource state when comparing behavior with the reference.