Editing events

To edit event details, such as name, location, description, visibility and more, you must use the event.edit endpoint operation. Any edit will reflect the event pages right away and data that is not intrinsic to the event model can't be edited over here (like tools, forms, emails and others), they will be discussed on their own API model guide.

Keys allowed

{
    "name": "event name",
    "nickname": "event url path",
    "email": "organization email",
    "description": "general description (summary of event) - accepts HTML content",
    "cover": "cover image url",
    "dateBegin": "begin date (timestamp)",
    "dateEnd": "end date (timestamp)",
    "enrollmentBegin": "timestamp from begin of enrollment",
    "enrollmentEnd": "timestamp from end of enrollment",
    "latitude": "latitude",
    "longitude": "longitude",
    "address": "address on google map",
    "fugleman": "organization name",
    "website": "website url",
    "accessCode": "event access code (in case it's private)",
    "facebook": "facebook page url",
    "twitter": "twitter profile url",
    "wireless": "wireless network information (wifi)",
    "visible": "visibility (boolean - 0 & 1)",
    "public": "privacy (boolean - 0 & 1)",
    "automaticEnrollment": "automatic enrollment (mobile app - boolean - 0 & 1)"
}

Example

This endpoint allows you to edit one field at a time and it expects the following query attributes: tokenID, eventID and key and the following body attribute: value. Please see the example below.

curl --request POST \
     --url 'https://inevent.com/api/?action=event.edit&tokenID=YOUR_TOKEN_HERE&eventID=YOUR_EVENT_ID&key=name' \
     --header 'Accept: application/json' \
     --header 'Content-Type: application/x-www-form-urlencoded' \
     --data value=NewName!

What’s Next