We have moved to provide most of our v2 API documentation through our API Explorer.

The Explorer allows you to browse each available endpoint and its supported HTTP verbs, view the model properties, and even test out calls to the API right there in the API Explorer.
Simply put, it’s an integrator’s dream, making API integration projects that much easier to implement.

While the primary focus of the API Explorer is on JSON format requests and responses, there are some areas where you can specify an XML response type to get an idea of what the API requires and responds with on the XML as well.

The API Explorer is a dynamic, living document of our API that is generated directly from our API code. Thus, you can have confidence that what you see in the Explorer is exactly what is supported and available right now on the API.

Each available API endpoint is outlined in the API Explorer, with Model and Model Schema tabs/links that reveal the structures involved in requests and responses.

The Model tab/option on each endpoint, in particular, provides detailed descriptions of the various field definitions and structure relationships.

As a rule, the /search endpoints on the main API entities provide the most detail for that entity’s common structures.

e.g. https://eforms.mobileform.net/apiexplorer/apiexplorer#!/task/getv2tasksearch provides detailed descriptions of our Task entity and its related structures when you click the Model option under that endpoint. 

You can access the API Explorer right now on: 

To see which node you should access, look at your web browser’s URL when viewing the web portal.
It differs in the first part of the URL, i.e. secure or secure-eu or secure-au, and just use the corresponding link.

If you use a branded website, simply tack “/apiexplorer” onto your custom domain name to access it. E.g., if your whitelabel domain is set up on secure.mycustomdomain.com, then your API Explorer URL will be “https://eforms.mobileform.net/apiexplorer/apiexplorer”