Platitun · API · Catalogue and requests · Everything about a position

Everything about a position

GET /api/v1/catalog/services/{slug}

Key scope: catalog · read only

Vendor plans, allowed delivery methods per product type, allowed delivery and guarantee periods. Take the values for a new listing from here — no guessing, and these are the very values the marketplace validates against.

The models inside a plan are what distinguishes a marketplace listing from a listing with just a price. Show them to the buyer rather than hiding them.

Response fields

Field	Type	What it is
`service`	`string`	The service slug.
`productTypes`	`array`	Possible product types.
`deliveryMethods`	`object`	Which delivery methods each product type allows. The values come from the core — they cannot diverge from the validation.
`slaChoices`	`array`	Allowed delivery times in minutes.
`guaranteeChoices`	`array`	Allowed guarantee periods in days.
`description`	`object`	The service description in both languages.
`tariffs`	`array`	Vendor plans: slug, name, period, models inside and named products.

Refusal reasons

A rule refusal arrives as {"error":"rejected","refusal":{"kind":"…"}} with status 409. Refusals common to all endpoints are in the rules section.

Code	What happened and what to do
`not_found`	The record does not exist or is not yours. The ownership condition is in the database query itself, so someone else’s record looks like a missing one.

Nearby in this section

GET /api/v1/me — Who am I
GET /api/v1/catalog/services — Search the catalogue
GET /api/v1/catalog/usual-price — The usual price for a position
GET /api/v1/catalog/demand — Demand: what buyers are waiting for
GET /api/v1/catalog/requests — My catalogue requests
POST /api/v1/catalog/requests — Request a new catalogue position