Remove Schema API (Detach from the Collection)
Using the Remove Schema API, You could detach the Schema API from a specific Collection.
Note that once the Schema is detached from the Collection, any recorded created already or thereafter will not be validated again unless a Schema is added.
Root
https://api.jsonbin.io/v3
Route
/c/<COLLECTION_ID>/schemadoc/remove
Request Type
PUT
Request Headers
Below are the list of Accepted Request Headers if you are trying to Detach Schema Doc from a Collection.
Request Header | Value | Required |
---|---|---|
X-Master-Key | <API_KEY> | Yes |
X-Master-Key Required
X-Master-Key is nothing but your Core API Access Key. You will need this Key to access mostly any API end-point on JSONBin. You could find the key on the API Keys page.
Code Samples
curl -v\
-H "X-Master-key: <YOUR_API_KEY>" \
--request PUT \
https://api.jsonbin.io/v3/c/<COLLECTION_ID>/schemadoc/remove
Request Response
Success Status Code: 200
{
"collectionName": "<COLLECTION_NAME>",
"schemaDocId": "<DETACHED_SCHEMA_DOC_ID>",
"metadata": {
"id": "<COLLECTION_ID>",
"createdAt": "<DATE/TIME>"
}
}
Error Status Code: 400, 401, 403, 404
{
"message": "<Error Message>"
}
For more information on the error codes & errors you might possibly encounter, refer to the below section.
Error Reference
Invalid Collection Id provided
You'll encounter this error when you've passed incorrect Collection Id in the URL. Verify your Collection Id.