Developer Access Terms
Effective Date: July 19, 20261. Scope and acceptance
These Developer Access Terms ("Developer Terms") govern use of the documented OrbiLattice developer-access features, including issued API credentials and documented incoming-webhook configuration. They supplement the Terms of Service and Privacy Policy. If these Developer Terms conflict with the Terms of Service about developer access, these Developer Terms control for that conflict.
By creating, using, or allowing use of a developer credential, you agree to these Developer Terms. If you act for an organization, you represent that you have authority to bind that organization.2. Current supported access
Developer access is limited to the operations and scopes expressly documented by OrbiLattice and enabled for your workspace. At the effective date, the documented read-only operations return either a workspace contact-count summary or sanitized incoming-webhook receipt metadata.
Developer access does not grant access to a general public API, full CRUD coverage, public GraphQL, an SDK, a public sandbox, a marketplace, arbitrary webhook delivery, or an availability or delivery service-level agreement. Undocumented endpoints and behavior are unsupported and may change without notice.3. Workspace authority and credentials
Only an authorized workspace administrator may create, rotate, revoke, or manage developer credentials. You are responsible for activity performed with credentials issued to your workspace and for assigning only the minimum scopes needed for the intended documented use.
Keep credentials confidential. Do not place them in browser or mobile client code, public repositories, screenshots, tickets, or other insecure locations. Promptly rotate or revoke a credential if you suspect loss, disclosure, misuse, or an unauthorized integration.4. Data handling and privacy
Use data received through developer access only for your organization's authorized use of the Services and only to the extent necessary for the documented integration. Maintain appropriate technical and organizational safeguards for that data and do not disclose it to third parties except as authorized by the applicable customer, these Developer Terms, and applicable law.
If your integration collects, receives, or otherwise processes personal data, you must provide and follow a clear privacy notice and comply with applicable privacy and data-protection laws. The Privacy Policy describes OrbiLattice's handling of personal data. Any applicable data-processing agreement remains governed by its own terms.5. Incoming webhooks and integration security
Where OrbiLattice documents an incoming-webhook configuration, you must follow the documented signature, timestamp, and idempotency requirements. Do not send secrets, raw credentials, or unnecessary personal data in a webhook payload.
You are responsible for securing systems you operate, validating requests you receive, and maintaining an incident-response process appropriate to your use. OrbiLattice may log and review developer-access activity to protect the Services, investigate abuse, and enforce these Developer Terms.6. Prohibited uses
You must not, and must not permit anyone acting for you to:
- Access an endpoint, scope, workspace, account, record, or data that your credential is not authorized to access.
- Bypass, disable, or interfere with authentication, workspace-scoping, rate-limit, security, signature, replay, or credential controls.
- Share, sell, sublicense, publish, embed in client-side code, or otherwise make developer credentials available to another person or service not authorized by your organization.
- Use developer access to scrape, create a substitute service, reverse engineer, probe, or test the security of the Services without our written permission.
- Introduce malware, interfere with the Services, or use developer access in a way that is unlawful or infringes another party’s rights.
- Treat developer access as permission to send messages, place calls, invoke communications providers, mutate CRM data, or use an undocumented operation.
7. Changes, limits, suspension, and termination
We may add, modify, limit, suspend, or discontinue developer access, credentials, scopes, documentation, or an operation when reasonably necessary for security, legal compliance, service integrity, or product changes. We may impose reasonable usage limits and may suspend or revoke credentials that violate these Developer Terms or create risk to the Services or others.
You may stop using developer access at any time by revoking your credentials. On termination or revocation, you must immediately stop using the affected access and delete credentials from systems under your control. Data-retention obligations under applicable law, the Terms of Service, or a customer agreement may continue.8. Ownership and feedback
OrbiLattice and its licensors retain all rights in the Services, developer access, documentation, and related technology. Except for the limited right to use documented developer access under these Developer Terms, no license or ownership right is granted to you.
If you provide feedback or suggestions about developer access, you grant us a non-exclusive, worldwide, royalty-free right to use that feedback without compensation or obligation to you.9. Disclaimers and liability
Developer access is provided as part of the Services and is subject to the warranty disclaimers, limitations of liability, indemnification, dispute-resolution terms, and other general provisions in the Terms of Service. To the maximum extent allowed by law, we do not promise uninterrupted availability, compatibility with every system, delivery of a webhook, or that developer access will meet a particular need.
These Developer Terms do not authorize use of developer access for high-risk activities where failure could reasonably lead to death, personal injury, or severe environmental damage.10. Contact
Questions about these Developer Terms or a requested integration may be sent to developers@orbilattice.com. Legal questions may be sent to legal@orbilattice.com.These Developer Access Terms are effective as of July 19, 2026.