marketplace

POST /v1/marketplace/guest-post-sites/{site_uid}/order

Order a guest post on one site — opens a support ticket in the caller's org.

All marketplace endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the tickets.reply permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a field in the JSON body.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/marketplace/guest-post-sites/{site_uid}/order \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{  }'

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

GUESTFEED1114: no payment is taken here; the ticket (origin guest_post_site_order) carries the site, the chosen offer and its price, and staff fulfil it with the seller. Requires tickets.reply in the org (the caller's scope or X-Zinn-Org). An unknown site or offer index is 404.

Parameters

NameTypeRequiredWhat it is
site_uid (path)stringYes—

Request body

NameTypeRequiredWhat it is
offer_indexintegerNo—
notestringNo—
org_idstringNo—

Response

NameTypeRequiredWhat it is
ticket_idstringYes—
site_uidstringYes—
price_minorobjectNo—
currencystringYes—

Errors this endpoint can return

401 · 403 · 404