Build field-service products, integrations, and migration workflows on top of Asteri.
This portal is where partner teams, internal platform builders, and migration specialists learn how to work with Asteri's keys, webhooks, future public APIs, and service-business operating model.
Know what is live, what is preview, and what is still coming.
This portal is intentionally honest about maturity. Use the live platform surfaces now, build against the private-preview contract where available, and treat the rest as roadmap.
Organization-scoped API keys, webhook endpoints, and delivery tracking are already in-product.
Stable public resources for customers, appointments, estimates, invoices, and payments.
Partner apps, OAuth clients, and sandbox tenants will launch behind a preview program first.
Keep up with API and SDK movement.
SDK and Generated Snippets
Choose the task, then jump straight into the right surface.
Generate a scoped key, send explicit org context, and validate the preview auth model end to end.
Start onboardingVerify signatures, inspect payloads, and model retries before you wire workers or queues.
Open webhooksUse the generated client, typed error handling, and example scripts instead of hand-writing fetch wrappers.
Use the SDKReview request bodies, response payloads, common errors, and copyable examples before integrating deeply.
Read the referenceMove through the portal in the order most teams need.
Start with onboarding
Create a scoped key, confirm org context, and make the first authenticated request.
Read nextReview the API program
Understand auth, scopes, rate limits, and the preview rollout before integrating deeply.
Read nextCheck the reference index
Inspect request and error contracts for customers, appointments, estimates, and invoices.
Read nextUse the SDK guide
Skip hand-written fetch code and adopt the generated TypeScript client plus error handling.
Read nextSee which resources are live, preview, or roadmap.
| Resource | API | Docs | SDK | Operations |
|---|---|---|---|---|
| API keys | Available now | Open docs | N/A | Security center |
| Webhook events | Available now | Open docs | Available now | Delivery history + replay flow |
| Customers | Private preview | Open docs | Available now | Read + create live |
| Appointments | Private preview | Open docs | Available now | Read + create live |
| Estimates | Private preview | Open docs | Available now | Read + create live |
| Invoices | Private preview | Open docs | Available now | Read live, write planned |
| Payments | Private preview | Open docs | Available now | Read live |
| Services | Private preview | Open docs | Available now | Read live |
| Files | Private preview | Open docs | Available now | Read live |
| Sandbox tenants | Planned v1 | Open docs | Planned v1 | Planned |
| Partner OAuth apps | Planned v1 | Open docs | Planned v1 | Planned |
Start with the real surfaces that already exist.
Developer Onboarding
Use the quickstart to create a workspace, generate scoped keys, configure signed webhooks, and choose the right integration lane.
Read the guideAPI Program
Review how Asteri will separate stable public resources from internal tRPC procedure shapes and roll out REST, OAuth, and SDKs in layers.
Read the docsWebhook Reference
Explore signed delivery, retries, event categories, payload shape, and the replay-oriented operating model built into Asteri.
View detailsDesign the public platform around durable contracts.
Least-privilege scopes, expiration controls, and rate-limit settings already exist in the security center.
HMAC signatures, retries, delivery history, reliability views, and secret rotation are already supported.
Teams can call external APIs from Asteri workflows without custom middleware.
Payments, accounting, communications, storage, databases, and social connectors are already part of the platform surface.
The first public contract should start with the revenue and operations backbone.
What makes this portal better
Asteri is not another generic CRM API. The portal is organized around revenue, dispatch, estimate, invoice, and compliance workflows.
Developers need request logs, webhook replay, secret rotation, and rate-limit insight in the same surface as the docs.
Teams leaving incumbents need compatibility guidance, workflow recipes, and onboarding paths that shorten the switch.
Reference cards with live program state.
Open API programCustomers
Private previewCustomer identity, contact points, tags, and activity history for field-service operations.
View referenceAppointments
Private previewScheduling, assignment, completion lifecycle, and downstream operational triggers.
View referenceEstimates
Private previewQuote creation, approval flows, acceptance events, and revenue transition states.
View referenceInvoices
Private previewBilling state, payment collection hooks, and accounting-system handoff.
View referencePayments
Private previewCollected payments, invoice linkage, payment methods, and collection-state visibility.
View referenceServices
Private previewService catalog visibility for pricing, duration, and booking-facing configuration.
View referenceFiles
Private previewUploaded file records, MIME metadata, processing status, and storage-bucket context.
View referenceWebhook Events
Available nowSigned event delivery with retries, delivery history, secret rotation, and replay-oriented operations.
View referenceAPI Keys
Available nowScoped keys, expirations, and rate limits already live inside the Asteri security center.
View referenceTypeScript SDK
Available nowGenerated fetch-based client package aligned with the public OpenAPI contract.
View referenceLaunch tracks
Connect Asteri to CRMs, data stores, and finance systems with signed events and outbound REST actions.
Build customer, estimate, invoice, and payment flows on top of Asteri instead of stitching together generic back office tools.
Give teams leaving Jobber and adjacent platforms a faster route into Asteri with recipes, import guides, and compatibility notes.
Stable external DTOs and versioned routes instead of exposing internal tRPC shapes.
Every developer should be able to test a realistic service company before touching production.
OAuth clients, scopes, review workflow, usage analytics, and changelog subscriptions in one place.
Questions teams ask before they build.
Can I use the developer portal before the public REST API ships?
Yes. The current program starts with scoped API keys, signed webhooks, outbound REST automations, and the integrations/security surfaces already in Asteri.
Will third-party partners get OAuth?
Yes, but after the public REST contract and app review workflow are stable. Server-to-server access comes first.
Is this only for external partners?
No. The portal is also for internal platform teams, operators building automations, and migration specialists moving teams off incumbent tools.