elefymove
Dokumentation

Entwicklerdokumentation

Leitfäden und Referenz für die ElefyMove Open API.

Diese Leitfäden sind derzeit nur auf Englisch verfügbar.

Endpoints

MethodeEndpunktScopeFunktion
POST/api/public/v1/community/postscommunity:writeEinen Community-Beitrag einreichen. Jeder von einem Partner erstellte Beitrag durchläuft die Moderation und wird nicht sofort veröffentlicht.
GET/api/public/v1/community/postscommunity:readIhre eigenen Community-Beiträge und deren Moderationsstatus auflisten.
GET/api/public/v1/community/posts/{externalId}community:readEinen eigenen Community-Beitrag über die von Ihnen vergebene externe ID abrufen.
PATCH/api/public/v1/community/posts/{externalId}community:writeEinen eigenen Community-Beitrag aktualisieren; ausgelassene Felder bleiben unverändert.
DELETE/api/public/v1/community/posts/{externalId}community:writeEinen eigenen Community-Beitrag depublizieren.

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