Kalo te përmbajtja kryesore

Developers / Auth

Authentication

The Glanevo API supports two methods: Bearer token (recommended) and OAuth2 (for 3rd party apps).

1. Bearer token (recommended)

Each tenant generates a token from its own Glanevo panel. Token format: glv_+ 64 hex characters. Stored as a SHA-256 hash — the plain value is visible only at the moment it's generated.

  1. Go to Panel → Settings → API Keys.
  2. "Generate new key" → choose a name and scopes.
  3. Copy the plain token once — save it somewhere secure.
  4. Use Authorization: Bearer glv_... in your requests.

2. OAuth2 (3rd party apps)

OAuth2 authorization code flow for 3rd party apps listed on the Marketplace. Contact: developers@glanevo.com

GET https://api.glanevo.com/oauth/authorize
  ?client_id=...
  &redirect_uri=...
  &scope=customers.read appointments.read
  &response_type=code
  &state=<csrf>

Scopes

ScopeDescription
customers.readRead customer list
customers.writeCreate/update customers
appointments.readRead appointment list
appointments.writeCreate/update appointments
services.readRead service catalog
payments.readRead payment list
reviews.readRead customer reviews
webhooks.writeManage webhook subscriptions

Rate limiting

Every response includes three headers:

  • X-RateLimit-Limit — the quota within the window
  • X-RateLimit-Remaining — remaining request allowance
  • X-RateLimit-Reset — the UNIX timestamp when the window resets
PlanHourly limit
Free100 / hour
Pro10,000 / hour
EnterpriseUnlimited (fair use)

Error codes

  • 401 Unauthorized — Token missing / invalid / revoked
  • 403 Forbidden — Token not authorized for this scope
  • 404 Not Found — Resource doesn't exist in this tenant
  • 422 Unprocessable — Validation error
  • 429 Too Many Requests — Rate limit exceeded
  • 5xx — Server error, retry recommended