Fieldwire API is the core of the Fieldwire platform. The API powers our highly rated web and mobile apps. The API is very mature and 100% production ready. In addition, many of Fieldwire's largest customers utilize the API to perform a variety of actions including: data import and export, archiving, analytics, and automation.
Yes, the API supports and allows any action that can be done through our apps.
Fieldwire continuously releases updates to the API but all updates are designed to be backwards compatible with all existing clients integrating with the API. API calls can be pinned to a particular version as explained here
Fieldwire releases with a zero downtime deployment strategy.
Yes. These docs are built using out OpenAPI V3 spec published here: https://console.fieldwire.net/oas/v3.json
See guide here.
Each API token has a limit of 10 API calls per second.
Applications that hit the rate limits will receive a 429 error until it is acceptable to make requests again.
Applications can utilize the following headers to handle this situation:
|Indicates that the limit was hit
|Indicates the UTC time when the limit is reset
Generally, there is no limit on storage for uploads. Usage is monitored and abuse will result in revocation of API access.
This is a small discrepancy between the Fieldwire UI and the API. What appears as "categories" in the UI, is called "teams" in the API. The payload for the /tasks endpoint will return a team_id. In order to get the name-id maaping you'll need to use the /teams endpoint
Updated 5 months ago