{"id":11767,"date":"2025-03-01T07:48:21","date_gmt":"2025-03-01T07:48:21","guid":{"rendered":"https:\/\/webnus.net\/dox\/modern-events-calendar\/?post_type=knowledgebase&p=11767"},"modified":"2026-06-18T09:28:49","modified_gmt":"2026-06-18T09:28:49","slug":"mec-restful-api","status":"publish","type":"knowledgebase","link":"https:\/\/webnus.net\/dox\/modern-events-calendar\/mec-restful-api\/","title":{"rendered":"MEC Restful API"},"content":{"rendered":"\n

The RESTful API<\/strong> in Modern Events Calendar allows developers to programmatically access, retrieve, and manage event data from external applications, websites, or services. It provides a structured and standardized way to interact with MEC data (such as events, locations, organizers, and schedules) without relying on the WordPress interface. This makes it suitable for integrations with mobile apps, third-party platforms, or custom front-end implementations.<\/p>\n\n\n\n

<\/span><\/a>Base URL<\/span><\/h2>\n\n\n\n

The base URL is different per website but the general pattern is like the following.<\/p>\n\n\n\n

http://example.com\/wp-json\/mec\/v1.0<\/code><\/pre>\n\n\n\n
<\/span>API Key<\/span><\/h2>\n\n\n\n
The API key is required for all the following commands. You should send the API key in headers with the name of mec-token<\/strong> If you don\u2019t send mec-token in headers then you will receive an invalid_api_token<\/strong> error.<\/p>\n\n\n\n
<\/span><\/a>All Events<\/span><\/h2>\n\n\n\n
GET<\/strong>    \/events\/<\/code><\/pre>\n\n\n\n
This is a public command, it means all users with an API key can run it.<\/p>\n\n\n\n
<\/span>Request<\/span><\/h3>\n\n\n\n
Send the following parameters as JSON.<\/p>\n\n\n\n
Name<\/strong><\/td>Type<\/strong><\/td>Accepted Values<\/strong><\/td>Example<\/strong><\/td><\/tr>
limit<\/td>integer<\/td> <\/td>12<\/td><\/tr>
order<\/td>string<\/td>ASC \/ DESC<\/td>ASC<\/td><\/tr>
offset<\/td>integer<\/td> <\/td>0<\/td><\/tr>
start<\/td>string<\/td>today \/ date \/ tomorrow \/ yesterday\/ start_last_month \/ start_current_month \/ start_next_month<\/td>date<\/td><\/tr>
start_date<\/td>string<\/td>(yyyy-mm-dd)<\/td>2024-12-15<\/td><\/tr>
show_only_past_events<\/td>integer<\/td>0,1<\/td>0<\/td><\/tr>
include_past_events<\/td>integer<\/td>0,1<\/td>0<\/td><\/tr>
show_only_ongoing_events<\/td>integer<\/td>0,1<\/td>0<\/td><\/tr>
include_ongoing_events<\/td>integer<\/td>0,1<\/td>0<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
You will receive all events in the events<\/strong> key of the response. Events are categorized based on their start date so you can utilize that to display the events in any format you need like list view, monthly calendar view, weekly timetable view or anything else.<\/p>\n\n\n\n
You can also use the pagination key of the response to read all events page by page. Just send the next_date<\/strong> value as start_date<\/strong> of your next request and send next_offset<\/strong> as the value of the offset<\/strong> parameter.<\/p>\n\n\n\n
{\n   \"events\": {\n      \"2025-01-15\": [{ ... }],\n\t...\n   },\n   \"pagination\": {\n       \"next_date\": \"2025-12-15\",\n       \"next_offset\": 1,\n       \"has_more_events\": true,\n       \"found\": 12\n   }\n}<\/code><\/pre>\n\n\n\n
<\/span>Single Event<\/span><\/h2>\n\n\n\n
GET<\/strong>    \/events\/{id}<\/code><\/pre>\n\n\n\n
This is a public command, it means all users with an API key can run it.<\/p>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
Send the following parameters as a query string.<\/p>\n\n\n\n
Name<\/strong><\/td>Type<\/strong><\/td>Example<\/strong><\/td><\/tr>
id *<\/strong><\/td>integer<\/td>1<\/td><\/tr>
occurrence<\/td>integer<\/td>1747335600<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
You will receive a bunch of information included but not limited to the following. The data<\/strong> key has many useful information about the event that you can use in your application. The dates<\/strong> key has upcoming dates of the event. You can send the start timestamp value that you can see as an occurrence value in the query string to move forward in the time. Also the date<\/strong> key holds information about the current occurrence.<\/p>\n\n\n\n
{\n   \"ID\": 1,\n   \"data\": { ... },\n   \"dates\": [{\n     \"start\": {\n         \"date\": \"2025-05-15\",\n         \"hour\": 7,\n         \"minutes\": \"0\",\n         \"ampm\": \"PM\",\n         \"timestamp\": 1747335600\n     },\n     \"end\": {\n         \"date\": \"2025-05-15\",\n         \"hour\": 11,\n         \"minutes\": \"0\",\n         \"ampm\": \"PM\",\n         \"timestamp\": 1747350000\n     },\n     \"allday\": \"0\",\n     \"hide_time\": \"0\",\n     \"past\": 0\n   }],\n   \"date\": {}\n}<\/code><\/pre>\n\n\n\n
<\/span>Login<\/span><\/h2>\n\n\n\n
POST<\/strong>    \/login<\/code><\/pre>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
Send the following parameters as regular-form data.<\/p>\n\n\n\n
Name<\/strong><\/td>Type<\/strong><\/td>Example<\/strong><\/td><\/tr>
username *<\/strong><\/td>string<\/td>user<\/td><\/tr>
password *<\/strong><\/td>string<\/td>12345678<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
Use the token<\/strong> to authorize users in other commands. You should send it as a new header named user-token<\/strong> for those commands that require authentication like my-events or trash events commands.<\/p>\n\n\n\n
{\n   \"success\": 1,\n   \"id\": 1,\n   \"token\": \"W2X53XpClol8TquAIKWaZo0j68L0tuho3o4wmwD0\"\n}<\/code><\/pre>\n\n\n\n
<\/span>Upload Image<\/span><\/h2>\n\n\n\n
POST<\/strong>    \/images<\/code><\/pre>\n\n\n\n
Users must be authenticated for this command. Both mec-token and user-token should be included in the headers.<\/p>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
Send following parameters as JSON.<\/p>\n\n\n\n
Name<\/strong><\/td>Type<\/strong><\/td>Example<\/strong><\/td><\/tr>
image *<\/strong><\/td>file<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
Use the image_id<\/strong> in other commands like creating events, etc.<\/p>\n\n\n\n
{\n    \"success\": 1,\n    \"image_id\": 10\n}<\/code><\/pre>\n\n\n\n
<\/span>Upload File<\/span><\/h2>\n\n\n\n
POST<\/strong>    \/files<\/code><\/pre>\n\n\n\n
Users must be authenticated for this command. Both mec-token and user-token should be included in the headers.<\/p>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
Send the following parameters as JSON.<\/p>\n\n\n\n
Name<\/strong><\/td>Type<\/strong><\/td>Example<\/strong><\/td><\/tr>
file *<\/strong><\/td>file<\/td><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
Use the file_id<\/strong> in other commands like creating events, etc.<\/p>\n\n\n\n
{\n    \"success\": 1,\n    \"file_id\": 10\n}<\/code><\/pre>\n\n\n\n
<\/span>Create Event<\/span><\/h2>\n\n\n\n
POST<\/strong>    \/events<\/code><\/pre>\n\n\n\n
Users must be authenticated for this command. Both mec-token and user-token should be included in the headers.<\/p>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
Send the following parameters as JSON.<\/p>\n\n\n\n
Name<\/strong><\/td>Type<\/strong><\/td>Example<\/strong><\/td><\/tr>
title *<\/strong><\/td>string<\/td>Event Title<\/td><\/tr>
content<\/td>string<\/td>Event Content<\/td><\/tr>
location[name]<\/td>string<\/td>Art Gallery<\/td><\/tr>
location[address]<\/td>text<\/td>Art Gallery, City<\/td><\/tr>
location[latitude]<\/td>float<\/td><\/td><\/tr>
location[longitude]<\/td>float<\/td><\/td><\/tr>
location[thumbnail]<\/td>int<\/td>10<\/td><\/tr>
organizer[name]<\/td>string <\/td>John Due<\/td><\/tr>
organizer[email] <\/td>email <\/td>john.due@gmail.com<\/td><\/tr>
organizer[tel]<\/td>tel <\/td>+13007772299<\/td><\/tr>
organizer[url]<\/td>url <\/td>https:\/\/google.com<\/td><\/tr>
organizer[thumbnail]<\/td>number <\/td>10<\/td><\/tr>
start_date<\/td>date (yyyy-mm-dd)<\/td>2025-06-01<\/td><\/tr>
start_hour<\/td>int<\/td>10<\/td><\/tr>
start_minutes<\/td>int<\/td>15<\/td><\/tr>
start_ampm<\/td>string <\/td>AM<\/td><\/tr>
end_date<\/td>date (yyyy-mm-dd)<\/td>2025-06-01<\/td><\/tr>
end_hour<\/td>int<\/td>2<\/td><\/tr>
end_minutes<\/td>int<\/td>45<\/td><\/tr>
end_ampm<\/td>string<\/td>PM<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
Use the event_id<\/strong> in other commands like get single event, etc.<\/p>\n\n\n\n
{\n    \"success\": 1,\n    \"message\": \"The event is published.\",\n    \"event_id\": 12\n}<\/code><\/pre>\n\n\n\n
<\/span>Edit Event<\/span><\/h2>\n\n\n\n
PUT<\/strong>    \/events\/{id}<\/code><\/pre>\n\n\n\n
Users must be authenticated for this command. Both mec-token and user-token should be included in the headers.<\/p>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
The request is exactly like the create event command.<\/p>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
The response is also exactly like the create event command.<\/p>\n\n\n\n
<\/span><\/a>My Events<\/span><\/h2>\n\n\n\n
GET<\/strong>    \/my-events<\/code><\/pre>\n\n\n\n
Users must be authenticated for this command. Both mec-token and user-token should be included in the headers.<\/p>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
Send the following parameters as JSON.<\/p>\n\n\n\n
Name<\/strong><\/td>Type<\/strong><\/td>Example<\/strong><\/td><\/tr>
limit *<\/strong><\/td>integer<\/td>12<\/td><\/tr>
pages *<\/strong><\/td>integer<\/td>1<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
You can loop through the events to display all events. Use the pagination data to navigate through the pages of events.<\/p>\n\n\n\n
{\n   \"events\": [\n       {\n           \"id\": 2645,\n           \"title\": \"Monthly\",\n           \"url\": \"http:\/\/example.com\/events\/monthly\/\",\n           \"status\": \"publish\"\n       }\n   ],\n   \"pagination\": {\n       \"current_page\": 2,\n       \"total_pages\": 5\n   }\n}<\/code><\/pre>\n\n\n\n
<\/span><\/a>Trash Event<\/span><\/h2>\n\n\n\n
DELETE<\/strong>    \/events\/{id}\/trash<\/code><\/pre>\n\n\n\n
Users must be authenticated for this command. Both mec-token and user-token should be included in the headers.<\/p>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
None.<\/p>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
If the command was successful you will receive the following response otherwise an error object with proper http code will be returned.<\/p>\n\n\n\n
{\n   \"success\": 1\n}<\/code><\/pre>\n\n\n\n
<\/span><\/a>Delete Event<\/span><\/h2>\n\n\n\n
DELETE<\/strong>    \/events\/{id}<\/code><\/pre>\n\n\n\n
Users must be authenticated for this command. Both mec-token and user-token should be included in the headers.<\/p>\n\n\n\n
This command will force delete an event. It doesn\u2019t matter if the event is already trashed or not.<\/p>\n\n\n\n
<\/span><\/a>Request<\/span><\/h3>\n\n\n\n
None.<\/p>\n\n\n\n
<\/span><\/a>Response<\/span><\/h3>\n\n\n\n
If the command was successful you will receive the following response otherwise an error object with proper http code will be returned.<\/p>\n\n\n\n
{\n   \"success\": 1\n}<\/code><\/pre>\n\n\n\n
<\/span>Taxonomy Entities<\/span><\/h2>\n\n\n\n
These endpoints allow you to manage MEC taxonomy entities including categories, tags, labels, speakers, and sponsors.<\/p>\n\n\n\n
Users must be authenticated for these commands. Both mec-token<\/code> and user-token<\/code> should be included in the headers.<\/p>\n\n\n\n
<\/span>List Taxonomy Entities<\/span><\/h3>\n\n\n\n
GET<\/strong>    \/taxonomies\/{entity}<\/code><\/pre>\n\n\n\n
<\/span>Path Parameters:<\/strong><\/span><\/h4>\n\n\n\n
Parameter<\/strong><\/strong><\/td>Type<\/strong><\/td>Description<\/strong><\/strong><\/td><\/tr>
entity<\/td>string<\/td>The entity type. One of:\u00a0categories<\/code>,\u00a0tags<\/code>,\u00a0labels<\/code>,\u00a0speakers<\/code>,\u00a0sponsors<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span>Query Parameters:<\/strong><\/span><\/h4>\n\n\n\n
Parameter<\/strong><\/strong><\/td>Type<\/strong><\/td>Default<\/strong><\/td>Description<\/strong><\/strong><\/td><\/tr>
limit<\/td>int<\/td>20<\/td>Number of items per page<\/td><\/tr>
paged<\/td>int<\/td>1<\/td>Page number<\/td><\/tr>
orderby<\/td>string<\/td>name<\/td>Sort field. Options:\u00a0name<\/code>,\u00a0slug<\/code>,\u00a0count<\/code>,\u00a0term_id<\/code><\/td><\/tr>
order<\/td>string<\/td>ASC<\/td>Sort order. Options:\u00a0ASC<\/code>,\u00a0DESC<\/code><\/td><\/tr>
search<\/td>string<\/td><\/td>Search term to filter results<\/td><\/tr>
hide_empty<\/td>boolean<\/td>false<\/td>Whether to hide empty terms<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/span>Sample Response:<\/strong><\/span><\/h4>\n\n\n\n
{\n    \"data\": {\n        \"categories\": [\n            {\n                \"id\": 1,\n                \"name\": \"Music\",\n                \"slug\": \"music\",\n                \"description\": \"\",\n                \"count\": 5,\n                \"taxonomy\": \"mec_category\",\n                \"icon\": \"\",\n                \"color\": \"\",\n                \"fallback_image\": \"\",\n                \"parent\": 0\n            }\n        ],\n        \"pagination\": {\n            \"current_page\": 1,\n            \"per_page\": 20,\n            \"total\": 1,\n            \"total_pages\": 1\n        }\n    },\n    \"status\": 200\n}<\/code><\/pre>\n\n\n\n
<\/span>Notes:<\/strong><\/span><\/h4>\n\n\n\n