Complete API documentation for MIDAS Web Based Room and Resource Scheduling Software. Our optional API allows you to interface with the scheduling system from your own web sites/applications. Find our more at http://mid.as/api
Line Messaging API Integration with Spring-BootInnovationM
The Line Messaging API is to establish communication between Line ChatBot and your server. If you want to create a chatbot where line user can send message’s and your server will reply for those messages then Line Messaging API is the right choice for you.
This presentation provides an introduction to API Facade pattern. It describes what the problem is, how the pattern solves the problem and how such a pattern can be utilized in real deployments.
Line Messaging API Integration with Spring-BootInnovationM
The Line Messaging API is to establish communication between Line ChatBot and your server. If you want to create a chatbot where line user can send message’s and your server will reply for those messages then Line Messaging API is the right choice for you.
This presentation provides an introduction to API Facade pattern. It describes what the problem is, how the pattern solves the problem and how such a pattern can be utilized in real deployments.
Kolkata Salesforce Developer Group Online - Summer '17Ashwani Soni
Here is the slide presented at Kolkata Developer group. It was a great session indeed. We will come with more great topics in next session. #SalesforceDGKolkata
Educar y formar también es tu responsabilidad 41091proyecto2013cpe
MARCO CONCEPTUAL
LA EDUCACIÓN EN VALORES Y LA PRÁCTICA EN EL AULA.
Según José María Parra Ortiz de la UNIVERSIDAD COMPLUTENSE de Madrid.
• La educación es aquella actividad cultural que se lleva a cabo en un contexto intencionalmente organizado para la transmisión de conocimiento, las habilidades y los valores que son demandados por el grupo social. Así pues todo proceso educativo está relacionado con los valores. En todo tiempo y lugar, la escuela ha contribuido, de forma decisiva, al proceso de socialización de los jóvenes, decisiones en los valores comunes compartidos por el grupo social con el fin de garantizar el orden en la vida social y comunidad.[1]
EL VALOR DE LA RESPONSABILIDAD.
Es un valor que está en la conciencia de la persona que permite, reflexionar, administrar, orientar y valorar las consecuencias de sus actos, siempre en lo pleno de su moral. La persona responsable es aquella que actúa conscientemente siendo ella causa directa o indirecta de un hecho ocurrido. Está obligado a responder por alguna cosa o una persona.
¿Responsabilidad ante quién? El hombre es responsable de sus actos ante quien es capaz de dictar normas y esto puede hacerlo Dios (responsabilidad moral), uno mismo (juicio de conciencia) y otros hombres.
La responsabilidad es un valor que ejecutamos a diario. Desde corta edad se les debe inculcar que las tareas escolares son su responsabilidad, y el no ser responsable trae como consecuencia bajar su rendimiento. Siendo responsable podemos convivir pacíficamente en la familia y en la sociedad.[2]
PARA SER RESPONSABLE SE DEBE TENER EN CUENTA:
• Percatarnos de lo que todo lo que hagamos tiene una consecuencia, depende de nosotros mismos.
• Lograr de manera estable que nuestros actos corresponden a nuestras promesas.
• Educar la responsabilidad, e ir corrigiendo lo que no hacemos bien y volverá a empezar.
• Reflexionar seriamente antes de tomar cualquier decisión que pueda afectar nuestra propia vida y la de los demás.
• Responder por todo lo que hacemos si está bien hecho sí o no.
• Reconocer los errores que cometemos y estar dispuestos a repararlos.
• Es importante cimentar valores en nuestros estudiantes como la lealtad, respeto, solidaridad entre otros, pero la responsabilidad es base fundamental para que ellos puedan salir airosos en todas las situaciones que la vida les presente, pues podrán cumplir cabalmente todas las tareas que le sean asignadas.
La realidad es que a los jóvenes les falta ponerse metas a corto, mediano y largo plazo, al hacerlo con responsabilidad, esfuerzo, dedicación los estudiantes podrán luchar por alcanzar sus objetivos, empezando por los más factibles y cercanos, que son como escalones que irán superando poco a poco, estas servirán como medición en las propuestas que tendrán un fin específico al alcanzar tan anhelada meta final que en el caso de ellos será la culminación del año escolar.
Para log
Knowledge of Unseen - Ilm-e-ghayeb-علم الغيبIffu Slides
Knowledge of Unseen (Ilm ul Gaib).
Knowledge of the unseen is something that Allaah has kept for Himself, as is indicated by the texts of the Qur’aan and Sunnah.
Shaykh Ibn ‘Uthaymeen (may Allaah have mercy on him) said: The noblest of the angelic Messengers, Jibreel, asked the noblest of the human Messengers, Muhammad (peace and blessings of Allaah be upon him), “Tell me about the Hour.” He said: “The one who is asked about it is does not know any more about it than the one who is asking” meaning, just as you have no knowledge of it, I have no knowledge of it either.
Kolkata Salesforce Developer Group Online - Summer '17Ashwani Soni
Here is the slide presented at Kolkata Developer group. It was a great session indeed. We will come with more great topics in next session. #SalesforceDGKolkata
Educar y formar también es tu responsabilidad 41091proyecto2013cpe
MARCO CONCEPTUAL
LA EDUCACIÓN EN VALORES Y LA PRÁCTICA EN EL AULA.
Según José María Parra Ortiz de la UNIVERSIDAD COMPLUTENSE de Madrid.
• La educación es aquella actividad cultural que se lleva a cabo en un contexto intencionalmente organizado para la transmisión de conocimiento, las habilidades y los valores que son demandados por el grupo social. Así pues todo proceso educativo está relacionado con los valores. En todo tiempo y lugar, la escuela ha contribuido, de forma decisiva, al proceso de socialización de los jóvenes, decisiones en los valores comunes compartidos por el grupo social con el fin de garantizar el orden en la vida social y comunidad.[1]
EL VALOR DE LA RESPONSABILIDAD.
Es un valor que está en la conciencia de la persona que permite, reflexionar, administrar, orientar y valorar las consecuencias de sus actos, siempre en lo pleno de su moral. La persona responsable es aquella que actúa conscientemente siendo ella causa directa o indirecta de un hecho ocurrido. Está obligado a responder por alguna cosa o una persona.
¿Responsabilidad ante quién? El hombre es responsable de sus actos ante quien es capaz de dictar normas y esto puede hacerlo Dios (responsabilidad moral), uno mismo (juicio de conciencia) y otros hombres.
La responsabilidad es un valor que ejecutamos a diario. Desde corta edad se les debe inculcar que las tareas escolares son su responsabilidad, y el no ser responsable trae como consecuencia bajar su rendimiento. Siendo responsable podemos convivir pacíficamente en la familia y en la sociedad.[2]
PARA SER RESPONSABLE SE DEBE TENER EN CUENTA:
• Percatarnos de lo que todo lo que hagamos tiene una consecuencia, depende de nosotros mismos.
• Lograr de manera estable que nuestros actos corresponden a nuestras promesas.
• Educar la responsabilidad, e ir corrigiendo lo que no hacemos bien y volverá a empezar.
• Reflexionar seriamente antes de tomar cualquier decisión que pueda afectar nuestra propia vida y la de los demás.
• Responder por todo lo que hacemos si está bien hecho sí o no.
• Reconocer los errores que cometemos y estar dispuestos a repararlos.
• Es importante cimentar valores en nuestros estudiantes como la lealtad, respeto, solidaridad entre otros, pero la responsabilidad es base fundamental para que ellos puedan salir airosos en todas las situaciones que la vida les presente, pues podrán cumplir cabalmente todas las tareas que le sean asignadas.
La realidad es que a los jóvenes les falta ponerse metas a corto, mediano y largo plazo, al hacerlo con responsabilidad, esfuerzo, dedicación los estudiantes podrán luchar por alcanzar sus objetivos, empezando por los más factibles y cercanos, que son como escalones que irán superando poco a poco, estas servirán como medición en las propuestas que tendrán un fin específico al alcanzar tan anhelada meta final que en el caso de ellos será la culminación del año escolar.
Para log
Knowledge of Unseen - Ilm-e-ghayeb-علم الغيبIffu Slides
Knowledge of Unseen (Ilm ul Gaib).
Knowledge of the unseen is something that Allaah has kept for Himself, as is indicated by the texts of the Qur’aan and Sunnah.
Shaykh Ibn ‘Uthaymeen (may Allaah have mercy on him) said: The noblest of the angelic Messengers, Jibreel, asked the noblest of the human Messengers, Muhammad (peace and blessings of Allaah be upon him), “Tell me about the Hour.” He said: “The one who is asked about it is does not know any more about it than the one who is asking” meaning, just as you have no knowledge of it, I have no knowledge of it either.
Dans l'hebdomadaire Deuzio du journal L'Avenir, Céline Fion interroge Christophe Chaptal de Chanteloup à propos des ingrédients insolites utilisés par l'industrie cosmétique.
The Schema-first API design approach advocates for writing your API definition first in one of many API Specification languages before writing any code. This talk introduces you to the realm of Schema-First API design and how to get started with the OpenAPI ecosystem.
[WSO2Con Asia 2018] Managing API Integrations with WSO2 API ManagerWSO2
Do you have difficulty when connecting with APIs, providing API integration, managing your APIs or dealing with protocols provided by APIs? If yes, this is the perfect session for you. In this session Piseth will provide a full understanding on:
- Managing API integrations, API security, and API requests (TPS)
- Allowing a single protocol for API requests
- Troubleshooting quickly
When SaaS companies use Blendr.io – an embedded integration platform – to boost their native integrations offering, we often receive the question – “What is a good API”? At Blendr.io, we have been working with hundreds of API’s and compiled an API Checklist for SaaS companies.
Practices and tools for building better API (JFall 2013)Peter Hendriks
Een belangrijke voorwaarde om goede en leesbare Java code te schrijven is om gebruik te maken van een goede API. Een goede API helpt ontwikkelaars om sneller hoogwaardige code te schrijven. Het ontwerp van een API is daarom belangrijk, zeker als er grotere systemen worden gerealiseerd in teamverband. Moderne ontwikkeltools als Eclipse, IntelliJ IDEA en FindBugs helpen met het schrijven van goede API, en het detecteren van slecht gebruik. Deze sessie gaat in op de laatste ontwikkelingen en mogelijkheden, inclusief nieuwe taalmogelijkheden in Java 8. Er wordt hierbij gebruik gemaakt van praktische situaties en concrete codevoorbeelden, gebaseerd op echte ervaringen in grote codebases. Met praktische tips en toegankelijke tools kan al een grote stap gemaakt worden om in de praktijk beter met API ontwerp om te gaan!
A well designed API has to be discoverable. MuleSoft anypoint platform API portal provides a centralized place for discovering all the tools (API Documentation, Mock API testing etc) that anybody can use to successfully discover an API.
MuleSoft anypoint platform API portal provides API Notebook, a web-based tool to explore the API in JavaScript scripting workspace. API Notebook generates API client from API RAML specification to understand API’s resources, methods, required arguments etc and allow user to make live call to API for personalized testing.
Super simple introduction to REST-APIs (2nd version)Patrick Savalle
See also: https://hersengarage.nl/rest-api-design-as-a-craft-not-an-art-a3fd97ed3ef4
An API in an interface or client-server-contract and REST is an HTTP design pattern. A REST-API is the de facto standard in web interface. It maps server resources onto URLs and allows CRUD-like manipulations of those (Create-Read-Update-Delete).
In this presentation we cover the basics of:
- The HTTP protocol
- The REST design pattern
- The API
These slides focus on documentation for REST APIs. See http://idratherbewriting.com for more detail. For the video recording, see http://youtu.be/0yfNd7tzH2Q. This deep dive is the second slide deck I used in the presentation.
Why your next serverless project should use AWS AppSyncYan Cui
In this webinar, Yan Cui and Lumigo Software Engineer Guy Moses will discuss some of the power of GraphQL and AppSync and why AppSync + Lambda + DynamoDB should be your stack of choice in 2021 and beyond!
A brief overview of some of the key features and benefits of MIDAS Room Booking software.
View more features at https://mid.as/features
Simply accessed through your favorite web browser, on your desktop, laptop, tablet or mobile device, MIDAS lets you see at a glance when your room bookings are scheduled in the calendar. The system also allows you to schedule staffing and equipment, send booking confirmations, reminders and invoices to clients, take bookings or booking requests through your public website, and put an end to double bookings and confusion once and for all!
As all you need is a modern web browser, your MIDAS booking system is readily available wherever you are! - Whether at the office, at home, or on the move - the information in your room booking system is right there at your fingertips!
MIDAS room booking software is available as either a cloud hosted SaaS (Software as a Service) solution, or as a self-hosted "on-premises" solution where it may be downloaded, installed, and run from your own server.
We also offer a no risk 30-day FREE trial! - Get yours today at https://mid.as/free-trial
This is the complete User Manual for MIDAS (https://mid.as/)
MIDAS is a leading room booking system giving you complete control over your room bookings and resource scheduling, and trusted by organizations and businesses of all shapes and sizes around the world.
Simply accessed through your favorite web browser, on your desktop, laptop, tablet or mobile device, the software lets you see at a glance when your room bookings are scheduled in the calendar. The system also allows you to schedule staffing and equipment, send booking confirmations, reminders and invoices to clients, take bookings or booking requests through your public website, and put an end to double bookings and confusion once and for all!
As all you need is a modern web browser, your MIDAS booking system is readily available wherever you are! - Whether at the office, at home, or on the move - the information in your room booking system is right there at your fingertips!
MIDAS room booking software is available as either a cloud hosted SaaS (Software as a Service) solution, or as a self-hosted "on-premises" solution where it may be downloaded, installed, and run from your own server.
We also offer a no risk 30-day FREE trial! - see https://mid.as/free-trial
Complete 84-page User and Administrative Guide to MIDAS v4.15.
MIDAS (https://mid.as) is a powerful and intuitive browser-based scheduling system that gives you complete control over your room bookings & resource scheduling. Accessed entirely from your favorite web browser, see at a glance when your bookings are scheduled, manage staffing & equipment, send confirmations & invoices to clients, take booking requests through your website, and put an end to confusion & double bookings once and for all!
As all you need is a browser, your MIDAS booking system is readily available wherever you are! - Whether at the office, at home, or on the move - from your desktop, laptop, tablet or mobile device - your booking information is right at your fingertips! Available to download (for use on your own server), or as cloud hosted SaaS (Software as a Service), MIDAS drastically cuts down on your costs, by streamlining the time spent on booking & administrative tasks, and reducing the amount of paperwork!
Manuals for other versions may be obtained via https://mid.as/manuals
MIDAS - Web Based Room & Resource Scheduling Software - LDAP (Active Director...MIDAS
This is the complete User Manual for MIDAS (http://mid.as/), a complete web based scheduling solution giving you complete control over your room bookings & resource scheduling. You can find out more about MIDAS at http://mid.as/
MIDAS - Web Based Room & Resource Scheduling Software - User ManualMIDAS
This is the complete User Manual for MIDAS (http://mid.as/), a complete web based scheduling solution giving you complete control over your room bookings & resource scheduling. You can find out more about MIDAS at http://mid.as/
Complete documentation for the optional Digital Signage addon for MIDAS Web Based Room & Resource Scheduling Software. Find out more at http://mid.as/signage
MIDAS - Web Based Room & Resource Scheduling Software - User ManualMIDAS
This is the complete User Manual for MIDAS (http://mid.as/), a complete web based scheduling solution giving you complete control over your room bookings & resource scheduling. You can find out more about MIDAS at http://mid.as/
MIDAS (http://mid.as/) is a complete web based scheduling solution that gives you complete control over your room bookings & resource scheduling. This presentation outlines some of the features of the software. You can find out more at http://mid.as/
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
2. API Documentation
Table of Contents
Table of Contents ....................................................................................................................................................1
API Usage Guide..........................................................................................................................................................2
Overview.................................................................................................................................................................2
Installing the API .....................................................................................................................................................2
Making API calls ......................................................................................................................................................2
API responses..........................................................................................................................................................2
API Settings .............................................................................................................................................................3
Global Parameters...............................................................................................................................................4
Scope ......................................................................................................................................................................4
API Command Reference ............................................................................................................................................5
get_activity .............................................................................................................................................................5
get_availability ........................................................................................................................................................6
get_bookings ..........................................................................................................................................................7
get_client ................................................................................................................................................................9
get_consumable_levels ......................................................................................................................................... 10
get_invoice ........................................................................................................................................................... 11
get_invoices .......................................................................................................................................................... 12
get_messages ....................................................................................................................................................... 13
get_reminders ...................................................................................................................................................... 14
get_resource_availability ...................................................................................................................................... 14
get_setting ............................................................................................................................................................ 15
get_user................................................................................................................................................................ 15
get_venue ............................................................................................................................................................. 18
http://md.as/signage
get_venues_in_group ........................................................................................................................................... 20
get_venues_in_use ............................................................................................................................................... 21
get_watches.......................................................................................................................................................... 21
util_from_epoch ................................................................................................................................................... 22
util_to_epoch........................................................................................................................................................ 22
Appendix A – Activity Codes ...................................................................................................................................... 23
Appendix B – Setting Names ..................................................................................................................................... 24
Appendix C – Error Handling ..................................................................................................................................... 27
Code Samples ........................................................................................................................................................... 28
jQuery ................................................................................................................................................................... 28
Perl ....................................................................................................................................................................... 28
PHP ....................................................................................................................................................................... 28
Release Notes ........................................................................................................................................................... 29
http://mid.as/api
Page |1
3. API Documentation
API Usage Guide
Overview
The MIDAS API (Application Programming Interface) allows developers to interface directly with MIDAS from their
own applications.
Installing the API
The MIDAS API is an optional add-on for MIDAS v4.03 (or later), that can be purchased along with MIDAS, or added
at a later stage.
•
•
To purchase MIDAS and the API addon, please visit: http://mid.as/purchase
To add the API addon to an existing MIDAS installation, please go to MIDAS Admin Options → Manage
Addons → Available Addons → API Access
Once purchased, the API will become available for one-click installation via MIDAS Admin Options → Manage Addons
→ Addons Ready To Install → API Access
Once installed, various API settings are available via MIDAS Admin Options → Manage Addons → Installed Addons →
API Access
Making API calls
To make an API call, your application will need to perform an HTTP POST request to http://your_midas_url/api.pl.
Each request must include as a minimum your unique API key, an API command and all associated required
parameters for the API command issued. Please refer to the API Command Reference for details of available API
commands and associated parameters.
API responses
The MIDAS API returns JSON (JavaScript Object Notation) formatted data. Example responses are shown throughout
the API Command Reference. Error responses are also returned in JSON format and denoted by the term “error”.
http://mid.as/api
Page |2
4. API Documentation
API Settings
A number of API settings are available via MIDAS Admin Options → Manage Add-ons → API Access.
Setting
Enable API access?
Description
Allows enabling/disabling of API access. If disabled, any API calls will return:
{"error":"not enabled"}
Enable logging?
(Only available to self-hosted editions of MIDAS) When enabled, API calls will be logged to
api_log.dat (located in your MIDAS directory). The format of each line of this file is as
follows:
timestamp
Allowed Referrers
IP_address
api_command
This can be used to log/monitor calls to your API. It should only be enabled for debugging
purposes as it will reduce performance of the API, and may lead to a large api_log.dat file if
left enabled for a long of time.
Allows calls to your API to be restricted from certain domains/IP addresses. If left blank,
API calls will be allowed from any referrer. For calls from banned referrers, the API will
return:
{"error":"referrer not allowed"}
http://mid.as/api
Page |3
5. API Documentation
Global Parameters
The following parameters are required with each API call
Required Parameters
key
Possible Values
<API key>
action
<API command>
Description
Your unique API key. For security, the API will only respond to your
unique key. Calls made to the API without a key, or with an invalid key,
will not be processed. You should not make your API key
visible/available to anyone.
The action you wish the API to perform. See the API Command
Reference for a full list of supported commands.
The following parameters are optional, but may also be included with any API call
Optional Parameters
l
Possible Values
<language>
id
<database>
epoch
1|0
Description
By default, the API will use the “en-US” language pack where applicable.
To optionally use a different language pack, its corresponding language
code can be specified.
MIDAS allows you to optionally run multiple, independent, databases
from the same interface. If multiple databases have been setup in your
MIDAS, API calls will be made to whichever database is currently set as
the "default". To make API calls to one of the other defined databases,
its corresponding database code can be passed in the "id" attribute.
To locate the correct database code to pass with the "id" parameter,
open up your midasglobal.dat settings file in a standard text editor and
locate the <database> section within this file. This section contains
details of all defined databases for your MIDAS. The database "code" to
use is the current value of the "r" parameter for the relevant database.
For API calls that require start/end times, setting “epoch” to “1” will
accept start/end values in epoch seconds (instead of the default
YYYYMMDDHHMM format)
For API calls that return a date/time, setting “epoch” to “1” will return
date/time values in epoch seconds (instead of following the current
MIDAS date/time format settings, for instance, “DD/MM/YYYY @
HH:MM”
What are epoch seconds?
Epoch seconds are the number of seconds that have elapsed since midnight Coordinated Universal Time (UTC) on 1
January 1970
Scope
Version 1.xx of the MIDAS API is a read-only API - which should be sufficient for the majority of applications, allowing
you to use existing data from MIDAS in your own applications. It is envisaged that Version 2 of the API will go on to
provide a bi-directional interface to MIDAS.
http://mid.as/api
Page |4
6. API Documentation
API Command Reference
get_activity
Returns all MIDAS user activity between two times. The optional “user” parameter can be used to limit the activity
returned to a specific user, and the optional “filter” parameter can be used to limit the results to a specific activity.
Required Parameters
start
Possible Values
Valid date and time
(Format: YYYYMMDDHHMM)
Valid date and time
(Format: YYYYMMDDHHMM)
Description
Start time
Optional Parameters
user
Possible Values
<User’s Full Name> | SYSTEM
filter
<activity code>
Description
Limit the returned activity to a specific user identified by
<User’s Full Name> or the keyword “SYSTEM”. “SYSTEM”
will return activity not assigned to a specific user (for
example database backups, new booking requests
received, etc). If this parameter is omitted, activity for all
users (including “SYSTEM”) will be returned
Limit the returned activity to a specific action. See
Appendix A for a list of activity codes
end
End time
Example Response
{
{
"time":"5/4/2013 @ 07:53",
"user":"SYSTEM",
"action":"BKUP"
},
{
"time":"5/4/2013 @ 07:26",
"user":"Joe Bloggs",
"action":"ADD",
"data1":"12/5/2013 @ 22:00"
}
}
Variables Returned
time
user
action
data1
data2
data3
data4
http://mid.as/api
Date/Time activity occurred
User who generated activity
Code of action performed. See Appendix A for a list of activity codes
Returns additional data specific to action. See Appendix A for more information
Returns additional data specific to action. See Appendix A for more information
Returns additional data specific to action. See Appendix A for more information
Returns additional data specific to action. See Appendix A for more information
Page |5
7. API Documentation
get_availability
Checks whether a venue is available (free) for booking between two times
Required Parameters
start
Description
Start time
venue
Possible Values
Valid date and time
(Format: YYYYMMDDHHMM)
Valid date and time
(Format: YYYYMMDDHHMM)
<Venue name>
Optional Parameters
attendees
Possible Values
<number>
Description
The number of desired attendees. If specified, availability
will also be dependent upon whether the number of
attendees if less than the venue’s capacity and/or
maximum global occupancy levels.
end
End time
Venue
Example Response
{
"availability":"1"
}
Variables Returned
availability
http://mid.as/api
Current Venue Availability
A value of “1” means the venue is “available” on the dates/times specified
A value of “Unavailable” means the venue is not available on the dates/times
specified (i.e. clashes with an existing booking)
Any other values also mean “Unavailable” but will specify the reason for the
unavailability i.e. “This will exceed your maximum occupancy level”, or “Venue
unavailable from 6/5/2103”
Page |6
8. API Documentation
get_bookings
Returns all bookings between two dates/times
Required Parameters
start
end
Optional Parameters
venue
type
status
Possible Values
Valid date and time
(Format: YYYYMMDDHHMM)
Valid date and time
(Format: YYYYMMDDHHMM)
Description
Start time
Possible Values
<Venue name>
<Booking Type>
all | request | deleted
Description
Limits returned bookings to a specific venue
Limits returned bookings to a specific booking type
Controls which bookings are returned. “request” will only
return booking requests. “deleted” will only return
deleted bookings. “all” will return all bookings (including
deleted bookings and booking requests). If this parameter
is omitted only confirmed bookings will be returned
End time
Example Response
{
{
"id":"222",
"start":"5/4/2013 @ 13:00",
"end":"5/4/2013 @ 14:00",
"venue":"Room 3",
"client":"Some User (Some Org)",
"type":"Community",
"attendees":"30",
"notes":"",
"resources":[
{
"resource":"Laptop",
"qty":"2"
},
{
"resource":"Projector",
"qty":"1"
}
],
"invoice":"MIDAS00001",
"history":[
{
"action":"Added",
"date":"2/4/2013 @ 08:23",
"user":"Joe Bloggs"
},
{
"action":"Modified",
"date":"2/4/2013 @ 16:52",
"user":"Joe Bloggs"
}
]
},
http://mid.as/api
Page |7
9. API Documentation
{
"id":"223",
"start":"5/4/2013 @ 14:15",
"end":"5/4/2013 @ 16:30",
"venue":"Room 4",
"client":"Some User (Some Org)",
"type":"Community",
"attendees":"40",
"notes":"",
"resources":[],
"invoice":"MIDAS00001",
"history":[
{
"action":"Added",
"date":"2/4/2013 @ 08:25",
"user":"Joe Bloggs"
}
]
}
}
Variables Returned
id
start
end
venue
client
type
attendees
notes
resources
resource
qty
invoice
history
action
date
user
custom fields
http://mid.as/api
Internal Booking ID
Start date/time of booking
End date/time of booking
Venue
Client the booking is for
Booking Type
Estimated number of people attending booking
Booking Notes
Resources assigned to booking
The name of the resource
The quantity of the resource
Invoice in which the booking appears
Booking history
The action performed. This will be one of the following:
“Booking Request Received”, “Added”, “Modified”, “Deleted”, “Restored”, or
“Invoice Created”
The date/time the action occurred
The user who performed the action
Any custom booking fields setup in your MIDAS will also be returned
Page |8
10. API Documentation
get_client
Returns client records
Required Parameters
(at least 1 required)
client
org
email
Possible Values
Description
<Client name>
<Organization name>
<email address>
Client name
Organization name
Email address
Optional Parameters
match
Possible Values
exact | loose
Description
Allows specifying the closeness of the match.
If match is set “exact” and “client” is set to “Joe Bloggs”,
only clients with the name “Joe Bloggs” will be returned.
If match is set to “loose” and “email” is set to “@mid.as”,
any client with an “@mid.as” email address will be
returned.
If the match parameter is omitted only exact matches are
returned
Example Response
{
{
"name":"Joe Bloggs",
"organization":"MIDAS",
"email":"joe@mid.as",
"address":"PO Box 224,Cheadle,Cheshire.SK8 4AF",
"phone":"01234 567 890",
"fax":"01234 567 891",
"mobile":"07123456789",
"notes":"",
"added":"7/8/2012 @ 16:49"
}
}
Variables Returned
name
organization
email
address
phone
fax
mobile
notes
added
http://mid.as/api
Client’s name
Client’s organization
Client’s email address
Client’s postal address
Client’s telephone number
Client’s fax number
Client’s mobile (cell) number
Notes about the client
Date/time when client was added to MIDAS
Page |9
11. API Documentation
get_consumable_levels
Returns the current stock level of all consumable items
Required Parameters
This API command has no additional required parameters
Example Response
{
{
"consumable":"Flipchart Paper",
"qty_remaining":"23",
},
{
"consumable":"Permanent Marker Pens",
"qty_remaining":"156",
}
}
Variables Returned
consumable
qty_remaining
http://mid.as/api
The name of the consumable
The current stock level. If no stock quantity has been defined, qty_remaining will
return “Unlimited”
P a g e | 10
12. API Documentation
get_invoice
Retrieves a specific invoice
Required Parameters
invoice
Possible Values
<Invoice Reference>
Description
Invoice Reference
Example Response
{
"client":"MIDAS (MIDAS2)",
"date":"5/11/2012 @ 10:00",
"items":[
{
"description":"Room 1 (6/11/2012 @ 19:30 - 21:30)",
"qty":"2.00",
"rate":"23.50"
},
{
"description":"Room 2 (13/11/2012 @ 19:30 - 21:30)",
"qty":"2.00",
"rate":"23.50"
}
],
"total":"94.00",
"tax_rate":"20.00",
"tax_amount":"18.80",
"paid":"0.00",
"history":[
{
"action":"Created",
"date":"5/11/2012 @ 08:45",
"user":"MIDAS Administrator"
},
{
"action":"Modified",
"date":"5/11/2012 @ 09:42",
"user":"MIDAS Administrator"
},
{
"action":"Emailed",
"date":"5/11/2012 @ 10:00",
"user":"MIDAS Administrator"
}
]
}
Variables Returned
client
date
items
description
qty
rate
total
http://mid.as/api
Client
Invoice Date (or “Invoice Not Sent if invoice hasn’t been emailed/printed)
Invoice items
The item’s description
The item’s quantity
The item’s rate (charge)
Invoice total (ex tax)
P a g e | 11
13. API Documentation
Tax rate (percentage)
Tax amount
Amount paid
Invoice history
The action performed. This will be one of the following:
“Created”, “Modified”, “Printed”, “Emailed”, “Payment Received”, “Payment
Overdue”, “Paid In Full”
The date/time the action occurred
The user who performed the action
tax_rate
tax_amount
paid
history
action
date
user
get_invoices
Retrieves a list of invoices for a specific client
Required Parameters
(at least 1 required)
client
org
email
Possible Values
Description
<Client name>
<Organization name>
<email address>
Client name
Organization name
Email address
Example Response
{
"client":"Joe Bloggs (Bloggs Inc)",
"email":"joe@bloggsinc.com",
"invoices":"MIDAS0001,MIDAS0003,MIDAS0004"
}
Variables Returned
client
email
invoices
http://mid.as/api
Client/Organization
Client’s email address
A comma separated list of all invoices associated with the client
P a g e | 12
14. API Documentation
get_messages
Retrieves all current internal messages for a specific user
Required Parameters
(only 1 required)
email
user
Possible Values
Description
<user’s email>
<user’s name>
User’s email address
User’s name
Example Response
{
{
"message":"Hello World!",
"author":"Joe Bloggs",
"created","24/4/2013 @ 00:03",
"expires","26/4/2013 @ 00:00"
},
{
"message":"This is a test message",
"author":"Jane Doe",
"created","25/4/2013 @ 03:42",
"expires","29/4/2013 @ 12:30"
}
}
Variables Returned
message
author
created
expires
http://mid.as/api
Details of the watch
The user who created the message
Date/Time the message was created
Date/Time at which the message expires
P a g e | 13
15. API Documentation
get_reminders
Retrieves all current reminders for a specific user
Required Parameters
(only 1 required)
email
user
Possible Values
Description
<user’s email>
<user’s name>
User’s email address
User’s name
Example Response
{
{
"reminder":"Reminder: Room 3: 25/4/2013 @ 13:00 - 15:00 Booking for Joe Bloggs",
"expires":"25/4/2013 @ 15:00"
},
{
"reminder":"Reminder: Room 3: 26/4/2013 @ 14:00 - 16:30 Booking for Jane Doe",
"expires":"26/4/2013 @ 16:30"
}
}
Variables Returned
reminder
expires
Details of the reminder
Date/Time at which the reminder expires
get_resource_availability
Returns the quantity available of a specified resource between two dates/times
Required Parameters
start
end
resource
qty
Possible Values
Valid date and time
(Format: YYYYMMDDHHMM)
Valid date and time
(Format: YYYYMMDDHHMM)
<Resource name>
Number
Description
Start time
End time
Resource name
Quantity to check
Example Response
{
"available":"2"
}
Variables Returned
available
http://mid.as/api
Quantity of specified resources available during times specified
P a g e | 14
16. API Documentation
get_setting
Returns a current MIDAS setting
Required Parameters
setting
Possible Values
<setting name>
Description
Setting name. See Appendix B for available setting names
Example Response
{
"email_sendfrom":"midas@yourorganization.com"
}
Variables Returned
<setting>
The current value of the specified <setting>
get_user
Returns user information
Required Parameters
(at least 1 required)
user
email
Possible Values
Description
<name>
<email address>
User’s full name
User’s email address
Optional Parameters
match
Possible Values
exact | loose
Description
Allows specifying the closeness of the match.
If match is set “exact” and “user” is set to “Joe Bloggs”,
only users with the name “Joe Bloggs” will be returned.
If match is set to “loose” and “user” is set to “Joe”, any
user named “Joe” will be returned.
If the match parameter is omitted only exact matches are
returned
Example Response
{
{
"name":"Joe Bloggs",
"email":"joe@bloggs.com",
"added":"25/2/2013 @ 16:49",
"last_login":"23/4/2013 @ 20:51",
"last_password_change":"29/3/2013 @ 18:34",
"last_modified":"25/2/2013 @ 23:42",
"account_locked":"0",
"failed_login_attempts":"0",
"day_starts_at":"00",
"day_runs_for":"24",
"do_not_log_activity":"0"
"email_calendar_events":"1",
"email_messages":"0",
http://mid.as/api
P a g e | 15
17. API Documentation
"email_pending_notifications":"1",
"email_watch_notifications":"0",
"force_pw_change_at_login":"0",
"suppress_messages_popup":"0",
"venue_group_access":"Group A,Group B",
"permissions":[
{
"can_add_bookings":"1",
"can_add_clients":"1",
"can_add_day_notes":"1",
"can_add_historical_bookings":"0",
"can_add_out_of_hours_bookings":"0",
"can_change_password":"1",
"can_delete_bookings":"2",
"can_delete_clients":"1",
"can_email_clients":"1",
"can_evac":"1",
"can_invoice":"1",
"can_manage_booking_types":"1",
"can_manage_midas":"1",
"can_manage_resources":"1",
"can_manage_users":"1",
"can_manage_venues":"1",
"can_modify_bookings":"2",
"can_modify_clients":"",
"can_print":"1",
"can_process_requests":"1",
"can_restore_bookings":"1",
"can_use_mymessages":"1",
"can_view_activity_log":"1",
"can_view_clients":"2",
"can_view_statistics":"1"
}
]
}
}
Variables Returned
name
organization
added
last_login
last_password_change
last_modified
account_locked
failed_login_attempts
day_starts_at
day_runs_for
do_not_log_activity
http://mid.as/api
User’s name
User’s email address
Date/Time user was added to MIDAS
Date/Time user last successfully logged in
Date/Time user last changed their password
Date/Time user information was last modified
Indicates if the user has been suspended / locked out of MIDAS
The number of unsuccessful login attempt on this account since last
successful login
The hour (in 24-hour clock mode) the user’s booking grid is displayed
from
The number of hours the user’s booking grid displays
If “0” all user activity within MIDAS will be recorded in the Recent
Activity Log
If “1” user activity within MIDAS will appear in the Recent Activity Log,
except for logins/logouts
If “2” no user activity will be recorded in the Recent Activity Log
P a g e | 16
18. API Documentation
Indicates whether reminders should also be sent to user’s email as
calendar events
email_messages
Indicates whether messages are forwarded to user’s email
email_pending_notifications
Indicates whether new booking request notifications are forwarded to
user’s email
email_watch_notifications
Indicates whether watch notifications are forwarded to user’s email
force_pw_change_at_login
Indicates whether user is required to change their password upon next
login
suppress_messages_popup
Indicates whether the “My Messages” pop-up is suppressed (not
shown) after login
venue_group_access
Indicates which Venue Groups the user has access to in the Booking
Grid.
A value of “*” indicates user can view all Venue Groups
permissions
The various permissions associated with the user account. Most take a
value of either “1” meaning user has been granted a permission, “0”
meaning the user does not have a permission. Permissions with
additional possible values are indicated.
can_add_bookings
User can add bookings.
“0” indicates user may not make bookings
“1” indicates user may make bookings
“2” indicates user may only make booking requests
can_add_clients
User can add clients
can_add_day_notes
Use can add notes to calendar dates
can_add_historical_bookings
User can add bookings for dates occurring in the past
can_add_out_of_hours_bookings User can add bookings outside of a venue’s operating hours
can_change_password
User can change their password
can_delete_bookings
User can delete bookings
“0” indicates user cannot delete any bookings
“1” indicates user may delete only those bookings originally added by
them
“2” indicates user may delete any booking
can_delete_clients
User can delete clients
can_email_clients
User can email clients directly from MIDAS
can_evac
User can print Emergency Evacuation data
can_invoice
User can use invoicing
can_manage_booking_types
User can manage Booking Types
can_manage_midas
User can manage MIDAS
can_manage_resources
User can manage Resources
can_manage_users
User can manage Users & Permissions
can_manage_venues
User can manage Venues
can_modify_bookings
User can modify bookings
“0” indicates user cannot modify any bookings
“1” indicates user may modify only those bookings originally added by
them
“2” indicates user may modify any booking
can_modify_clients
User can modify clients
can_print
User can use print functions
can_process_requests
User can approve/reject pending booking requests
email_calendar_events
http://mid.as/api
P a g e | 17
19. API Documentation
can_restore_bookings
can_use_mymessages
can_view_activity_log
can_view_clients
can_view_statistics
User can restore previously deleted bookings
Use can use My Messages (Messages, Reminders, and Watches)
Use can access the Recent Activity log
User can view client information
“0” indicates user cannot view any client data
“1” indicates user can view client and organization names only
“2” indicates user can view full client info for any client
“3” indicates user can only view full client into for clients they’ve added
bookings for
Use can access Statistics
get_venue
Returns venue information
Required Parameters
venue
Possible Values
<Venue name>
Description
Venue name
Optional Parameters
match
Possible Values
exact | loose
Description
Allows specifying the closeness of the match.
If match is set “exact” and “venue” is set to “Meeting
Room”, only the venue with the name “Meeting Room”
will be returned.
If match is set to “loose” and “venue” is set to “Meeting
Room”, any venue containing the name “Meeting Room”,
such as “Meeting Room A”, “Meeting Room B”, etc will be
returned.
If the match parameter is omitted only exact matches are
returned
Example Response
{
{
"venue":"Room 1",
"capacity":"20",
"description":"A small meeting room",
"requestable":"1",
"rates":[
{
"day":"Mon",
"rate":"20.00",
"rate_type":"Hourly"
},
{
"day":"Tue",
"rate":"20.00",
"rate_type":"Hourly"
},
{
"day":"Wed",
"rate":"20.00",
http://mid.as/api
P a g e | 18
21. API Documentation
Variables Returned
venue
capacity
description
requestable
rates
day
rate
rate_type
operating_hours
day
closed
closed_from
closed_until
managers
Venue name
The maximum occupancy of the venue
The venue’s description
Whether the venue is available for public requesting
The room rate/hire charge for each day of the week
The day of the week
The room/rate hire charge amount
If “Hourly”, the rate is per-hour, if “Daily”, the rate is per-day
The times between which the venue is closed during each day of the week
The day of the week
A comma separated list of the times (24 hour format) the venue is closed
The date after which the venue is considered closed
The date until which the venue is considered closed
A comma separated listed of user who are “Managers” of the venue i.e. can approve
Booking Requests for the venue
get_venues_in_group
Returns a list of venues in a venue group
Required Parameters
group
Possible Values
<venue group>
Description
Name of a venue group
Example Response
{
"Group A":"Room 1,Room 2,Room3"
}
Variables Returned
<group name>
http://mid.as/api
Comma separated list of current venues in group
P a g e | 20
22. API Documentation
get_venues_in_use
Returns a list of all venues in use at the point in time when the API call is made. If optional start and end parameters
are supplied, returns a list of all venues in use between start and end parameters.
Optional Parameters
start
end
Possible Values
Valid date and time
(Format: YYYYMMDDHHMM)
Valid date and time
(Format: YYYYMMDDHHMM)
Description
Start time
End time
Example Response
{
"venues":"Room 1,Room 2,Room3"
}
Variables Returned
venues
Comma separated list of venues in use
get_watches
Retrieves all current watches for a specific user
Required Parameters
(only 1 required)
email
user
Possible Values
Description
<user’s email>
<user’s name>
User’s email address
User’s name
Example Response
{
{
"watch":"Booking Matching [Venue: Room 1] on 25/4/2013 @ 13:00 - 15:00 For Joe
Bloggs Added",
"expires":"25/4/2013 @ 15:00"
},
{
"watch":"Booking Matching [Venue: Room 4] on 25/4/2013 @ 14:00 - 16:30 For Jane
Doe Deleted",
"expires":"26/4/2013 @ 16:30"
}
}
Variables Returned
watch
expires
http://mid.as/api
Details of the watch
Date/Time at which the watch expires
P a g e | 21
23. API Documentation
util_from_epoch
Converts epoch seconds to a standard date/time format
Required Parameters
data
Possible Values
Epoch seconds
Description
Epoch seconds to convert
Optional Parameters
format
Possible Values
1|0
Description
If omitted (or “0”), the returned date/time string will be in
the format “YYYYMMDDHHMM”.
If “1”, the returned date/time string will reflect the
current time/date format settings in MIDAS, for instance,
“DD/MM/YYYY @ HH:MM”
Example Response
{
"response":"201305121008"
}
Variables Returned
response
The converted epoch time, returned in a date/time format specified by the “format”
parameter. If no “format” parameter specified, response is returned as
“YYYYMMDDHHMM”
util_to_epoch
Converts a date/time to epoch seconds
Required Parameters
data
Possible Values
Valid date and time
(Format: YYYYMMDDHHMM)
Description
Date/Time string to convert to epoch seconds
Example Response
{
"response":" 1357066800"
}
Variables Returned
response
http://mid.as/api
The converted date/time, returned as epoch seconds
P a g e | 22
24. API Documentation
Appendix A – Activity Codes
The following codes may be used in conjunction with the “get_activity” call
CODE
ADD
ADD2VG
ADDBT
ADDC
ADDI
ADDRES
ADDU
ADDV
ADDVG
BKUP
CANR
DELB
DELBT
DELC
DELI
DELRES
DELV
DELVG
EMS
EMSI
EXPB
EXPC
EXPIS
EXPR
GENI
IN
MBKUP
MOD
MODBT
MODC
MODI
MODRES
MODU
MODV
MREST
NEWR
OUT
PEED
PENA
PENR
PRNT
PRNTI
PWC
REMFVG
REMU
RENVG
REST
UPSI
Description
Data1
User added booking
User added venue to group
User added booking type
User added client
User created invoice
User added resource
User added User
User added venue
User added venue group
MIDAS backup (Automatic)
Booking request cancelled
User deleted booking
User deleted booking type
User deleted client
User deleted invoice
User Deleted Resource
User deleted venue
User deleted venue group
User sent email
User sent email invoice
User exported bookings
User exported clients
User exported invoice summaries
User exported resources
User generated invoice
User logged in
MIDAS backup (Manual)
User modified booking
User modified booking type
User modified client
User modified invoice
User Modified Resource
User modified User
User modified venue
User Restored a MIDAS backup
Booking request received
User logged out
User printed Emergency Evacuation Data
User approved booking
User rejected booking
User printed bookings
User printed invoice
User changed password
User removed venue from group
User deleted User
User renamed venue group
User restored booking
User updated invoice status
Date/Time
Venue
Type
Client
Invoice
Resource
Name
Venue
Venue Group
http://mid.as/api
Client
Date/Time
Type
Client
Invoice
Resource
Venue
Venue Group
Client
Client
Data2
Data3
Data4
New Type
New Color
Venue Group
Color
Organization
Email
Organization
Organization
Subject
Invoice
Invoice
Date/Time
Previous Type
Client
Invoice
Resource
Name
Venue
Date/Time
Client
Previous Color
Organization
Email
Organization
Date/Time
Date/Time
Print Title
Client
Client
Client
Venue
Name
Previous Venue Group
Date/Time
Invoice
Venue Group
Email
New Venue Group
Reason
Invoice
P a g e | 23
25. API Documentation
Appendix B – Setting Names
The following codes may be used in conjunction with the “get_setting” call
Setting
api_version
backup_email
backup_last
backup_persist
build_date
datetime_amsymbol
datetime_datefirst
datetime_dateformat
datetime_dtlink
datetime_gmtoffset
datetime_minterval
datetime_pmsymbol
datetime_startofweek
datetime_timeformat
datetime_timenow
datetime_timezone
datetime_ttlink
email_bcc
email_sendfrom
invoicing_counter
invoicing_createbydefault
invoicing_createifzero
invoicing_currencycode
invoicing_currencysymbol
invoicing_decimalsep
invoicing_google_account
invoicing_google_enabled
invoicing_includezero
invoicing_paypal_account
http://mid.as/api
Description
Current version of the MIDAS API
The email address that automated database backups
are sent to
The time of the last backup (epoch seconds)
The number of days to keep backups on server
Current MIDAS build date
The symbol denoting the first 12 hours of the day
(when running in 12 hour clock mode)
If "1" dates are shown before times, otherwise times
are shown before dates
The date format
The link symbol between date and time
The timezone's GMT offset
The granularity of minutes
The symbol denoting the first 12 hours of the day
(when running in 12 hour clock mode)
The day that should be considered the start of the
week (0 = Sunday, 1 = Monday, etc)
The time format
The current time (in epoch seconds)
The timezone
The link symbol between two times
The email address that outgoing email should be bcc'd
to
The email address that outgoing email should appear
sent from
The next invoice number to be generated
If "1" the "Create Invoice" option is checked when
adding bookings
If "1" invoices will be created even if the calculated
invoice total is zero. If "0" invoices will only be created
if their values are non-zero
The currency code
The currency symbol
The decimal separator
Your Google Wallet (formally Google Checkout) ID
If "1" online invoice payments are allowed via Google
Wallet
If "1" items will be included on invoices even if their
total value is zero. If "0" invoices will only include items
that have an associated cost
Your PayPal email address
Example value
1.02
backup@yourdomain.com
1365609454
7
1365608000
AM
1
DD/MM/YYYY
@
0
5
PM
1
HH:mm
1365696187
Europe/London
bcc@yourdomain.com
midas@yourdomain.com
4
0
1
USD
$
.
0000000000000000
1
1
paypal@yourdomain.com
P a g e | 24
26. API Documentation
If "1" online invoice payments are allowed via PayPal
If "1" clients are required to enter their email address
in order to view their invoice online
invoicing_prefix
The prefix that is added to all your invoice numbers
invoicing_rounding
If "1" invoice values are rounded up to the nearest
whole number 0
invoicing_silentdisc
If "1" booking type discounts are applied to invoices
without any indication. If "0" invoices will denote that
a discount has been applied
invoicing_tax
The default tax percentage to be added to invoices
invoicing_thousandsep
The thousand separator
occupancy_max
The maximum number of people allowed on your site
at any one time
occupancy_show
Show the occupancy level when adding/modifying
bookings
occupancy_warn
Warn if the number of people on site exceeds this
value
print_evactolerance
When printing Emergency Evacuation Data, this
number reflects how many minutes either side of the
current time the calculation of the number of people
on site should account for
print_sortby
The booking field to sort booking print outs by
print_sortdir
The sort order of print outs (0 = ascending, 1 =
descending)
search_maxresults
The maximum number of search results to return per
page
version
Current MIDAS version
view_autoclose_alerts
The number of seconds the "My Messages" pop-up
should display for, if enabled by users
view_autoclose_notes
The number of seconds after which any "day notes"
pop-ups should automatically close
view_changemonthcell
Allow users to choose what's displayed in the monthly
overview
view_cutoffdays
The number of days to keep temporary logs for
view_default
The default view in the Booking Grid
view_gridrowheight
The height (in pixels) of each row in the booking grid
view_gridvenuewidth
The width (in pixels) of the first column in the booking
grid
view_showonblocks
The booking field(s) to show on booking "blocks" in the
booking grid
view_showonmonthcell
The booking field to show on dates in the monthly
overview
view_showontools
The booking field(s) to show on tooltips when hovering
over booking "blocks" in the booking grid
view_updatefrequency
The number of seconds between successive
background data refreshes
view_viewsize
The number of days to show in the booking grid by
default
webrequest_alloweddomains A comma separated list of email domains from which
invoicing_paypal_enabled
invoicing_pay_require_email
http://mid.as/api
1
1
MIDAS
1
0
0
,
510
1
300
15
start
0
50
4.03
10
15
1
30
All
30
100
organisation
client
organisation
30
1
@yourdomain.com,
P a g e | 25
28. API Documentation
Appendix C – Error Handling
When making API calls, your applications should take into account possible errors that may be returned.
API errors will be returned in JSON format as follows:
Example Error Response
{"error":"error response"}
Error Response
"invalid api key"
"no matches found”
"not enabled"
"referrer not
allowed"
"required
parameter missing"
"unknown booking
type"
"unknown
command"
"unknown
resource"
"unknown setting"
"unknown user"
"unknown venue
group"
"unknown venue"
http://mid.as/api
Meaning
You have not supplied your API key in your call, or
the API key supplied is invalid
No data was returned for the API call. Try
broadening the search parameters
API access is not enabled at this time. API access can
be enabled from within MIDAS via MIDAS Admin
Options → Manage Addons → API Access → Enabled
The API call originates from a blocked domain/IP
address. Allowed domains/IP's may be specified
from within MIDAS via MIDAS Admin Options →
Manage Addons → API Access → Allowed Referrers
One or more parameters are required for the
particular call you're making is missing
Indicates that the specified booking type doesn't
exist
The API command you've specified was
unrecognized. Please check you're using a valid
command
Indicates that the specified resource doesn't exist
Indicates that the specified setting isn't recognized
Indicates that the specified user doesn't exist
Indicates that the specified venue group doesn't
exist
Indicates that the specified venue doesn't exist
Applies To
All
get_activity
get_bookings
get_client
get_consuable_levels
get_invoice
get_invoices
get_messages
get_reminders
get_user
get_venues_in_group
get_watches
All
All
All
get_bookings (when the type parameter
is specified)
All
get_resource_availability
get_setting
get_activity
get_messeges
get_reminders
get_watches
get_venues_in_group
get_availability
get_bookings (when the venue parameter
is specified)
get_venue
P a g e | 27
30. API Documentation
Release Notes
v1.02
18th February 2014
Added support for multiple databases
v1.01
7th October 2013
Added “get_venues_in_use” call
v1.00
1st June 2013
Initial API release
For the most up-to-date API documentation, please visit http://mid.as/api
http://mid.as/api
P a g e | 29