The ruby gem about NHR Device

That gem allow the developer to access Nibo's RESTful API resource.

Nice diff generates the tabular readable diff of two JSON or XML files. A file object reference to corresponding JSON or XML files needs to be passed along with the format type being expressed.

Nicepay Indonesia

utils for nicovideo

See more at https://nifi.apache.org/

A Rails extension for creating JSON hashes for Active Record classes

Nightingale brings the 'script-as-app' experience to Ruby. Write your UI in pure Ruby DSL, backed by Sinatra and React/Vite.

Ruby library for Nihaopay payment gateway API

Ruby library for accessing Nike+ data

NikeRb is a ruby wrapper for the Nike Developers API. Originally created for use with the Nike Fuelband API. Support for other devices may be added at a later date.

Ruby wrapper for the Nimble CRM Api.

Scale your Heroku Dynos to demand at http://nimblenodes.com

Client library and command-line tool to design and manage websites on the Nimbu platform.

A simple library for talking to the Ninja Blocks Platform.

A wrapper for the National Institute of Standards and Technology (NIST) Randomness Beacon 'cause sometimes you need to get a 512-bit full-entropy bit-string programmatically. You never know.

NitPicker is a command-line tool that uses AI to review your staged Git changes and provide constructive feedback

Api client for Bunchball's Nitro. http://www.bunchball.com/nitro/

Sarasty sister API Library

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `<` lower than - `>=` lower than or equal - `><` included in list, items should be separated by `|` - `!><` not included in list, items should be separated by `|` - `~` pattern matching, may include `%` (any characters) and `_` (one character) - `!~` pattern not matching, may include `%` (any characters) and `_` (one character)