Custom Connector
JSONBin.io Data Connector
Global
The JSONBin.io Data Connector is a cloud service for storing and managing JSON data via simple REST APIs. It simplifies prototyping, mock services, and lightweight database storage — delivering accurate, consistent results in JSON. Core endpoints create, retrieve, update, and delete JSON bins.
Overview
Integration Overview
This document provides a detailed guide for each integration point using the JSONBin.io Data Connector — four CRUD endpoints for JSON bins.
- Create Bin. Add a new JSON bin.
- Retrieve Bin. Fetch data from a specific JSON bin by ID.
- Update Bin. Replace the content of an existing JSON bin.
- Delete Bin. Remove a JSON bin by ID.
Documentation
Detailed Integration Documentation
Create a Bin
| Operation ID | createBin |
|---|---|
| Endpoint | POST /bin |
| Parameters | Required: X-Master-Key (header) — master key for authentication. Body: the JSON data to store. |
| Purpose | Creates a new JSON bin and stores the provided data. Returns the stored record plus metadata such as bin ID and creation timestamp. |
| Output | JSON object with the stored bin data and metadata. |
| Workflow example | Use to store application data, configuration settings, or mock datasets for testing and prototyping. |
Retrieve a Bin
| Operation ID | getBin |
|---|---|
| Endpoint | GET /bin/{bin_id} |
| Parameters | Required: bin_id (path) — ID of the bin to retrieve; X-Master-Key (header). |
| Purpose | Retrieves the content of a specific JSON bin, including the record and version information. |
| Output | JSON object with the bin content and version details. |
| Workflow example | Fetch stored data for display, reporting, or downstream processing. |
Update a Bin
| Operation ID | updateBin |
|---|---|
| Endpoint | PUT /bin/{bin_id} |
| Parameters | Required: bin_id (path) — ID of the bin to update; X-Master-Key (header). Body: the replacement JSON. |
| Purpose | Replaces the content of an existing JSON bin and updates version metadata. |
| Output | JSON object reflecting the updated bin content and version metadata. |
| Workflow example | Modify stored JSON data for applications, testing, or configuration updates. |
Delete a Bin
| Operation ID | deleteBin |
|---|---|
| Endpoint | DELETE /bin/{bin_id} |
| Parameters | Required: bin_id (path) — ID of the bin to delete; X-Master-Key (header). |
| Purpose | Deletes a specific JSON bin from the database. |
| Output | Confirmation of deletion and metadata of the removed bin. |
| Workflow example | Remove old or obsolete records, reset mock databases, or clean up test data. |
Example Workflow: JSON Data Integration
| Create bin | Add a new JSON record for storage or testing. |
|---|---|
| Retrieve bin | Fetch stored data for display or processing. |
| Update bin | Modify the stored JSON data as needed. |
| Delete bin | Remove the bin when no longer required. |
Support
For technical support, contact custom-connectors-support@isolutions.sa.