# Posiway Documentation

Use these resources to connect business applications, GPS hardware, and event-driven workflows to the Posiway location platform. They are written for software developers, solution architects, GPS service providers, and technical teams preparing a production integration.

## Choose an integration path

- Start with the [integration guides](/docs/guides/) to understand the available interfaces and choose between request-driven APIs and event-driven webhooks.
- Use the [interactive API reference](/docs/api/) to inspect authentication, endpoints, parameters, examples, and response models.
- Read the [webhook receiver guide](/docs/guides/webhook-api) before implementing signature verification, idempotency, acknowledgement, retry, and queue handling.
- Consult the [alarm event reference](/docs/guides/webhook-alarm-events) for supported hardware and business alarm types, payload fields, subscription scope, and fuel-impact estimates.

## Before production

Confirm which customer accounts and devices the integration may access. Store API credentials and webhook secrets outside browser code, request only the permissions you need, and agree on a rotation process. API clients should handle pagination, rate limits, timeouts, retries, and partial failures. Webhook receivers should preserve the raw request body for signature verification, deduplicate by event ID, return a successful response promptly, and process slower business work asynchronously.

The documentation describes the public integration contract. Your Posiway contact can help confirm tenant setup, device coverage, and rollout requirements that are specific to your deployment.

[Open the API reference](/docs/api/) · [Review integration guides](/docs/guides/) · [Contact integration support](mailto:support@posiway.com?subject=Posiway%20integration%20support)