elefymove

开发者文档

ElefyMove Open API 的指南与参考。

这些指南目前仅提供英文版。

Endpoints

方法端点权限范围用途
POST/api/public/v1/community/postscommunity:write提交一篇社区帖子。合作伙伴创建的帖子都会先进入审核,不会立即发布。
GET/api/public/v1/community/postscommunity:read列出你自己的社区帖子及其审核状态。
GET/api/public/v1/community/posts/{externalId}community:read按你指定的外部 ID 读取你的某篇社区帖子。
PATCH/api/public/v1/community/posts/{externalId}community:write更新你的社区帖子;未提交的字段保持不变。
DELETE/api/public/v1/community/posts/{externalId}community:write下架你的社区帖子。

How community posts work

  • You identify each post by your own externalId, the same pattern as listings.
  • A post you create does not publish instantly: it lands as pending and goes through ElefyMove moderation before it is visible to anyone else. Read moderationStatus on the response, or poll GET /community/posts/:externalId, to track it.
  • An image supplied as a URL is fetched and re-hosted by ElefyMove — your URL is never stored or linked directly, the same handling as listing photos.
  • Posts created with a test key stay pending permanently and never appear on any public surface, regardless of moderation — the sandbox has no path to publish.
  • PATCH is a partial update — any field you omit is left unchanged. A content edit to an already-published post can send it back to pending for re-review. DELETE unpublishes it (it does not erase history).