
Security News
Crates.io Implements Trusted Publishing Support
Crates.io adds Trusted Publishing support, enabling secure GitHub Actions-based crate releases without long-lived API tokens.
dyspatch-client
Advanced tools
_IntroductionThe_Dyspatch_API_is_based_on_the_REST_paradigm_and_features_resource_based_URLs_with_standard_HTTP_responsecodes_to_indicate_errors__We_use_standard_HTTP_authentication_and_request_verbs_and_all_responses_are_JSON_formatted_See_our__Implement
DyspatchClient - JavaScript client for dyspatch-client
The Dyspatch API is based on the REST paradigm, and features resource based URLs with standard HTTP response codes to indicate errors. We use standard HTTP authentication and request verbs, and all responses are JSON formatted. See our Implementation Guide for more details on how to implement Dyspatch.
Dyspatch provides API Clients for popular languages and web frameworks.
This SDK is automatically generated by the OpenAPI Generator project:
To publish the library as a npm, please follow the procedure in "Publishing npm packages".
Then install it via:
npm install dyspatch-client --save
Finally, you need to build the module:
npm run build
To use the library locally without publishing to a remote npm registry, first install the dependencies by changing into the directory containing package.json
(and this README). Let's call this JAVASCRIPT_CLIENT_DIR
. Then run:
npm install
Next, link it globally in npm with the following, also from JAVASCRIPT_CLIENT_DIR
:
npm link
To use the link you just defined in your project, switch to the directory you want to use your dyspatch-client from, and run:
npm link /path/to/<JAVASCRIPT_CLIENT_DIR>
Finally, you need to build the module:
npm run build
If the library is hosted at a git repository, e.g.https://github.com/getdyspatch/dyspatch-javascript then install it via:
npm install getdyspatch/dyspatch-javascript --save
The library also works in the browser environment via npm and browserify. After following
the above steps with Node.js and installing browserify with npm install -g browserify
,
perform the following (assuming main.js is your entry file):
browserify main.js > bundle.js
Then include bundle.js in the HTML pages.
Using Webpack you may encounter the following error: "Module not found: Error: Cannot resolve module", most certainly you should disable AMD loader. Add/merge the following section to your webpack config:
module: {
rules: [
{
parser: {
amd: false
}
}
]
}
Please follow the installation instruction and execute the following JS code:
var DyspatchClient = require('dyspatch-client');
var defaultClient = DyspatchClient.ApiClient.instance;
// Configure API key authorization: Bearer
var Bearer = defaultClient.authentications['Bearer'];
Bearer.apiKey = "YOUR API KEY"
// Uncomment the following line to set a prefix for the API key, e.g. "Token" (defaults to null)
//Bearer.apiKeyPrefix['Authorization'] = "Token"
var api = new DyspatchClient.DraftsApi()
var draftId = "draftId_example"; // {String} A draft ID
var languageId = "languageId_example"; // {String} A language ID (eg: en-US)
var accept = "accept_example"; // {String} A version of the API that should be used for the request. For example, to use version \"2020.11\", set the value to \"application/vnd.dyspatch.2020.11+json\"
api.deleteLocalization(draftId, languageId, accept).then(function() {
console.log('API called successfully.');
}, function(error) {
console.error(error);
});
All URIs are relative to https://api.dyspatch.io
Class | Method | HTTP request | Description |
---|---|---|---|
DyspatchClient.DraftsApi | deleteLocalization | DELETE /drafts/{draftId}/localizations/{languageId} | Remove a localization |
DyspatchClient.DraftsApi | getDraftById | GET /drafts/{draftId} | Get Draft by ID |
DyspatchClient.DraftsApi | getDraftLocalizationKeys | GET /drafts/{draftId}/localizationKeys | Get localization keys |
DyspatchClient.DraftsApi | getDrafts | GET /drafts | List Drafts |
DyspatchClient.DraftsApi | getLocalizationForDraft | GET /drafts/{draftId}/localizations | Get localizations on a draft |
DyspatchClient.DraftsApi | saveLocalization | PUT /drafts/{draftId}/localizations/{languageId} | Create or update a localization |
DyspatchClient.DraftsApi | setTranslation | PUT /drafts/{draftId}/localizations/{languageId}/translations | Set translations for language |
DyspatchClient.DraftsApi | submitDraftForApproval | POST /drafts/{draftId}/publishRequest | Submit the draft for approval |
DyspatchClient.LocalizationsApi | getDraftLocalizationById | GET /localizations/{localizationId}/drafts/{draftId} | Get Draft Localization Object by ID |
DyspatchClient.LocalizationsApi | getPublishedLocalizationById | GET /localizations/{localizationId} | Get Localization Object by ID |
DyspatchClient.TemplatesApi | getTemplateById | GET /templates/{templateId} | Get Template by ID |
DyspatchClient.TemplatesApi | getTemplates | GET /templates | List Templates |
FAQs
_IntroductionThe_Dyspatch_API_is_based_on_the_REST_paradigm_and_features_resource_based_URLs_with_standard_HTTP_responsecodes_to_indicate_errors__We_use_standard_HTTP_authentication_and_request_verbs_and_all_responses_are_JSON_formatted_See_our__Implement
The npm package dyspatch-client receives a total of 1 weekly downloads. As such, dyspatch-client popularity was classified as not popular.
We found that dyspatch-client demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Crates.io adds Trusted Publishing support, enabling secure GitHub Actions-based crate releases without long-lived API tokens.
Research
/Security News
Undocumented protestware found in 28 npm packages disrupts UI for Russian-language users visiting Russian and Belarusian domains.
Research
/Security News
North Korean threat actors deploy 67 malicious npm packages using the newly discovered XORIndex malware loader.