Nurish’d API terms
Version 2026-01 · Effective November 20, 2026
How these terms work
These terms govern your company’s access to the Nurish’d Connect API. The owner of your company’s developer account accepts them once, on behalf of the company.
The API reference is public. Keys are not. Anyone can read the Nurish’d Connect documentation without accepting or signing anything. These terms govern the use of keys, and Nurish’d issues a key only to a company that has a signed agreement with Nurish’d in place.
Who is bound. Acceptance binds your company, its employees and its contractors, and anyone who calls the API with a key issued to your company. Your company is responsible for every call made with its keys.
What acceptance gives you. Acceptance lets your company create Sandbox keys. It is one condition among several: Nurish’d issues no key, in either environment, until your company has a signed agreement in place. Acceptance does not give you Production access and does not permit use with real people’s data. Section 5 lists what Production needs.
If your company has a signed agreement with Nurish’d. Where your company and Nurish’d have signed a Master Services and Integration Agreement, or any other written agreement covering the Nurish’d Connect API, that agreement controls wherever it conflicts with these terms. These terms fill gaps the signed agreement does not address. Accepting these terms, or any later version of them, does not amend that agreement, whichever was signed or accepted first. Where a business associate agreement is in place, it controls on anything concerning protected health information.
Version. These terms are version 2026-01. Section 4 explains how they change.
1. Acceptable use
What you may build with Nurish’d Connect, and what is off limits.
What you may build. Call the API from systems your company controls, to let your own users:
check eligibility and coverage for Nurish’d nutrition services
find a dietitian, and book, reschedule or cancel appointments
browse and order meals and other products from the Nurish’d marketplace
see their own appointments, orders and account information
Keys are issued to one company, for that company’s own application.
Off limits. You may not:
Send real people’s data to Sandbox. Sandbox data is synthetic. Do not send real names, contact details, dates of birth, insurance identifiers or health information to a Sandbox endpoint.
Give anyone else access. Do not resell, sublicense, share or expose your keys or the API to a third party, including an affiliate, a client or an agency, without Nurish’d’s written permission.
Build a competing service. Do not use the API, its responses, or anything you learn from it to create, price, train or improve a product that competes with Nurish’d’s nutrition services, dietitian network or medically tailored meal offering.
Train models on the data. Do not use data received through the API to train, fine-tune, benchmark or evaluate any machine learning model, your own or a third party’s, and do not pass it to a general purpose AI service, without Nurish’d’s written permission. This does not stop you using the data to operate the features described above.
Interfere with the embedded surface. If you also use the Nurish’d Surface, our iframe or SDK, do not scrape it, intercept its traffic, instrument it, inject into it, or configure your application so that information inside it reaches your systems.
Reverse engineer or probe. Do not reverse engineer the API, test its security, or run load tests outside Sandbox, without written permission.
Step into clinical decisions. Nurish’d is the provider of record. Do not direct, influence or interfere with any clinical matter, do not hold yourself out as the provider of care, and do not condition any payment or benefit on a clinical outcome, a treatment decision or a level of utilization.
Build inducements. Do not offer a user anything of value to induce them to use a Nurish’d service that is or may be billed to a federal health care program. That includes points, rewards, credits, account balance, prize entries, waived fees and discounts tied to booking, attending or completing a visit. How your company and Nurish’d pay each other, and the referral law covenants that go with it, are in your signed agreement.
Misrepresent the relationship. Describe Nurish’d services accurately, keep the attribution your agreement requires, and do not suggest that Nurish’d endorses, sponsors or is responsible for your other products.
Break the law. Do not use the API in any way that violates applicable law, including state licensure and telehealth rules, HIPAA, state privacy law, and consumer protection and marketing law.
Clinical content. Information the API returns about a user’s care belongs to that user and their Nurish’d care team. Do not alter it, do not present it as your own clinical advice, and do not use it to generate clinical guidance inside your product.
2. Data handling
How your company stores, protects and deletes the data it receives.
Why this section is strict. Nurish’d offers two integration paths. On the embedded surface, Nurish’d serves clinical information straight to the user’s device and your systems never hold it. On this API, your systems do hold it. That is why a business associate agreement is required before Production.
Business associate status. For protected health information your company receives through the API, your company is a business associate. The signed business associate agreement sets your obligations in full. What follows is the minimum, and does not replace it.
What Nurish’d does with the data. Nurish’d uses what it receives to create and run the user’s account, to book appointments, to build meal plans, to recommend providers, and to personalize what the user sees, including through automated and AI-assisted recommendations. It also uses it for internal reporting and customer service. Any automated processing is in service of the user’s own care and the operation of the Nurish’d platform. For protected health information, Nurish’d is the provider of record and handles it for treatment, payment and health care operations under its own notice of privacy practices. Nurish’d does not sell it and does not use it for advertising.
Minimum necessary. Request only the fields your feature needs. Do not pull records in bulk, or fields you do not use, to build a general store.
Security. At a minimum:
TLS 1.2 or higher in transit, and encryption at rest
access limited to personnel with a business need, under named individual accounts
multi-factor authentication on any system that stores or reaches the data
access logging, retained for at least 12 months
strict separation of Sandbox and Production. Never load Production data into a test, demo or development environment.
No secondary use. Do not sell the data, use it for advertising or audience building, or disclose it to anyone except as your business associate agreement permits. Do not combine it with your own customer data for any purpose beyond the features described in Section 1, and do not de-identify or aggregate it without Nurish’d’s written permission.
Tracking technologies. Do not place third-party analytics, advertising, session replay or similar tracking technology on any screen, email or notification where data received through the API appears, without Nurish’d’s written permission.
Subcontractors. You may use a subcontractor or cloud provider that handles this data only if it is bound by terms at least as protective as these. You remain responsible for what it does.
Security incidents. Tell Nurish’d within two business days of discovering any unauthorized access, use, disclosure or loss of data received through the API, at privacy@nurishd.io. Give us the facts you have, keep us updated, and cooperate with investigation and notification. Coordinate with Nurish’d before notifying individuals or regulators about an incident involving Nurish’d data, unless law requires you to act sooner. Unsuccessful attempts that result in no unauthorized access, such as pings, port scans and blocked log-in attempts, do not need to be reported.
Individual requests. Nurish’d holds the designated record set. If a user asks you for access to, a copy of, an amendment to, or an accounting of their health information, route the request to Nurish’d within five business days rather than answering it yourself.
Deletion. When your access ends, or when Nurish’d asks, delete or return all data received through the API within 30 days and confirm in writing that you have done so. If law requires you to keep a copy, keep protecting it under these terms and delete it when that requirement ends.
Where data is processed. Process, store and access the data only from within the United States unless Nurish’d agrees otherwise in writing.
3. Rate limits
The calls per minute your company gets in Sandbox and Production. Limits apply per company, across every key in that environment, not per key. Standard limits are as follows:
Limit
Sandbox
Production
Sustained requests
60 per minute
300 per minute
Burst
120 in any 10 seconds
600 in any 10 seconds
Bulk and reporting endpoints
10 per minute
30 per minute
Concurrent requests
10
50
When you hit a limit. The API returns 429 Too Many Requests with a Retry-After header. Honor it. Back off exponentially with jitter, and never retry a 429 immediately or in a tight loop.
What to retry. Retry 429 and 5xx after a backoff. Do not retry any other 4xx; fix the request instead. Send an idempotency key on every call that creates something, so a retry does not double-book an appointment or duplicate an order.
Webhooks. Nurish’d posts an event to your endpoint the moment a connection, booking or order changes. The delivery policy:
Item
Policy
Response timeout
5 seconds for the whole request
Success
any 2xx. A redirect is not followed and counts as a failure.
Retry window
3 days from the first attempt
Retry spacing
30 seconds, then doubling, capped at 6 hours, about 20 attempts
Stops early
the endpoint is disabled or deleted, or its address is not allowed
Signature
Nurishd-Signature, HMAC-SHA256. The timestamp is valid for 5 minutes.
Secret rotation
the old and the new secret both work for 24 hours
Delivery
at least once, so dedupe on the event ID
Resend
none. After 3 days a delivery is marked failed for good.
Answer 2xx first and do your work afterwards. Verify the signature on every delivery, and reject anything whose timestamp falls outside the 5 minute window. Because there is no resend, an endpoint that is down for 3 days loses those events for good.
Asking for more. Write to hello@nurishd.io with the endpoint, the traffic pattern and the peak you expect. Higher limits are granted per company and recorded on your company record. Ask before launch rather than after.
If you go over repeatedly. Nurish’d may throttle your company, and for sustained abuse may suspend its keys. Where it is practicable we tell you first.
4. Changes with notice
We tell you before the terms change, and you accept the new version.
Versions. These terms carry a version, written as a year and a month. This is version 2026-01. Every earlier version stays available in the developer portal.
Material changes. Nurish’d gives 60 days’ notice before a material change takes effect. Notice goes by email to your account owner and appears in the developer portal. A material change is one that narrows what you may build, adds an obligation, or lowers your rate limits.
Everything else. Corrections, clarifications, new endpoints and new optional features take effect when they are posted.
How you accept. Your account owner accepts the new version in the developer portal. Continuing to call the API after the effective date is also acceptance.
If you do not accept. You may stop using the API and close your account before the effective date, at no cost. Your keys are deactivated, and Section 2 still governs data you already received. If you neither accept nor close the account, Nurish’d may suspend your keys after the effective date, except where your company has a signed agreement with Nurish’d. In that case the disagreement is handled under that agreement’s dispute resolution and termination provisions, and your keys are not suspended on that ground alone.
Urgent changes. A change needed to meet a legal requirement or to close a security risk may take effect immediately. We tell you as soon as we can.
Deprecation. Nurish’d gives at least 90 days’ notice before removing an endpoint, a field or a webhook event, except where security or law requires us to move faster. Deprecations appear in the developer portal changelog with their removal date.
Changes to the API itself. Within a published version, Nurish’d will not change the type or meaning of an existing field, or the meaning of an existing value, without at least 90 days’ notice, the same window as a deprecation. New endpoints, new fields and new values may be added at any time without notice, so build your client to ignore what it does not recognize rather than fail on it. A change required for security or by law may take effect sooner.
Your signed agreement is separate. A change to these terms does not change a signed agreement between your company and Nurish’d. That agreement is amended the way it says.
5. Keys, environments and access
Who may hold a key. Your company must have a signed agreement with Nurish’d before any key is created, in Sandbox or in Production. Your account owner then decides who in your company can create keys. Keys belong to your company, not to the person who created them.
Keep them secret. Treat a key like a password. Do not commit it to source control, put it in client-side code, a mobile app binary or a browser, or send it over email or chat. Keys are for server-to-server calls only.
Rotation. Rotate keys at least once a year, and immediately if a key may have been exposed or when someone with access leaves. Tell Nurish’d within 24 hours at privacy@nurishd.io and we will revoke it.
Environments. Sandbox keys work only against Sandbox, which returns synthetic data, uses simulated calendars and sends no email, SMS or push notification to anyone. Production keys work only against Production, where real people and real orders are.
Getting to Production. Nurish’d turns on Production when your integration is ready. That means:
these terms are accepted and current
an integration review has been completed with Nurish’d
a business associate agreement is signed, where the integration will receive protected health information
a Master Services and Integration Agreement, or another written agreement covering the API, is in force
your webhook endpoint is reachable and verified, and your retry and error handling has been demonstrated
Your responsibility. Your company is responsible for every call made with its keys, including calls made by someone who should not have had the key.
6. Suspension, term and termination
Term. These terms apply from the day your account owner accepts them until your company’s access ends.
Suspension. Nurish’d may suspend a key or your company’s access, with notice where that is practicable and immediately where it is not, if:
a key is exposed or is being misused
your use presents a security risk to Nurish’d, its users or its partners
you breach Section 1 or Section 2
your traffic exceeds the limits in a way that affects other partners
the law or a regulator requires it
We tell you what happened and what has to change before access is restored.
Termination by you. You may stop using the API and close your developer account at any time.
Termination by Nurish’d. Nurish’d may end your access on 30 days’ notice, or immediately for a material breach of Section 1 or Section 2 that is not fixed within 10 business days of notice, or immediately where the breach cannot be fixed.
What happens then. Keys are deactivated and you stop calling the API. Section 2 keeps applying to data you already received until you have deleted or returned it.
What survives. Sections 1, 2, 6 and 7 survive, together with your business associate agreement to the extent it says so.
Where you have a signed agreement. Its term, termination and transition provisions control, including any obligation to keep serving users through a wind-down period.
7. What these terms do not cover
These are the rules for using the API. The commercial relationship lives elsewhere.
Warranties, liability, indemnity, insurance and service levels are set in the agreement your company signs with Nurish’d, not here.
Every company with API access has a signed agreement. Nurish’d does not issue a key, in Sandbox or in Production, until one is in place. Warranties, liability, indemnity and service levels therefore always come from that agreement, in both environments.
Fees. Nothing in these terms obliges either company to pay the other. What your company and Nurish’d pay each other, and on what basis, is set in your signed agreement.
Protected health information. Your business associate agreement controls. Where it conflicts with Section 2, the business associate agreement wins.
Clinical care. Nurish’d is the provider of record for the nutrition services delivered through the API. Nurish’d holds the patient relationship, the medical record and the payer contracts, and bills under its own group National Provider Identifier. Nothing in these terms makes your company a provider of care.
Governing law. Your signed agreement controls. Every company with API access has one.
Who to write to. privacy@nurishd.io, a shared mailbox, for integration questions, for anything involving a key or an incident, and for these terms.