API referenceTenvelo API
https://api.tenvelo.com The contract, as OpenAPI

Contract 2026-10-10. Every path below carries its own major version.

Staff · Reference

Support

How a merchant reaches whoever runs this deployment, shown in the back office under Help after each partner it has let in.

Operations
1
Base
https://api.tenvelo.com

  1. GET/v1/support-contact

    How to reach this deployment

    No. getSupportContactAuth members:read

    The phone, email and hours a merchant uses to reach the support that runs this deployment, shown in the back office under Help after each partner it has let in. Empty where the deployment has not said; a partner's own contact is shown before this.

    Responses

    • 200

      The deployment's support contact.

      SupportContact · application/json
      • emailstring

        Required

        The address a merchant writes to. Empty where the deployment has not said.

      • hoursstring

        Required

        When the deployment answers, in its own words. Empty where the deployment has not said.

      • phonestring

        Required

        The phone a merchant rings. Empty where the deployment has not said.

    • 400

      The request could not be parsed. Malformed JSON, a bad query parameter, or a header that failed to decode, among them an API-Version later than the server speaks or not a date (api-version-unknown, with the server's own in api_version).

      Distinct from 422: a 400 never reached validation, so invalid_params is absent. Retrying without changing the request will fail again, except that a request refused for its API-Version goes once the server is updated.

    • 401

      No credentials, or credentials that could not be verified — missing bearer token, malformed JWT, expired token, or a signature that failed against the issuer's JWKS.

      Refresh the token and retry once. Repeated 401 after a refresh means the device needs to re-enrol.

    • 403

      Authenticated, but not permitted. The token is valid and its merchant was resolved, but the caller's role does not allow this operation, or the target belongs to a different merchant.

      Cross-tenant access is reported as 403 on a resource the caller may not see, and as 404 where even confirming existence would leak information. Retrying will not help.

    • 410

      The request names an API-Version this server no longer serves (docs/decisions/0011). Nothing in it was read. api_version names the version the server speaks: the client is behind, and sends the request again once it is updated.

    • 500

      Something failed on our side. trace_id identifies the request in our tracing — quote it in a support ticket.

      The body never carries internal detail: no SQL, no stack traces, no upstream error strings. Safe to retry with the same Idempotency-Key.