JavaScript API
Blackbeard includes smart defaults and simple options and settings to make it easy for you to configure and customize your Portal.
But for developers who want more fine-grained control and customization, it also provides a robust JavaScript API that you can use to extend functionality with your own scripts.
All of Blackbeard's JavaScript APIs are namespaced under the `m$` global variable.
## `loadJS()`
Load a JavaScript file asynchronously. Adapted from [loadJS by Filament Group](https://github.com/filamentgroup/loadJS/).
Pass in the file source as an argument, and an optional callback function to run after load. If the file already exists (for example, on subsequent Ajax page loads), the callback will run instantly.
If the file needs to be reexecuted on page loads, you can force the file to redownload by passing in the `reload` argument as `true`.
```js
/**
* @param {String} src URL of script to load.
* @param {Function} callback Callback to run on completion.
* @return {String} The script URL.
*/
m$.loadJS(src, callback, reload);
// Example
m$.loadJS('/files/myscript.js');
// With a callback
m$.loadJS('/files/myscript.js', function () {
myScript.init();
});
// For redownload
m$.loadJS('/files/myscript.js', null, true);
```
`m$.loadJS()` can also be used for dependency management by calling it again as a callback after a file loads.
```js
m$.loadJS('/files/myscript.js', function () {
m$.loadJS('/files/anotherscript.js');
});
```
## `loadCSS()`
Load a CSS file asynchronously. Adapted from [loadCSS() by Filament Group](https://github.com/filamentgroup/loadCSS).
Pass in the URL to the CSS file as an argument. If you want to load it before a specific file in the DOM for cascading purposes, or have a specific media type, you can optionally pass those in as arguments.
*__Note:__ Because this file loads asynchronously, the browser may not load it for several seconds, results in a flash of unstyled content until it does. You may prefer to [load your stylesheets synchronously instead](/docs/read/customizing_your_portal/extras/Loading_Additional_Stylesheets).*
```js
/**
* @param {String} href The URL for your CSS file
* @param {Node} before Element to use as a reference for injecting the [optional]
* @param {String} media Stylesheet media type [optional, defaults to 'all']
*/
m$.loadCSS(href, before, media);
// Example
m$.loadCSS('/files/mystyles.css');
```
## `onloadCSS()`
Detect when a CSS file is loaded and run a callback. Adapted from [onloadCSS() by Filament Group](https://github.com/filamentgroup/loadCSS).
Pass in the stylesheet to detect as the first argument, and the callback as the second. Works in conjunction with `m$.loadCSS()`.
```js
/**
* @param {Node} ss The stylesheet
* @param {Function} callback The callback to run
*/
m$.onloadCSS(ss, callback);
// Example
var css = m$.loadCSS('/files/mystyles.css');
m$.onloadCSS(css, function () {
console.log('My CSS loaded!');
});
```
## `extend()`
Merge two or more JavaScript objects together. By default, runs a shallow merge. To do a deep merge, pass in `true` as the first argument.
```js
/**
* @param {Boolean} deep If true, do a deep (or recursive) merge [optional]
* @param {Object} objects The objects to merge together
* @returns {Object} Merged values of defaults and options
*/
m$.extend(object1, object2, ...);
// Example objects
var object1 = {
apple: 0,
banana: { weight: 52, price: 100 },
cherry: 97
};
var object2 = {
banana: { price: 200 },
durian: 100
};
var object3 = {
apple: 'yum',
pie: 3.214,
applePie: true
};
// Create a new object by combining two or more objects
var shallowMerge = extend(object1, object2, object3);
var deepMerge = extend(true, object1, object2, object3);
```
## `sanitizeClass()`
Sanitize a string for use as a class or ID. Removes spaces and other invalid characters.
Pass in the string to use as an argument, and optionally, a prefix to apply before it.
```js
/**
* @param {String} id The string to convert into a class
* @param {String} prefix A prefix to use before the class [optional]
*/
m$.sanitizeClass(id, prefix);
// Example
var id = m$.sanitizeClass('Can you TUr34 this into an id?'); // returns "can-you-tur34-this-into-an-id-"
// With prefix
var id = m$.sanitizeClass('Can you TUr34 this into an id?', 'docs-pages'); // returns "docs-pages-can-you-tur34-this-into-an-id-"
```
## `inject()`
Inject HTML elements into the ``.
Pass in the type of element as the first argument, and an object of attributes as the second. The key is attribute name, and the value is it's value.
```js
/**
* @param {String} type The HTML element type
* @param {Object} atts The attributes and values for the element
*/
m$.inject(type, atts);
// Example
// Note: This specific example done already by the Portal if you portalOptions.responsive is `true` (the default).
m$.inject('meta', {
name: 'viewport',
content: 'width=device-width, initial-scale=1.0'
});
```
## `resetOptions()`
Reset the global `portalOptions` variable.
This wipes out any existing preset values, and is useful if you're attempting to re-render the Portal with an entirely different set of options.
```js
m$.resetOptions();
```
## `setOptions()`
Merge user options into Portal settings.
This runs automatically when the Portal first initializes. If you update any `portalOptions` after the Portal loads, you can use this to update settings for subsequent renders.
```js
/**
* @param {Object} options User options to merge into defaults
*/
m$.setOptions(options);
// Example
portalOptions.logo = '';
m$.setOptions(portalOptions);
```
## `emitEvent()`
Emit a custom event. This is a custom wrapper around the browser-native [CustomEvent API](https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/CustomEvent).
Pass in your event name to simply emit an event. If you'd like to include custom event details, optionally pass in an object with the `details` key. You can also specify an element to emit the event on. By default, it runs on the `window`.
```js
/**
* @param {String} eventName The name of the event to emit
* @param {Object} options Options for the event
* @param {Node} elem The element to dispatch the event on [optional - defaults to window]
*/
m$.emitEvent(eventName, options, elem);
// Example
m$.emitEvent('myCustomEvent');
// Listening for an event
window.addEventListener('myCustomEvent', function () {
console.log('My custom event ran!');
}, false);
// With Details
m$.emitEvent('anotherCustomEvent', {
details: {
something: 'a value',
another: true,
answer: 42
}
});
// Accessing details in the event listener
window.addEventListener('myCustomEvent', function (event) {
console.log(event.details);
var something = event.details.something;
var another = event.details.another;
var answerToTheLifeTheUniverseAndEverything = event.details.answer;
}, false);
```
## `click()`
Simulate a browser click event. Pass in the clicked element as an argument.
```js
/**
* @param {Element} elem the element to simulate a click on
*/
var click(elem);
// Example
var button = document.querySelector('#my-button');
click(button);
```
## `fixLocation()`
Jump to anchor or adjust focus when rendering is complete.
This is done automatically after rendering is complete, but if you inject content or manually update the URL with a hash value, you can run `m$.fixLocation()` to set focus on the correct element.
```js
m$.fixLocation();
```
## `renderPortal()`
Re-render the Portal. If render was triggered by an Ajax event that may require new files to be downloaded, or existing ones to be redownloaded or rerun, pass in `true` as an argument.
```js
/**
* @param {Boolean} ajax If true, the page is being loaded via Ajax
*/
m$.renderPortal(ajax);
// Example
m$.renderPortal();
// Example that triggers file downloads
m$.renderPortal(true);
```
## `convertMarkdown()`
Convert markdown into HTML. This is handled automatically for you on custom pages, documentation, and blog posts, but you can convert any other markdown content to HTML by passing in the content.
```js
var content = '## My Awesome Heading';
m$.convertMarkdown(content);
//
My Awesome Heading
``` ## `atomic.ajax()` To help you make XHR requests more easily, the [Atomic Ajax/HTTP plugin](https://github.com/cferdinandi/atomic) comes prebundled. Pass in the requested URL, and optionally, the request type. Defaults to `GET`. The `success`, `error`, and `always` callbacks run when the request is successful, when it fails, and either way, respectively. They accept the `responseText` (`data`) and full response (`xhr`) as arguments. All three callbacks are optional. ```js // A GET request atomic.ajax({ url: '/endpoint.com' }) .success(function (data, xhr) { console.log(data); // xhr.responseText console.log(xhr); // full response }) .error(function (data, xhr) { console.log(data); // xhr.responseText console.log(xhr); // full response }) .always(function (data, xhr) { console.log(data); // xhr.responseText console.log(xhr); // full response }); // A POST request atomic.ajax({ type: 'POST', url: '/endpoint.com' }); ``` JSONP requests do not accept the callback functions. You must instead setup a global callback function and pass in the function name a string to the `callback` option. Atomic will pass the returned data into your callback as an argument (in the example below, `data`). ```js var myCallback(data) { console.log(data); // full response }; // A JSONP request atomic.ajax({ type: 'JSONP', url: '/endpoint.com', callback: 'myCallback' }); ``` **Options & Settings** ```js atomic.ajax({ type: 'GET', // {String} the request type url: null, // {String} the endpoint for your request data: {}, // {Object|Array|String} data to be sent to the server callback: null, // {String} The name of a global callback function (for use with JSONP) headers: { // {Object} Adds headers to your request: request.setRequestHeader(key, value) 'Content-type': 'application/x-www-form-urlencoded' }, responseType: 'text', // {String} the response type (https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/responseType) withCredentials: false // {Boolean} If true, send credentials with request (https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest/withCredentials) }); ```Docs Navigation
- API Documentation Portal
- IO Docs Definition
- Mashery API Documentation
- Mashery 3.0 API Guide
- Mashery 2.0 API Guide
- OAuth Supporting Methods
- Examples
- JSON RPC
- Authentication
- API Objects
- Fetching Objects
- Query Language
- Creating Objects
- Updating Objects
- Validating Fields
- Deleting Objects
- Applications
- General Object Methods
- Members
- Packages
- Plans
- Package Keys
- Keys
- Developer Classes
- Services
- Roles
- Mashery 2.0 Reporting API Guide
- Event Trigger API
- Differences between Roles and Portal Access Groups
- Managing a Portal Access Group Using Mashery V2 or V3 API
- Mashery Reporting Event Post API Guide
- Tips and Tricks
- Your Portal
- API Traffic Manager
- I/O Docs WSDL requirements