Log inTalk to us

Register an app for a team

post/v1/teams/{team_id}/apps
Requires an API key

The team's owners, admins and developers, and Ivora administrators. An app is private: only the team's own projects can install it. It declares its UI origins and extensions (where the dashboard shows it), the scopes it requests, and a webhook URL. Each UI origin must be https://<app>.<apps domain>, one label of 1-63 characters with no port (ivoraapps.com in production; 422 app_origin_outside_apps_domain), and never on Ivora's own domains (422 app_origin_refused). Apps may request stations:control, billing:write and tariffs:write, which installers must consent to; never billing:refund or stations:admin (422 app_scope_forbidden). The client_secret is returned once. A team registers at most 50 apps. Only Ivora administrators register an app as visibility first_party (403 otherwise): Ivora's own app, which every project can install and the dashboard shows as made by Ivora (publisher Ivora).

Path parameters

  • team_idstringRequired
    Pattern ^team_[0-9a-f]{32}$

Request body

  • namestringRequired
    2–80 characters
  • descriptionstring | null
    Up to 500 characters
  • icon_urlstring | null
    An https image URL.
    Up to 512 characters
  • ui_originsarray of stringRequired
    https origins (scheme and host, no port or path) the dashboard may frame for the app. Each must be one label of 1-63 characters under the environment's apps domain (https://<app>.ivoraapps.com in production); other hosts are refused (422 app_origin_outside_apps_domain).
  • extensionsarray of Extension
    Child attributes
    • pointenumRequired
      Where the dashboard shows the app: a project tab, a panel on a station or a session, an overview widget, or an action (a button on a station or session that opens the app).
      One of project.tab, station.panel, session.panel, overview.widget, action
    • pathstringRequired
      The page on the app's UI origin, starting with /.
      1–200 characters
    • titlestring | null
      The tab, panel or action label; required except for widgets.
      1–60 characters
    • targetenum | null
      For an action: the page it appears on.
      One of station, session
    • sizeenum | null
      For a widget: its size on the overview grid.
      One of 1x1, 2x1, 2x2
  • scopesarray of stringRequired
    Project scopes. Never billing:refund or stations:admin, and never staff or API-key routes.
  • webhook_urlstring | null
    The https endpoint the app's lifecycle events go to.
    Up to 512 characters
  • visibilityenum
    private: only the owning team's projects can install it. first_party: Ivora's own app, installable by every project and shown as made by Ivora; only Ivora administrators set it (403 otherwise).
    One of private, first_party · Default "private"

Returns · 201

  • idstringRequired
  • team_idstringRequired
  • namestringRequired
  • descriptionstring | nullRequired
  • icon_urlstring | nullRequired
  • ui_originsarray of stringRequired
  • extensionsarray of objectRequired
  • scopesarray of stringRequired
    The scopes the app requests; an install holds the part its installer consented to.
  • webhook_urlstring | nullRequired
    Null for a first_party app read from another team's project.
  • revisionintegerRequired
    Counts the changes to the app's scopes, origins and extensions. A consent is valid only for the revision it was given on.
  • visibilityenumRequired
    private: only the owning team's projects can install it. first_party: Ivora's own app, installable by every project and shown as made by Ivora; only Ivora administrators set it (403 otherwise).
    One of private, first_party
  • publisherstring | null
    Ivora for a first_party app, which the dashboard shows as made by Ivora; null: the team that registered it.
  • statusenumRequired
    One of active, archived
  • checkout_servicebooleanRequired
    Whether Ivora trusts the app's backend to name the driver's IP address (X-Ivora-Driver-Address) on payment creation, so the 30-a-minute per-address limit counts per driver: honoured only on a client_credentials token of an install holding billing:write, never on a session or exchanged token. Only Ivora administrators set it (403 otherwise), on an app that requests billing:write.
  • secret_prefixstring | nullRequired
    The client secret's first characters, to recognise it; the secret is shown only when it is created or rotated. Null for a first_party app read from another team's project.
  • secret_rotated_atstring | nullRequired
  • created_bystring | nullRequired
    Null for a first_party app read from another team's project.
  • created_atstringRequired
  • updated_atstringRequired
  • installsinteger | null
    Active installs, in the team's projects.
  • client_secretstringRequired
    Shown once. Keep it on the app's backend; Ivora stores only its hash.
  • webhook_secretstring | null
    Shown once, when the app is registered: the key that signs the app's lifecycle events (Ivora-Signature). Null when the client secret is rotated.
POST /v1/teams/{team_id}/apps
curl --fail-with-body -X POST "https://api.ivoracharge.com/v1/teams/team_0123456789abcdef0123456789abcdef/apps" \
  -H "Authorization: Bearer $IVORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "bay-01",
  "ui_origins": [
    "string"
  ],
  "scopes": [
    "string"
  ]
}'
Response · 201JSON
{
  "id": "id_0123456789abcdef",
  "team_id": "team_0123456789abcdef",
  "name": "bay-01",
  "description": "string",
  "icon_url": "https://app.example.com/return",
  "ui_origins": [
    "string"
  ],
  "extensions": [
    {}
  ],
  "scopes": [
    "string"
  ],
  "webhook_url": "https://app.example.com/return",
  "revision": 1,
  "visibility": "private",
  "publisher": "Ivora",
  "status": "active",
  "checkout_service": false,
  "secret_prefix": "string",
  "secret_rotated_at": "2026-09-30T17:00:00Z",
  "created_by": "string",
  "created_at": "2026-09-30T17:00:00Z",
  "updated_at": "2026-09-30T17:00:00Z",
  "installs": 1,
  "client_secret": "string",
  "webhook_secret": "string"
}
Requires an approved production API keyProduction access starts with a request, a short meeting with Ivora and a card on file, after which Ivora staff grant your account access. How to request access
Try itproduction · api.ivoracharge.com

Paste a production api key (iv_live_…). Create keys in Developer tools. The key stays in this page's memory, is sent only to https://api.ivoracharge.com and clears when you reload. Test keys are refused.

POST is a write: you confirm the method, path and project before it is sent, with a generated Idempotency-Key.