Ocoya API

Name: Ocoya API API
Brand: Ocoya API
Availability: InStock

✓ Official Vendor SpecSocial MediaSocial PublishingapiKey7 EndpointsREST

For Agents

Schedule and retrieve social media posts, manage workspaces, and read connected social profiles through Ocoya's publishing API.

Quickstart

Get started with Ocoya API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"schedule a social media post across networks"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Ocoya API API.

Read the authenticated user's Ocoya profile via /me

List workspaces accessible to the API key holder

Read connected social profiles inside a workspace across networks

Schedule a new post to one or more social profiles via /post

Retrieve a previously created post by ID for status checks

GET STARTED

Start building with Ocoya API API

Explore with Jentic

View OpenAPI Spec

Use Cases

Patterns agents use Ocoya API API for, with concrete tasks.

★ Cross-Channel Post Scheduling

Schedule a single piece of content across multiple connected networks by listing the workspace's social profiles and submitting a /post request that targets the chosen profile IDs. Ocoya handles channel-specific rendering and queue timing. Useful for content teams that want to drive scheduling from a CMS, AI workflow, or bespoke calendar instead of clicking through the Ocoya UI.

Call /social-profiles, pick the LinkedIn and X profiles, then POST to /post with caption text and a future scheduled time.

AI-Generated Content Pipeline

Feed AI-generated captions and graphics into Ocoya by having an upstream agent write the copy, then calling /post with the generated text and an asset URL to schedule the publish. The workflow keeps the human-in-the-loop step inside Ocoya for review while letting an agent handle bulk drafting. Best suited to founders and small marketing teams running high-volume social calendars.

POST to /post with caption 'Launch day is here' and a scheduled time, then call /post/{postId} to confirm it was queued.

Workspace and Profile Audit

Audit which social profiles are connected to which Ocoya workspaces by reading /workspaces and /social-profiles. Useful for agencies running multiple client workspaces who need to confirm coverage and account ownership before a campaign starts. The endpoints return structured records that map cleanly into a CRM or operations spreadsheet.

Call /workspaces and for each one call /social-profiles, then return a table of workspace name and connected networks.

AI Agent Social Concierge

An AI agent embedded in a marketing chatbot can schedule posts on demand by routing to Ocoya through Jentic — the user types 'post this announcement on LinkedIn at 3pm Friday' and the agent finds the operation by intent, picks the right social profile, and submits the /post call. Credentials stay in the Jentic vault throughout.

Use Jentic to call /social-profiles, choose the LinkedIn profile, and POST to /post with caption and scheduled time.

Key Endpoints

7 endpoints — ocoya is a social media management platform with ai-assisted copy and graphics generation, and the public api exposes programmatic control over the core publishing surface.

METHOD

PATH

DESCRIPTION

GET

/me

Authenticated user profile

GET

/workspaces

List accessible workspaces

GET

/social-profiles

List connected social profiles

POST

/post

Schedule a new post

GET

/post/{postId}

Retrieve a post by ID

GET

/me

Authenticated user profile

GET

/workspaces

List accessible workspaces

GET

/social-profiles

List connected social profiles

POST

/post

Schedule a new post

GET

/post/{postId}

Retrieve a post by ID

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Ocoya API keys are stored encrypted in the Jentic vault. Agents receive scoped access — the X-API-Key value is injected at execution time and never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'schedule a social media post') and Jentic returns the matching Ocoya /post operation with its input schema, so the agent calls the right endpoint without browsing docs.

Time to first call

Direct Ocoya integration: 1-2 days for auth, schema mapping, and scheduling logic. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Buffer API

Schedule and analyse posts across multiple social networks

Choose Buffer when the agent needs deep analytics on post performance; Ocoya leans toward AI-assisted creation plus scheduling.

Alternative

Sprout Social API

Enterprise social management with publishing, listening, and reporting

Choose Sprout Social for large-team workflows with approvals and listening; Ocoya is lighter weight and better for solo or small-team use.

Complementary

Mailchimp API

Email and audience automation

Pair Mailchimp with Ocoya when an agent needs to coordinate email and social touches in the same campaign.

FAQs

Specific to using Ocoya API API through Jentic.

What authentication does the Ocoya API use?

An API key supplied via the X-API-Key header. Jentic stores the key encrypted in its vault and injects it at execution time so the raw secret never enters the agent's prompt.

Can I schedule a post to multiple networks at once with Ocoya?

Yes. Call /social-profiles to list the connected networks, then POST to /post with the IDs of every profile you want to publish to in the same call. Ocoya queues per-channel publication based on the scheduled time you supply.

What are the rate limits for the Ocoya API?

Ocoya does not publish a hard quota in the spec. Confirm your plan limits in the Ocoya dashboard before running bulk scheduling and respect any 429 responses with exponential backoff.

How do I retrieve a scheduled post status through Jentic?

Search Jentic for 'get an Ocoya post by ID', load the schema for /post/{postId}, and execute with the post ID. With pip install jentic the call is await client.search(...), await client.load(...), await client.execute(...) inside an asyncio.run wrapper.

Does the API expose AI copy or image generation directly?

The public API in this spec covers publishing primitives — workspaces, social profiles, and posts. Generate the AI copy or imagery upstream in your own pipeline, then submit the finished asset to /post.

Can I list all workspaces my Ocoya key has access to?

Yes. /workspaces returns every workspace tied to the authenticated key, which is essential for agencies operating across multiple client environments.