Snyho documentation

Getting started

Connecting WordPress (application passwords)

1. In WordPress, use HTTPSand set permalinks to anything other than "Plain" so the REST API routes resolve correctly.
2. Create or pick a user with Editor (or appropriate) capabilities — avoid wiring your personal admin password into third-party tools.
3. Go to Users → Profile, open Application Passwords, name the key (e.g. "Snyho"), and copy the generated password.
4. In Snyho Projects, paste the site URL, username, and application password. Test the connection from the project settings flow.

If you see 401 errors, verify the password, user role, and that your host is not stripping the Authorization header (Apache may need CGIPassAuth On). 403 often indicates a WAF or security plugin blocking REST traffic — allowlist your editor traffic.

Connecting social accounts (OAuth-style tokens)

Social publishing uses per-network credentialsstored on the project (e.g. bearer tokens or page tokens depending on the network). Enter values in the project's social fields from the dashboard; keep tokens rotated on the same cadence you use for other marketing stacks.

• X (Twitter): use a bearer or token appropriate to your posting workflow.
• Meta (Facebook): use a page access token with the scopes required to publish on behalf of the page.
• LinkedIn: configure a token with share permissions for your company or showcase page.

After saving, open the Social Hub to confirm the project is eligible and that your role allows publishing (some roles are view-only by design).

The Pro workspace editor

The workspace editor is a TipTap-based rich text surface tuned for long articles: headings, lists, quotes, links, and embed-friendly content. Use the project selector to choose which WordPress site receives publishes.

Image upload & media library

When you attach a featured image, the web app uploads through Snyho's secure upload API, then includes that asset when you publish so WordPress can attach it to the post. Inline images follow the same pattern where supported — prefer compressed JPEG/PNG/WebP within your host's upload limits.

• Use descriptive file names — they often flow through to media library entries.
• Large files may hit PHP upload_max_filesize caps on smaller hosts.

Live SEO analyzer

The analyzer scores your draft against common on-page SEO signals so you fix issues while writing, not after export.

• Focus keyword: taken from your SEO keywords field (first token is treated as primary). Density and placement in title, headings, and body affect the score.
• Meta & slug: checks presence and sensible length for meta descriptions and URL slugs.
• Alt text & structure: encourages descriptive alt text on images and a logical heading hierarchy for readers and crawlers.

Scores are heuristic guides, not guarantees of ranking — use them to catch obvious gaps before client review or publication.

AI text & image studios

AI Text Studio

From the article body (or excerpt), generate platform-ready social copy for X, Facebook, and LinkedIn. Bring your own model keys where required (BYOK) so you control cost and data residency policies.

• Review every generated line for tone and factual accuracy before publishing.
• Tweak hooks and CTAs to match each network's norms (threads vs. single posts, etc.).

AI Image Studio

Higher tiers can generate marketing visuals via integrated image models (e.g. Flux through configured providers). Use clear prompts tied to the article narrative; iterate sizes for social cards vs. hero images.

Social command center

The Social Hub is where you compose, preview, and ship to connected networks. Depending on configuration, you can publish immediately or rely on scheduled jobs where enabled.

• Instant publish: sends the payload now — ideal for launch moments and coordinated blog + social drops.
• Scheduling (cron-backed where available): queues posts for later windows so teams can batch production without losing cadence.
• X, Meta, LinkedIn: each path validates tokens and surfaces errors early — fix scopes or expirations in the project settings, then retry.

Magic client approvals (Agency only)

On the Agency plan, you can generate a secure magic link for any draft. The client opens the page without a Snyho login, reads the article (including featured image when provided), and either approves or submits structured feedback.

1. Finish the draft in the workspace editor and set a featured image if needed.
2. Click Request client approval — the server issues a token-backed URL.
3. Copy the link from the sidebar and send it via email or chat. Links are single-use for approve/reject flows per policy shown to the client.
4. Feedback returns to your editor with a high-visibility banner when rejected; use Fix / Edit from the Client Approvals hub to jump straight into the draft.

Enforcement: creating approval links requires an Agency effective plan computed from your database subscription and trial windows — the UI disables the action on lower tiers, and the API returns 403 if someone bypasses the client.

Hybrid referral program

Every eligible account can share a personal referral link (see Dashboard → Referrals). The hybrid program combines time-based bonuses with revenue share:

• Free days: successful referrals can extend your trial-style access window (commonly communicated as bundles of bonus days — see in-app copy for current thresholds).
• 20% commission: on qualifying paid conversions from invited accounts, a portion accrues toward your wallet balance according to program rules.
• USDT payouts: where enabled, withdrawals follow the wallet flows documented in-app — always verify destination addresses carefully.

Program details may evolve; the dashboard always reflects the latest rules tied to your account.

WordPress deep dive

Snyho talks to WordPress through the official REST API. Pretty permalinks, TLS, and reachable /wp-json/ routes are mandatory for reliable publishing.

Common errors

• 404 on REST: flush permalinks; check for aggressive rewrites.
• 413 / media: raise upload limits or shrink assets.
• 502 / 504: reduce concurrency or extend PHP timeouts for heavy media batches.

API limits & webhooks

Client-side pacing and queues smooth bursts so shared infrastructure and your WordPress tier stay healthy. Higher plans raise parallelism and headroom — see Pricing for tier ceilings.

Webhooks and sync acknowledgments use backoff and idempotencyso transient errors don't duplicate side effects; jobs reschedule until success or exhaustion.