Skip to main content

SIGNAL4D / DEVELOPERS

Build with a view
of what’s ahead.

Bring weather, location and operational data into your application. Track assets, query conditions and act on the changes that matter.

Start building Explore the API

REST APIs / JSON / Vector tiles / Webhooks

YOUR FIRST REQUEST GET

Start with your collections.

Retrieve the groups used to organize your assets.

curl 'https://api.signal4d.com/locations/v2/collections' \
  --header 'x-api-key: YOUR_API_KEY'
EXAMPLE RESPONSE 200 OK
[
  {
    "collectionId": "field-operations",
    "collectionName": "Field operations"
  }
]

Use an API key supplied by your developer support contact. Authentication guide ↗

FROM DATA TO DECISIONS

Connect your assets. Add context. Define when to act.

Find your starting point

GET YOUR BEARINGS

A practical place to start.

All integration guides
01

Authenticate

Understand API keys, tokens and request headers.

02

Organize your assets

Group related records with collections.

03

Send telemetry

Connect assets and report their locations.

04

Add a map layer

Display vector tiles in your own map.

THE CONNECTION IS THE POINT

Put your data in context.

Weather is part of the picture. Bring in your own sensor and operational feeds to see what conditions mean for your assets.

Weather & forecasts Sensors & telemetry Assets & locations
YOUR LOGICRules & conditionsOne signal, or several together
YOUR APPLICATIONAlerts & webhooksAct when conditions match
AN EXAMPLE

Wind gusts above 30 knots AND a sudden drop in line tension notify the operations team.

Illustrative rule combining weather and sensor data.

THE BUILDING BLOCKS

Find the API
for the job.

Use the pieces you need, from a single weather query to monitoring a moving fleet.

Open API reference The API reference requires sign-in. Access depends on your account.
01

Weather & forecasts

Query forecasts and official weather alerts. Add the conditions around an asset, route or area to your application.

02

Rules & notifications

Define thresholds and geofence rules, then deliver alerts through notifications and webhooks.

03

Assets & telemetry

Store locations and metadata for vehicles and field assets. Use collections to query related objects together.

04

Routes & areas

Check where weather alerts and fire zones intersect routes. Use named areas and geofences for spatial monitoring.

05

Map-ready layers

Add weather, wildfire and infrastructure context to your map with vector tiles.

LET’S GET IT CONNECTED

Need a key or a hand?

Contact developer support for API access and help with your integration.

Talk to developer support devsupport@signal4d.com