SceniqDevelopers

reorder_itinerary

Move an itinerary between two neighbours.

PUT/v1/itineraries/{itineraryId}/position
MCP tool reorder_itineraryScope: writeBetaSince 2026-10-06.3
Markdown

Place the itinerary after previousId and before nextId, like reorder_chapter. Either neighbour may be omitted for the ends; with neither, move to the end.

curl -X PUT "https://sceniq.earth/api/v1/itineraries/ki7a2c4e6g8j0m2p4s6v8y0b2d4f6h8k/position" \
  -H "Authorization: Bearer $SCENIQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "nextId": "ki7b3d5f7h9k1n3q5t7w9z1c3e5g7j9m"
}'

Path parameters

Body parameters

  • nextIdstring · itineraries idoptional

    Id of the itinerary of this guide that should follow it.

  • previousIdstring · itineraries idoptional

    Id of the itinerary of this guide that should precede it.

Returns

200 OK with ItineraryAck: An itinerary position acknowledgement.

  • okbooleanrequired

    Always true: the write went through.

    Always true

  • itineraryIdstring · itineraries idrequired

    The itinerary moved.

Response 200
{
  "ok": true,
  "itineraryId": "ki7a2c4e6g8j0m2p4s6v8y0b2d4f6h8k"
}

Errors

Every error is { error: { code, message } }. Act on the code.

  • 400invalid_argumentA required field is missing, a field is unknown, or a value does not match its type (the Convex validator's path and value are in the message).
  • 400invalid_requestA writer refused a value: a map link on a host that is not allowed, a title that is too long, a date that does not exist, too many items in a list. The message is the writer's own sentence.
  • 401unauthenticatedThe request carries no key. Send it as Authorization: Bearer sk_sceniq_... (or X-Api-Key).
  • 401invalid_api_keyThe key is unknown, revoked or expired.
  • 403api_scope_requiredA read-only key called a write operation, or a key without the publish option called publish_changes.
  • 403forbiddenThe key belongs to a creator account that is no longer active.
  • 404not_foundThe id does not exist or belongs to another creator. The two answers are identical on purpose, so ids never reveal what exists.
  • 413payload_too_largeA JSON body over 2 MB, an image over 6 MB, a batch upload over 19 MB, or an MCP message over 2 MB.
  • 429rate_limitedOver a limit: requests per key per minute, per creator per hour, uploads per key per minute, or check_links per guide per hour.
  • 500internal_errorAn unexpected failure. The message is hidden on purpose.