Developer documentation

Guides and reference for the ElefyMove Open API.

Endpoints

Method	Endpoint	Scope	What it does
POST	`/api/public/v1/community/posts`	`community:write`	Submit a community post. Every partner-created post enters moderation and does not publish instantly.
GET	`/api/public/v1/community/posts`	`community:read`	List your own community posts and their moderation status.
GET	`/api/public/v1/community/posts/{externalId}`	`community:read`	Read one of your community posts by the external ID you assigned it.
PATCH	`/api/public/v1/community/posts/{externalId}`	`community:write`	Update one of your community posts; any field you omit is left unchanged.
DELETE	`/api/public/v1/community/posts/{externalId}`	`community:write`	Unpublish one of your community posts.

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