elefymove

Documentation développeur

Guides et référence de l'Open API ElefyMove.

Ces guides ne sont disponibles qu'en anglais pour le moment.

Endpoints

MéthodeEndpointPortéeRôle
POST/api/public/v1/community/postscommunity:writeSoumettez une publication communautaire. Toute publication créée par un partenaire entre en modération et n'est pas publiée instantanément.
GET/api/public/v1/community/postscommunity:readListez vos propres publications communautaires et leur statut de modération.
GET/api/public/v1/community/posts/{externalId}community:readConsultez une de vos publications communautaires via l'identifiant externe que vous lui avez attribué.
PATCH/api/public/v1/community/posts/{externalId}community:writeMettez à jour une de vos publications communautaires ; les champs omis restent inchangés.
DELETE/api/public/v1/community/posts/{externalId}community:writeDépubliez une de vos publications communautaires.

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