Define the boundary
Choose the routine questions the assistant may handle and the conversations that always return to a person.
Integration Planned
A creator DM API should make safe actions easy and unsafe actions impossible by default
Loresta's public creator DM API is planned. This page defines the product boundary and the contracts required before external developers receive access.
Keep provider complexity behind one authorized boundary
Instagram and X have different permissions, delivery rules, rate limits, and review processes. A creator DM API can normalize the application workflow without pretending those platform differences disappear.
Loresta will expose only capabilities supported by the connected provider and approved for the workspace. Unsupported actions should fail clearly rather than falling back to scraping or browser simulation.
- Provider capability checks
- Official authorization
- Clear unsupported errors
- No scraping fallback
Model the creator context explicitly
A useful API needs a creator profile, approved facts, destinations, voice summary, policy, conversation, and media eligibility. Passing a single prompt string makes access control and review too difficult.
Structured resources also prevent one workspace or creator from leaking context into another. Every request must enforce the tenant and profile association.
- Creator profile resource
- Policy resource
- Conversation resource
- Media resource
Webhooks need the same rigor as reply endpoints
Webhook signatures, retries, deduplication, ordering, and failure visibility determine whether an integration behaves reliably. A 200 response must never hide an event that failed before processing.
The public launch will require documented signatures, event IDs, retry behavior, versioning, and test fixtures. Until then, external developers should join the rollout instead of reverse engineering application routes.
- Signed webhooks
- Event deduplication
- Retry behavior
- Versioned contracts
A controlled rollout
Use the smallest safe workflow first, then widen it only after real conversation review.
Add the creator context
Approve the voice, facts, destination, and optional media that can support a useful reply.
Connect carefully
Authorize the supported inbox with official access and begin in draft-first mode.
Review and improve
Inspect replies, handoffs, usage, and repeated intent before widening any automation rule.
Launch checklist
Every connection and automatic reply should remain authorized, observable, and reversible.
- Official account authorization
- Inbound-only messaging
- Creator-approved facts
- Editable voice profile
- Conversation context
- Low-confidence handoff
- Personal and business inquiry handoff
- Visible usage and pause controls
Frequently asked questions
Direct answers about capability, rollout status, and creator control.
Is the Loresta creator DM API public?
No. It is planned and will not be considered public until authentication, documentation, rate limits, webhooks, and tenant-isolation tests are complete.
Which platforms will the API support?
The design targets Loresta's supported X workflow and future approved Instagram capabilities, with every action gated by the actual provider connection.
Will there be webhooks?
Signed webhooks for events such as draft readiness and owner handoff are part of the planned design, subject to final implementation.
Can developers use dashboard APIs?
No. Dashboard routes are private application interfaces and are not a stable, documented, or supported developer API.
Prepare the workflow while the integration is planned
Loresta keeps voice, facts, media, policies, and human handoffs visible before automation expands.