개발자 문서

ElefyMove Open API 가이드와 레퍼런스.

이 가이드는 현재 영어로만 제공됩니다.

Endpoints

메서드	엔드포인트	스코프	설명
POST	`/api/public/v1/community/posts`	`community:write`	커뮤니티 게시물을 제출합니다. 파트너가 작성한 게시물은 모두 심사에 들어가며 즉시 게시되지 않습니다.
GET	`/api/public/v1/community/posts`	`community: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`	본인의 커뮤니티 게시물을 게시 중단합니다.

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).