Delulu

Build on the same publishing system

Social media publishing API

Use Delulu's typed REST API to create, schedule, publish, inspect, and retry social posts while preserving workspace roles, review rules, and per-target status.

How it works

From setup to a finished workflow

  1. 1

    Choose authorization

    Use a workspace API key, OAuth with PKCE or device authorization, or a supported first-party session.

  2. 2

    Prepare the request

    Upload or import media, select connection IDs, and create a draft, schedule, or immediate-publish intent.

  3. 3

    Inspect every target

    Read the post and destination states until each target reaches a terminal result.

Capabilities

What you can do

  • OpenAPI 3.1 generated from the same typed server contract
  • Post draft, schedule, publish, edit, delete, target inspection, and retry operations
  • Presigned uploads and public-URL media import
  • Account connection and workspace administration operations
  • Review queues, decisions, comments, and activity
  • Analytics, automation, billing, and usage groups
  • Workspace-bound API keys and OAuth scopes

Best fit

Who it is for

  • Product teams adding social publishing to an internal tool
  • Agencies connecting an existing content pipeline
  • Developers who need explicit delivery state and retry behavior

Examples

  • Create a reviewed draft from a content-management system, then let an authorized publisher release it.
  • Import approved media from a public URL and schedule it to selected connection IDs.
  • Poll target state after publication and surface a provider-specific failure in an operations dashboard.

A successful request is not always a published post

Publishing is asynchronous and can produce a draft, scheduled post, pending review, processing job, partial destination result, or completed publication. API clients need to inspect the returned post and target states instead of treating an accepted request as delivery confirmation.

Authorization is evaluated against workspace membership, role ceilings, granted scopes, quota, and review rules. A custom client cannot use the API to bypass the controls visible in the Delulu workspace.

Requirements and limits

What to know before you start

  • Clients need an API key or supported OAuth flow with only the scopes their workflow requires.
  • Media must finish uploading or importing before its ID is referenced by a post.
  • Provider connections, plan limits, role permissions, and approval requirements remain authoritative.

Questions

What people ask about social media publishing api

Is there an OpenAPI document?

Yes. The documentation build generates OpenAPI 3.1 from the typed Delulu contracts and provides an interactive explorer from the same document.

How can a client authenticate?

Supported bearer credentials include workspace-bound API keys, Delulu OAuth tokens, and supported first-party sessions. OAuth supports discovery, PKCE, device authorization, refresh, and revocation.

Can the API publish immediately?

Yes. Create a post with explicit publish-now intent, subject to account, role, scope, review, quota, and provider checks. Draft is safer when a human decision is still needed.

How do I confirm that every destination succeeded?

Read the post and its target states. Only completed successful target states confirm delivery; an accepted or processing response is not final confirmation.

Can an API key access every workspace?

No. API keys are workspace-bound and carry a frozen role plus narrowed scopes. Live membership is still checked on each request.

Related features

Works with these connected channels

Availability still depends on the post format, account type, and permissions described above.

Put social media publishing api into your real workflow

Connect an account, create the first piece of work, and see how Delulu fits your publishing process.

Create your account