API terms of use
Last updated 22 November 2026.
These terms govern access to Stello SB’s organization API. They supplement the organization’s agreement with Stello. A signed agreement that expressly addresses the same subject takes precedence. Applicable mandatory law takes precedence over conflicting restrictions.
Agreement through use
By accessing or using the API, you accept these terms on behalf of the organization that owns the credentials. You must have authority to act for that organization. The organization is responsible for its integrations and the developers and service providers it authorizes. An integration provider must use access only for the organization that authorized it.
Permitted integrations
Stello grants a limited, non-exclusive, revocable permission to use the documented API for the authorized organization’s activities. Permitted uses include displaying its events, synchronizing its own records, producing internal reports, connecting its approved tools and checking whether a ticket or membership entitles a person to a service the organization itself provides, such as booking a room.
Access is limited to enabled resources, key permissions and selected events. A parent organization may access eligible sub-organizations only through the documented permission and staff enablement. Use the documented endpoints and respect pagination, rate limits, expiry and revocation.
Misuse and replication
You must not use the API, Stello-owned material or confidential information obtained through access to build, operate, sell or assist a clone, white-label version or competing replacement for Stello’s platform without Stello’s prior written agreement. This includes copying protected service designs or compiling a platform-wide database through access granted for individual organizations.
You must not bypass access restrictions, combine credentials to evade limits, access another organization’s records without authorization, discover private endpoints through probing, impersonate Stello, interfere with service availability, distribute malware or use access for unlawful activity. Reselling API access or providing an unrestricted proxy to third parties requires written permission.
You must not reverse engineer protected software or circumvent technical protections except where applicable law grants a right that cannot be excluded by contract, including qualifying interoperability rights.
Organizations may display, retain, export and move their own content and records where they have the relevant rights. Publishing an organization’s own event website and obtaining a lawful export are permitted uses. Stello’s platform, branding, software and confidential service information require their own permission.
Endpoints, permissions and later additions
These terms apply to every endpoint, permission and field that Stello documents for the API, including any added later. Additions are announced in the API changelog. A new endpoint or permission does not need new terms unless it changes these terms, in which case the section on changes applies.
Some endpoints return or confirm personal data, for example whether a ticket is valid. They are available only when an organization admin switches on the specific key permission for them. By doing so, the organization confirms that it has a lawful purpose and legal basis, that it is responsible for the data it receives or checks, and that it will use the result only for the purpose it has stated. A ticket’s code or ID identifies a ticket. It does not prove who is presenting it, so the organization must confirm the person in its own system.
You must not use the API to discover who holds tickets or memberships, for example by guessing or enumerating ticket codes or IDs, or to assemble attendee lists the API does not provide.
Data and credentials
Use secret keys only in an appropriately secured server environment. Keep keys out of browser code, public repositories, URLs, chat prompts and public logs. Limit access to authorized personnel and contracted providers. Revoke credentials promptly when they are compromised or an integration ends.
Publish only records eligible for public display. Apply an appropriate legal basis, access controls and retention period to personal data. Make the necessary arrangements with providers that process it for you. Do not sell personal data or use it for unrelated advertising, profiling or model training without the required rights and legal basis.
The organization retains its rights in its own content. API access grants rights only for the permitted integration. Respect other people’s copyright, image rights and confidentiality.
Accuracy and operation
Keep displayed event information reasonably current, respect cancellations and access changes, and identify indicative prices and availability accurately. Checkout determines the final price and availability. Implement retries and caching within the documented limits. To protect the service, Stello may keep the result of a successful read for a short time at the network edge (currently up to 30 seconds), so a change in access, such as a revoked key, can take up to that long to apply to a read that was already kept. Checks of whether a ticket is valid are not kept.
Stello may monitor use for operation, security and compliance. Report suspected misuse or a security incident affecting the integration promptly to Stello.
Stello may limit or suspend access reasonably needed to address misuse, security incidents, legal requirements or material breaches. Where practicable, Stello will explain the reason and the corrective steps. Serious or urgent incidents may require immediate action.
Changes, termination and liability
The API may evolve under its documented versioning policy. Material changes to these terms will be communicated with reasonable advance notice where practicable, with a stated effective date. Using the API after that date constitutes acceptance of the updated terms to the extent permitted by applicable law.
When access ends, stop using the credentials and remove access held by your integration providers. Retain or export organization records only where you have an independent right or legal obligation to do so.
Availability, fees, warranties, liability and dispute handling follow the applicable organization agreement and mandatory law. These terms create no additional service-level commitment. Norwegian law applies, with the venue specified in the organization agreement where valid.
Contact and related terms
Stello SB, organization number 937 786 999, Larsgårdsvegen 2, 6009 Ålesund, Norway. Contact hei@stello.no.
Webhook delivery is governed by the webhook terms. An MCP connection is governed by the MCP terms, alongside these API terms when the connection uses API access.