Fieldwire
Hardline uses a Fieldwire API token as the long-lived credential. Fieldwire calls this token a refresh token, API key, or API token. Hardline exchanges it for a short-lived access token before making Fieldwire API calls.
Provider docs:
What you need
Section titled “What you need”- A Fieldwire account with API access enabled.
- Account Owner or Manager access in Fieldwire.
- Developer access approved for your Fieldwire account.
- A Fieldwire API token.
- The Fieldwire account ID and project ID you want Hardline to use.
Recommended auth model
Section titled “Recommended auth model”Use API token in Hardline.
Do not paste a generated Fieldwire JWT access token into Hardline. Fieldwire access tokens are short-lived. Paste the long-lived Fieldwire API token from the Fieldwire account settings page; Hardline will exchange it for short-lived access tokens as needed.
Enable API access in Fieldwire
Section titled “Enable API access in Fieldwire”- Confirm your Fieldwire plan includes API access. Fieldwire API access is typically available on Enterprise plans or accounts with API access added.
- Sign in to Fieldwire as an Account Owner or Manager.
- Open the account settings page.
- Find
API Settings. - If API access is not enabled, request API access from Fieldwire.
- If developer access is required, request developer access from Fieldwire and wait for approval.
- Confirm the account shows token management access.
Create the Fieldwire API token
Section titled “Create the Fieldwire API token”- In Fieldwire, open the account settings page.
- Go to
API Settings. - Open token management.
- Create a new token.
- Copy the token immediately. Fieldwire may not show the token again after creation.
- Store it securely until you paste it into Hardline.
Connect Fieldwire in Hardline
Section titled “Connect Fieldwire in Hardline”- Open Hardline.
- Go to
Settings > Integrations. - Select
Fieldwire. - Click
Add credentials. - Choose
API token. - Paste the Fieldwire API token.
- Enter the Fieldwire account ID in
Account ID. - Enter the account name in
Account name. - Add a default project name if most assistant work should use one project.
- Save the connection.
- Click
Test connection. - Enable the Fieldwire tool policies your team wants available.
API regions
Section titled “API regions”Fieldwire account-level authentication uses:
https://client-api.super.fieldwire.comProject data may use a regional API host. Fieldwire documents the US project API host as:
https://client-api.us.fieldwire.com/api/v3and the EU project API host as:
https://client-api.eu.fieldwire.com/api/v3Hardline defaults to the US project API host unless your environment is configured otherwise. Contact Hardline support before connecting EU-hosted Fieldwire projects.
Troubleshooting
Section titled “Troubleshooting”| Symptom | What to check |
|---|---|
| Token exchange fails | Confirm you pasted the Fieldwire API token, not a generated JWT access token. |
| API settings are not visible | Confirm API access is enabled and your Fieldwire user has Account Owner or Manager access. |
| Connection works but project reads fail | Confirm the project is in the expected Fieldwire API region and the token can access that project. |
| Writes fail | Confirm the Fieldwire user and token have permission to create or update tasks, forms, RFIs, or change records in the project. |