Developers
How Nexynth Labs thinks about public APIs, partner integrations, and GetPandit connectivity — honest readiness only. No live developer portal or API keys on this corporate site.
This page describes future direction, not shipped endpoints. The marketing site does not host API sandboxes, publish OpenAPI files, or display credentials. Integration work is scoped per engagement until a formal developer program launches.
Direction
A partner-friendly API layer across Nexynth Labs products and services — designed for temples, vendors, enterprises, and technology allies in India.
Nexynth Labs is building toward a consistent developer experience: versioned REST APIs, signed webhooks, clear sandbox boundaries, and separation between the corporate marketing site and product domains such as getpandit.com. Today this is a vision document — not a live gateway.
Roadmap
Illustrative API families under consideration. Names and scopes may change; nothing below is callable from this site.
Read-only partner and temple metadata for approved integrators — eligibility flags, regions, and integration readiness labels.
Optional webhook callbacks for enterprise customers who submit RFPs or consultations — status transitions only, not full CRM.
Structured export of self-assessment tiers for teams that complete the AI Readiness Score — indicative only, not certification.
Programmatic RSVP for webinars and meetups once ticketing moves beyond enquiry-only registration.
GetPandit
Partner and vendor connectivity for GetPandit on getpandit.com — separate from the corporate site. Capabilities follow product roadmap; confirm live status on the product domain.
Expose pandit calendars, service catalogues, and slot holds for temple and vendor partners with conflict detection.
Payment gateway webhooks and settlement exports — architecture-ready; production cutover confirmed per product release notes only.
Transactional templates for booking confirmations and reminders — provider-specific (Twilio, Gupshup, Meta Cloud API).
Document upload, eligibility review, and integration checklist for partners joining the marketplace model.
Events
Event types we intend to support for integrators. Payload schemas and signing secrets ship with documentation — not before.
Fired when a GetPandit booking is confirmed on the product domain — includes booking ID, service type, and partner reference.
Cancellation and reschedule events with reason codes for partner dashboards.
Payment success signal for reconciliation — amount, currency, and gateway reference only; no PAN or full card numbers.
Corporate partner onboarding milestone — triggers when staff approves a technology or temple partner application.
Docs
Developer portal deliverables on the roadmap. Until then, use enquiry and consultation for integration questions.
Versioned OpenAPI 3.1 bundles per API family — published when endpoints reach beta with breaking-change policy.
Client credentials, rotating secrets, IP allowlists, and scoped tokens for server-to-server integrations.
Step-by-step signature verification, clock skew tolerance, and sample handlers in TypeScript and Python.
Isolated sandbox with synthetic data, rate limits, and no production PII — launched after auth and webhook baselines.
Interested in early access or co-design? Contact us with your use case — we respond manually; there is no self-serve API signup.
Share your architecture, auth model, and timeline. We will confirm what is live on product domains versus roadmap.
