Public Documentation

Lawie Docs

guideDifficulty: intermediateTime: 30mVersion: v1Services: api-keys, developer-sandbox, webhooksSDK: @lawie/sdkReviewed: 2026-06-11Reviewer: Docs PlatformTags: developer-platform, api-keys, sandbox, webhooks

Build on the Lawie Developer Platform

Configure credentials, validate integrations in the sandbox, and operate signed webhooks from the canonical developer surface.

Overview

Lawie developer workflows use three canonical platform capabilities:

  1. API keys for scoped machine authentication.
  2. The developer sandbox for non-production validation.
  3. Signed webhooks for outbound event delivery.

The former in-app developer portal and Zapier-specific subscription API are retired. OpenAPI reference, SDK guidance, and operational procedures now live in this documentation portal.

Prerequisites

  • Tenant administrator access
  • A secrets manager approved by your organization
  • An HTTPS webhook receiver
  • Access to the Lawie sandbox environment

Integration Flow

  1. Create a least-privilege API key from the API Keys workspace.
  2. Store the secret in your secrets manager and inject it at runtime.
  3. Validate requests and webhook handling in the developer sandbox.
  4. Register required event types through the canonical webhook subscription API.
  5. Verify signatures, timestamps, retries, and idempotency before production promotion.
  6. Rotate credentials and promote the tested configuration to production.

Canonical APIs

  • GET /api/v1/api-keys
  • POST /api/v1/api-keys
  • GET /api/v1/developer/sandbox/portal
  • POST /api/v1/developer/sandbox/webhooks/test
  • GET /api/v1/webhooks/subscriptions
  • POST /api/v1/webhooks/subscriptions

Use the API Reference as the source of truth for request and response schemas.

Operational Guides

Migration from Zapier-Specific Subscriptions

Register the destination URL with the canonical webhook subscription API and select the equivalent event types. Existing domain events continue through the signed webhook delivery pipeline with retry and delivery logging.

Legacy Zapier subscription records are retained for controlled data migration, but the Zapier-specific API is no longer active.

Troubleshooting

  • 401 or 403: verify API-key scope, tenant, expiration, and IP restrictions.
  • Signature failure: compare the raw request body and signing timestamp before parsing.
  • Missing delivery: confirm the subscription is active and includes the emitted event type.
  • Repeated delivery: deduplicate by event identifier and return a successful response after idempotent processing.