> For the complete documentation index, see [llms.txt](https://docs.nerovasystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerovasystems.com/guides/zero-to-live/zero-to-live.md). # Overview This walkthrough takes a platform on Nerova's API-first SaaS from a first API call to a live merchant. You use one Live API key for the whole journey. It runs on a free testing allowance until a commercial agreement is signed or a card is saved. The first release covers only Platform accounts serving human medical/clinic, salon/barber, and beauty businesses including nails. Veterinary and other verticals, vaccination-specific automation, and the deprecated customer WhatsApp payment flow are excluded. Existing source and payload examples may still expose retired values; they are not first-release recommendations. See [First-release scope](https://docs.nerovasystems.com/documentation/console/platform-access#first-release-scope). **Access policy:** Nerova approves the platform, which then receives a Live key and a free testing allowance of 5,000,000 tokens (never invoiced) before any commercial agreement. If the allowance runs out first, the key and the AI pause until the agreement is signed or a card is saved. See [Platform access](https://docs.nerovasystems.com/documentation/console/platform-access#from-approval-to-your-first-invoice). If you prefer task-oriented material instead of a single sequential path, use the [task guides](/guides/readme.md). This walkthrough is the long-form path; the reference material stays authoritative for individual endpoints. ## How the integration works Your platform team owns the API integration and the mapping to its system of record. Your backend calls Nerova's API under `/api/v1` to manage tenants, run activation, and observe the receptionist. Use SDKs and webhooks where documented. API contracts specify request and response behavior; they are not Nerova's product category or an offer of bespoke integration work. Provider API v1 pages describe the interface your platform implements separately. ```mermaid flowchart LR A[Your backend] -->|"Nerova API"| N[Nerova SaaS] A --> P[Your platform's system of record] ``` There is a single API host and a single kind of key. Every key is prefixed `nrv_live_` and operates Production. Nothing else is issued: any attempt to create a non-Live key returns `403 api_key.sandbox_disabled`. ## The journey | Step | What you accomplish | | ------------------------------------------------------------------------------------- | -------------------------------------------------------------- | | [1. Get credentials](/guides/zero-to-live/step-1-credentials.md) | Organization and your Live API key | | [2. First calls](/guides/zero-to-live/step-2-first-calls.md) | Verify the key, learn the request conventions | | [3. Implement Provider API v1](/guides/zero-to-live/step-3-implement-provider-api.md) | Understand the existing technical implementation specification | | [4. Provision a tenant](/guides/zero-to-live/step-4-provision-tenant.md) | Create the tenant that represents one merchant | | [5. Connect your platform](/guides/zero-to-live/step-5-connect-platform.md) | Configure the documented connection | | [6. Verify capabilities](/guides/zero-to-live/step-6-verify-capabilities.md) | Confirm what the connection verifiably supports | | [7. Run activation](/guides/zero-to-live/step-7-activation.md) | Walk the manifest-driven activation loop to Active | | [8. Bind a channel](/guides/zero-to-live/step-8-channels.md) | Connect the WhatsApp channel through a connection session | | [9. Webhooks today](/guides/zero-to-live/step-9-webhooks.md) | What eventing exists now and how to poll instead | | [10. Go live](/guides/zero-to-live/step-11-go-live.md) | Prove a booking end to end, then certification and entitlement | ```mermaid flowchart TD subgraph Launch S9[9. Webhooks today] --> S11[10. Go live] end subgraph Merchant["One merchant, zero to Active"] S4[4. Provision a tenant] --> S5[5. Connect your platform] --> S6[6. Verify capabilities] --> S7[7. Run activation] --> S8[8. Bind a channel] end subgraph Setup S1[1. Get credentials] --> S2[2. First calls] --> S3[3. Implement Provider API v1] end S3 --> S4 S8 --> S9 ``` ## What you need before step 1 * An email address you can receive verification codes on. * A development machine with `curl` or an HTTP client. * Your platform's system of record reachable from your own code (step 3). * Access instructions for your organization from Nerova. The free testing allowance funds every step through the end-to-end booking proof. Nothing in the journey needs a commercial agreement first. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nerovasystems.com/guides/zero-to-live/zero-to-live.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.