Bounded developer access

Scoped credentials and verified receipts

OrbiLattice currently exposes a narrow workspace-admin lifecycle for read-only API credentials and signed incoming-webhook verification. Review the exact boundary before building an integration.

Open developer settings Developer access terms Sign in

This is a bounded integration surface, not a promise of a complete public API, SDK, sandbox, arbitrary webhook destination, or guaranteed delivery service.

Issue once

A workspace administrator creates a credential with one of the currently allowlisted read scopes. The plaintext value is shown only in the issuance response.

Use the exact scope

The bounded developer endpoints expose a contact count or sanitized incoming-webhook receipt metadata. Other scopes are denied.

Verify local receipts

The incoming fixture path checks a timestamp and signature before claiming its workspace-scoped idempotency key.

Revoke durably

Revocation is irreversible through the management routes. Refresh shows the fingerprint and revoked state, never the prior secret.

Current request shapes

Sanitized receipt read-back

GET /api/developer/v1/webhook-receipts?provider=developer-fixture
Authorization: Bearer <one-time-issued-key>

{
  "data": [{
    "id": "<receipt-id>",
    "provider": "developer-fixture",
    "verified": true,
    "receiptState": "accepted",
    "eventTypes": ["webhook_received"],
    "receivedAt": "<timestamp>"
  }]
}

Signed local fixture

POST /api/incoming-webhooks/developer-fixture/<workspace-id>
X-Timestamp: <unix-seconds>
X-Signature: <fixture-signature>
X-Signature-Id: <configured-fixture-secret-id>
X-Idempotency-Key: <event-id>

// The same signed event id is accepted once.
// A replay is returned as deduplicated.
// Bad signatures and stale timestamps are rejected.

Explicit product boundary

No claim of complete public API or CRUD coverage
No official SDK, public sandbox, marketplace, or GraphQL promise
No outbound-delivery guarantee or production SLA
No credential, signing secret, raw signature, payload, or contact PII in read-back
No provider or CRM mutation in the deterministic local webhook fixture

Need a broader integration?

Confirm the required resource and operation with the product team before depending on an unproved route or delivery behavior.Contact developer support