Available SDKs
See where OmniLab stands on SDKs and how to integrate safely without an official one.
OmniLab does not publish an official customer SDK today.
What to do instead
- Call the approved endpoints over HTTPS from your own backend.
- Keep your own thin client for token retrieval, retries, and response parsing.
- Isolate OmniLab-specific logic behind an interface so you can swap to an official SDK later.
- Use the embedding guides for browser, kiosk, and WebView delivery.
What your thin client should cover
| Concern | What your wrapper should do |
|---|---|
| Authentication | Request and cache the bearer token securely |
| Retries | Back off safely on 429 and transient failures |
| Pagination | Handle page_size and page_number for list-style calls |
| Webhook verification | Verify signatures before processing events |
| Booking flows | Wrap the fetch and cancellation calls that your product needs |
Keep your wrapper intentionally small
Build only the adapter you need around the documented OmniLab surface. A thin wrapper is easier to maintain while the public API reference is still expanding.