Offers
Offers received and sent — read-only in batch 1.
Offers aren't public: each key only sees what it's allowed to — the listing's beneficiary, or its own sent offers.
Offers on one of your listings
curl https://api.ajungem.ro/v1/listings/7J769R/offers \
-H "Authorization: Bearer ajk_live_…"
Requires offers:read and the listing to belong to the key's holder. Otherwise, 404 not_found — same as for a listing that doesn't exist, so we don't confirm which codes are valid.
Your offers
curl https://api.ajungem.ro/v1/offers/mine \
-H "Authorization: Bearer ajk_live_…"
Offers sent by the account (or company) behind the key.
An offer, by id
curl https://api.ajungem.ro/v1/offers/9c1f… \
-H "Authorization: Bearer ajk_live_…"
Visible to the two participants: the carrier who sent it and the listing's beneficiary. Anyone else gets 404 not_found.
Fields: id, listingRef, price, currency, availableDate, message, status (sent, accepted, declined, withdrawn, expired), expiresAt, revisions, createdAt, updatedAt, url, plus carrier — the offering party's minimal public profile (name, isCompany, verified). No phone number. See the Offer object.
POST /listings/{ref}/offers (sending an offer through the API) is a proposed product extension, not an already-granted permission — planned for verified business keys, in batch 4. Accepting an offer stays site-only, in every batch: see Product rules.