Skip to content

Marketplace

Marketplace application management, billing, and installation.

Installing an application on a location is a two-step handshake: the owner connects the app (grant_access → status pending), then the partner confirms with the installation callback (→ status active). See the Install & test your app before moderation guide.

Host note: partner callbacks (/marketplace/partner/*) are served from the https://app.alteg.io root, not under https://api.alteg.io/api/v1. Each such operation documents its own server.

Operations

Connect an Application to a Location

Request

Step 1 of the two-step installation handshake — the location owner grants the application access to their location.

Call this on behalf of the location owner (combined partner + user token). On success the application is linked to the location with status pending: the partner service must then confirm the installation with the installation callback to move the link to active.

For non-public (draft/whitelisted) applications the link is activated immediately (fast install) instead of going through pending.

The authenticated user must have the Manage user rights permission on the location. See the end-to-end Install & test your app before moderation guide.

Security
BearerPartnerUser
Path
company_idintegerrequired

Location ID

application_idintegerrequired

Application ID

Headers
Acceptstringrequired

e.g. application/vnd.api.v2+json

Example:application/vnd.api.v2+json
curl -i -X POST \
  'https://developer.alteg.io/_mock/en/developers/openapi/company/{company_id}/marketplace/applications/{application_id}/grant_access' \
  -H 'Accept: application/vnd.api.v2+json' \
  -H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>'

Responses

Access granted. The application–location link is created with status pending (or active for fast-install applications).

Response
No content