Skip to main content

Connect AssetPilot Connect to AssetPilot

Connect reads and writes assets through AssetPilot's REST API with OAuth 2.0 (3LO). A Jira admin follows three steps once, on the Connection tab.

Pre-release

AssetPilot Connect is not on Atlassian Marketplace yet. It requires AssetPilot's app REST API, which is not in production. This page describes the release candidate.

Three steps, done once by a Jira admin.
The Connection tab after setup. Identifiers are replaced with placeholders.

Step 1: Turn on App REST APIs for AssetPilot​

  1. Select Open Atlassian Administration.
  2. Go to Apps → Sites → your site → Connected apps and open AssetPilot.
  3. In its settings, turn on App REST APIs. Without it, AssetPilot rejects calls from other apps.
  4. Copy the Required base URL. It looks like https://your-site.atlassian.net/gateway/api/svc/jira/apps/<app-id>_<env-id>.

Step 2: Create an OAuth 2.0 integration​

  1. Select Open developer console and choose Create → OAuth 2.0 integration. Name it, for example, AssetPilot Connect.

  2. Under Permissions → Add Marketplace or custom app → your site → AssetPilot for Jira, tick these scopes:

    ScopeLets Connect
    read:asset:customRead assets
    write:asset:customCreate, update, delete, change status, check out and check in
    read:catalog:customRead types, locations, people, the workflow and health
    read:event:customRead the event feed and attention items
    write:sync:customSend synced devices

  3. Under Permissions → Jira API → Add, then Configure → Granular scopes → Edit Scopes, tick read:forge-app:jira and write:forge-app:jira.

  4. Under Authorization, set the callback URL shown on the Connection tab. Use the copy button next to it.

  5. Open Settings in the console and copy the client ID and secret.

offline_access

offline_access is not ticked in the console. Connect asks for it when you authorize, so the connection keeps working without signing in again.

Step 3: Enter the details and authorize​

  1. Paste the AssetPilot REST API base URL from step 1, the Client ID and the Secret.
  2. Select Save. The secret goes to Forge secret storage and is never shown again; the field then reads Configured •••• 1234.
  3. Select Authorize. A new tab opens on Atlassian's consent screen. Accept it.

When it succeeds, the step shows Done, the header lozenge reads Connected and the button becomes Authorize again.

Connection status​

StatusMeaning
Not set upNo details saved yet. Authorize is disabled until you save.
Awaiting authorizationDetails saved. Select Authorize.
ConnectedConnect can call AssetPilot. The card shows the site, cloud ID, who authorized it and the last health check.
Connection errorThe last health check failed. The health line shows the error code and message. Syncs and deliveries pause until AssetPilot answers.

Select Test connection at any time. A healthy connection reports AssetPilot's version and the role Connect acts with.

Disconnect​

Disconnect is in the ⋯ menu next to Test connection.

Select ⋯ → Disconnect and confirm. MDM syncs and event deliveries stop until you authorize again. Your MDM sources, webhooks, channels and API keys are kept.