Support, training, and documentation
Many questions can be answered by reviewing our documentation and code library; however, here are some common questions.
- What formats does the Data API support?
- What formats does the WICK API support?
- Do the services support SSL?
- Are the services free?
- Is there a subscription service?
- Can I request a custom dataset?
- Can I create my own dataset?
- Are there restrictions using MySafeInfo?
- Do you provide sample source code?
- Can you help me with my code?
- What is JSONP?
- Does your service support CORS?
The Data API supports XML, JSON, CSV, and many other formats. Within each format, it is possible to customize the data. For more information see our documentation and examples.
The WICK API primarily uses JSON; however, WICK data is available to retrieve in other formats by leveraging the Data API.
Yes, all of our services support and require HTTPS
The Data API is provided free of charge (with limitations) and subscriptions are available for premium services.
The WICK API is provided free of charge (with limitations) and subscriptions are available for premium services.
Yes, we offer subscriptions for premium services.
If you can't find what you are looking for and would like to make a request for a custom dataset, please contact us.
The WICK API allows developers to create and manage their own databases, tables, and data. Login or register for more information.
Yes, there are restrictions. Please review our Terms and Conditions for more information.
We offer sample code for the most requested programming languages. Unfortunately we cannot offer all programming languages requested; however, if you need additional assistance, please contact us and we may be able to point you in the right direction.
We support developers when they are encountering issues connecting to the MySafeInfo services. We do not have the resources to support all requests; however, if you need help connecting a website or application to the MySafeInfo services and are not familiar with programming, please contact us and we may be able to point you in the right direction.
JSONP is "JSON with padding". JSONP allows web browsers to request data via JavaScript from a server in a different domain, something prohibited by typical web browsers because of the same origin policy. If you are consuming the service server-side, this likely will not apply to you; however, for client-side requests, JSONP allows you to consume the service via JavaScript and provide a callback function. See our examples for more information on calling the service.
Yes, we use CORS (cross-origin resource sharing) to allow our service to be widely accessible to our users. CORS can be used as an alternative to JSONP. While JSONP supports only the GET request method, CORS also supports other types of HTTP requests. Using CORS allows you to use JavaScript to make an XMLHttpRequest. CORS is supported by most modern web browsers. See our examples for more information on calling the service.