Frequently Asked Questions

Many questions can be answered by looking at our documentation and examples; however, here are some other commonaly asked questions.

Quick Links

What formats are supported by the Data API?

The Data API supports XML, JSON, JSONP, CSV and HTML.

What formats are supported by the WICK API?

The WICK API uses JSON for POST data. The responses returned will be JSON (default) or XML depending on the Content-Type header.

Do the services support SSL?

Yes, the services can be requested via HTTP or HTTPS.

Are the services free?

Public datasets are free and can be requested without registering.
Basic datasets are also free but require you to register.
Premium datasets require you to register and purchase a subscription.
The Data API is provided free of charge (with some limitations), but subscriptions are available for premium services.
The WICK API is provided free of charge (with some limitations), but subscriptions are available for premium services.
The Converter API is provided free of charge.

Is there a subscription service?

Yes, we offer subscriptions for premium services.

Can I request a custom dataset?

If you can't find what you are looking for and would like to make a request for a custom dataset, please contact us.

Can I create my own dataset?

The WICK API allows developers to create and manage their own databases, tables, and data. Login or register for more information.

Are there limits to how I can use the services and the data?

Yes, there are restrictions. Please review our Terms and Conditions for more information.

Do you provide sample code for using the services?

We try to offer sample code for the most requested programming languages. Unfortunately we cannot offer all programming languages requested. If you need sample code in a different programming language than what is available, please contact us and we may be able to point you in the right direction, or provide custom development (at an additional fee).

Can you help me connect my website to your services?

We support developers when they are encountering specific 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, or provide custom development (at an additional fee).

What is JSONP?

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.

Does your service support Cross-origin resource sharing (CORS)?

Yes, we use CORS 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.

mysafeinfo.com