The QuintaDB REST API is designed to unlock the potential of the data stored within your QuintaDB database. Using this API you can achieve more than currently offered by the default QuintaDB UI. This is how we give you ability to do with your data everything you need and in the way you need. You can create your own scripts, desktop and mobile applications for different platforms like iPhone/Android and many more. And QuintaDB will be a place where you store, share and manage your data.
Also, QuintaDB has own application on the Zapier service.
General information about API calls
All calls should contain REST API key, which could be found in menu "API" at the top right of the page. Result are returned in JSON or XML, depending on your request. We`ll show a table with a result for each call. The URL will be shown in this way /apps.json, it means that you should call https://QuintaDB.com/apps.json in your application. Please notice that all calls should use https and you have to validate servers SSL certificate.
require 'open-uri'
require 'openssl'
require 'net/http'
require 'json'
def call_mth(url, format, method, params={})
uri = URI.parse(url)
# Creating proper call with Method: GET/POST/PUT/DELETE
req = case method
when "get"
Net::HTTP::Get.new(uri.path)
when "post"
Net::HTTP::Post.new(uri.path)
when "put"
Net::HTTP::Put.new(uri.path)
when "delete"
Net::HTTP::Delete.new(uri.path)
end
# Convert the parameters into JSON/XML and set the content type as application/json or application/xmlNotice the XML format for parameters, the root element is api_call_params
req.body = case format
when "xml"
"<?xml version=\"1.0\" encoding=\"UTF-8\"?>
<api_call_params>
#{params.collect{|key, value| "<#{key}>#{value}"}.join("")}
</api_call_params>"
when "json"
JSON.generate(params)
else
"no"
end
# Setting content type
req["Content-Type"] = "application/#{format}"
https = Net::HTTP.new(uri.host, uri.port)
# All calls via HTTPS and verifying SSL certificates
https.use_ssl = (uri.scheme == 'https')
https.verify_mode = (OpenSSL::SSL::VERIFY_PEER)
# Making request
https.start do |htt|
htt.request(req)
end
end
# Make sure to set your own API_KEY here
params = {
:page => 1,
:rest_api_key => "API_KEY"
}
response = call_mth "https://quintadb.ru/apps.json", "json", "get", params
# Response will be in response.body
puts response.body
Database
Such database attributes can be accessible via REST API.
Attribute
Description
id
Unique database identifier. You'll need this to access this database forms and records
name
Name
created_at
Time when database was created
updated_at
Time when database was last updated (changed records or forms)
dtypes_count
Number of entries in database
entities_count
Number of tables in database
properties_count
Number of columns in database
complex_app?
Is it a complex app, i.e. the app where data caching enabled. Returns true or false
complex_app_with_fresh_data?
Is it a complex app and the data cache is fresh. Returns true or false
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ID
You have to know your form identifier in order to fetch form information. You can find ID using Fetch All Forms call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities.json to /apps/aOWO_dVXHdHie1WeGFE8k2/entities.jso
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ID
You have to know your form identifier in order to fetch form information. You can find ID using Fetch All Forms call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities.json to /apps/aOWO_dVXHdHie1WeGFE8k2/entities.jso
Format
URL
Method
Request body
Response
JSON
/apps/APP_ID/entities/ID.json
PUT
{"rest_api_key":"API_KEY", "name":"New form name"}
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ID
You have to know your database identifier. You can find APP_ID using Fetch All Forms call. Once you know it, you'll need to add this APP_ID to URL in the link below, i.e. change /apps/APP_ID/entities.json to /apps/aOWO_dVXHdHie1WeGFE8k2/entities.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ENTITY_ID
You have to know your form identifier in order to fetch form information. You can find ID using Fetch All Forms call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities.json to /apps/aOWO_dVXHdHie1WeGFE8k2/entities.jso
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ENTITY_ID
You have to know your form identifier in order to fetch form information. You can find ID using Fetch All Forms call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities.json to /apps/aOWO_dVXHdHie1WeGFE8k2/entities.jso
ID
You have to know your field identifier in order to update field settings. You can find ID using Fetch All Form Fields call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties/ID.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties/asdasddVXHdHie1WeGFE8k2.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ENTITY_ID
You have to know your form identifier in order to fetch form information. You can find ID using Fetch All Forms call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities.json to /apps/aOWO_dVXHdHie1WeGFE8k2/entities.jso
ID
You have to know your field identifier in order to update field settings. You can find ID using Fetch All Form Fields call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties/ID.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties/asdasddVXHdHie1WeGFE8k2.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ENTITY_ID
You have to know your field's form identifier in order to update field settings. You can find ENTITY_ID using Fetch All Forms call. Once you know it, you'll need to add this ENTITY_ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties.json
ID
You have to know your field identifier in order to update field settings. You can find ID using Fetch All Form Fields call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties/ID.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties/asdasddVXHdHie1WeGFE8k2.json
Field type name. Can by one of: string, text, integer, float, select, radio button, check box,
date, dob, datetime, file, image, boolean, language, states, table, country, time_zone, note,
divider, formula, autoincrement, login, password
APP_ID
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ENTITY_ID
You have to know your field's form identifier in order to update field settings. You can find ENTITY_ID using Fetch All Forms call. Once you know it, you'll need to add this ENTITY_ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties.json
Format
URL
Method
Request body
Response
JSON
/apps/APP_ID/entities/ENTITY_ID/properties.json
POST
{"rest_api_key":"API_KEY", name: "Field name 1", type_name: "string"}
You have to know your field's form identifier in order to update field settings. You can find ENTITY_ID using Fetch All Forms call. Once you know it, you'll need to add this ENTITY_ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties.json
ID
You have to know your field identifier in order to update field settings. You can find ID using Fetch All Form Fields call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties/ID.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties/asdasddVXHdHie1WeGFE8k2.json
view
You have to know your report id in order to fetch records. (Optional)
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ENTITY_ID
You have to know your form identifier in order to fetch form information. You can find ID using Fetch All Forms call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities.json to /apps/aOWO_dVXHdHie1WeGFE8k2/entities.jso
page
Records page number. From 1 to Table Records count/per_page.
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ID
You have to know your record identifier. You can find ID using Fetch All Records call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/dtypes/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2/dtypes/asd987asdasd97asd.json
If you using jQuery, Ruby or another programming language then, please, use 'values' parameter to send encoding parameters. However, if your framework doesn't allow this you can send record values as JSON string, but in this case specify your parameter name as 'json_values'. And your JSON values string will looks like this: "{"aNW4nkW5bdUjldO8oKuSku":"2", "aMW4HKWR9bnOoGWQbpWQS4":"aaa"}"
subforms_values / subforms_json_values
To create or update subforms, in the same way, use 'subforms_values' or 'json_subforms_values'. With a format below: "{property1_id: {entity_id: subform1_id, subform1_record1_id: {subform1_field1_id: "2", subform1_field2_id: "aaa"}, subform1_record2_id: {subform1_field1_id: "3", subform1_field2_id: "bb"}}, property2_id: {entity_id: subform2_id, subform2_record1_id: {subform2_field1_id: "4", subform2_field2_id: "bb"}, subform2_record2_id: {subform2_field1_id: "5", subform2_field2_id: "dd"}}}" .
Where property1_id and property2_id - this is Fields ID's with a Subform type in the main table. subform1_id, subform2_id - Forms ID's, which was set in property1_id and property2_id settings. subform1_record1_id и subform1_record2_id - this is new or existent subform records ID's. subform1_field1_id, subform1_field2_id - fields ID's in the form subform1_id. subform2_field1_id, subform2_field2_id - fields ID's in the form subform2_id.
All ID's - it's a 22 characters URL-save base64 code, you can get them from other API calls or create for new subform records.
APP_ID
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ID
You have to know your record identifier. You can find ID using Fetch All Records call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/dtypes/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2/dtypes/asd987asdasd97asd.json
Update data cell - you can update record cell by passing record id, field id and new cell value
Request parameter
Description
rest_api_key
your API key
val
New cell value
DTYPE_ID
You have to know your record identifier. You can find ID using Fetch All Records call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/dtypes/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2/dtypes/asd987asdasd97asd.json
PROPERTY_ID
You have to know your field identifier in order to update field settings. You can find ID using Fetch All Form Fields call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties/ID.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties/asdasddVXHdHie1WeGFE8k2.json
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ID
You have to know your record identifier. You can find ID using Fetch All Records call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/dtypes/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2/dtypes/asd987asdasd97asd.json
If you using jQuery, Ruby or another programming language then, please, use 'values' parameter to send encoding parameters. However, if your framework doesn't allow this you can send record values as JSON string, but in this case specify your parameter name as 'json_values'. And your JSON values string will looks like this: "{"aNW4nkW5bdUjldO8oKuSku":"2", "aMW4HKWR9bnOoGWQbpWQS4":"aaa"}"
subforms_values / subforms_json_values
To create or update subforms, in the same way, use 'subforms_values' or 'json_subforms_values'. With a format below: "{property1_id: {entity_id: subform1_id, subform1_record1_id: {subform1_field1_id: "2", subform1_field2_id: "aaa"}, subform1_record2_id: {subform1_field1_id: "3", subform1_field2_id: "bb"}}, property2_id: {entity_id: subform2_id, subform2_record1_id: {subform2_field1_id: "4", subform2_field2_id: "bb"}, subform2_record2_id: {subform2_field1_id: "5", subform2_field2_id: "dd"}}}" .
Where property1_id and property2_id - this is Fields ID's with a Subform type in the main table. subform1_id, subform2_id - Forms ID's, which was set in property1_id and property2_id settings. subform1_record1_id и subform1_record2_id - this is new or existent subform records ID's. subform1_field1_id, subform1_field2_id - fields ID's in the form subform1_id. subform2_field1_id, subform2_field2_id - fields ID's in the form subform2_id.
All ID's - it's a 22 characters URL-save base64 code, you can get them from other API calls or create for new subform records.
ID
You have to generate 22 characters long URL-safe base64 UUID (Universally Unique IDentifier). For example, in Ruby. Then you'll need to pass this identifiers to 'values' hash. I.e. :values => {'id' => ID}, change to :values => {'id' => '22adadVXHdHie1WeGFE8k2'}
APP_ID
You have to know your database identifier in order to fetch database information. You can find ID using Fetch All Databases call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2.json
ENTITY_ID
You have to know your field's form identifier in order to update field settings. You can find ENTITY_ID using Fetch All Forms call. Once you know it, you'll need to add this ENTITY_ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties.json
In order to update link between records your have to pass separate hash into CREATE or UPDATE record call.
curl -H 'Content-Type: application/json' -X PUT -d '{"rel":{REL_ID:RECORD_ID}}' "https://quintadb.com/apps/APP_ID/dtypes/CURRENT_RECORD_ID.json?rest_api_key=API_KEY"
This hash should be like 'rel' => {rel_id => RECORD_ID} or 'rel' => {rel_id => [RECORD_ID, RECORD_ID2]} if you have many-to-many relationship. Where RECORD_ID it's a record's ID with which you want to link current record. Please, see below how to get rel_id.
Request parameter
Description
rest_api_key
your API key
ENTITY_ID
You have to know your field's form identifier in order to update field settings. You can find ENTITY_ID using Fetch All Forms call. Once you know it, you'll need to add this ENTITY_ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties.json
PROPERTY_ID
You have to know your field identifier in order to update field settings. You can find ID using Fetch All Form Fields call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties/ID.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties/asdasddVXHdHie1WeGFE8k2.json
In order to download record files you have to fetch record values first and then you'll be able to download file using the link like this https://quintadb.com/images/data/PROPERTY_ID/RECORD_ID/FILE_NAME, where FILE_NAME - file name, which you can get from record values hash, which looks likeу PROPERTY_ID => VALUE, RECORD_ID - record ID, PROPERTY_ID - field ID.
In order to upload a file into a record you have to make a POST request to the upload_file API method with multipart/form-data content type header and only after that you have to create or update your record. So the record ID should be generated before the calls. And also you'll have to generate the Multipart header, please, follow the Ruby example with MultipartPost class below. In example you'll learn how to upload the file into the subform too.
require 'open-uri'
require 'openssl'
require 'net/http'
require 'json'
require 'securerandom'
#MultipartPost
class MultipartPost
BOUNDARY = "-----------RubyMultipartPost"
EOL = "\r\n"
def initialize uri, &block
@params = Array.new
@uri = URI.parse uri
instance_eval &block if block
end
def params_part key, value
@params << multipart_text(key, value)
end
def files_part key, filename, mime_type, content
@params << multipart_file(key, filename, mime_type, content)
end
def request_body
body = @params.map{|p| "--#{BOUNDARY}#{EOL}" << p}.join ""
body << "#{EOL}--#{BOUNDARY}--#{EOL}"
end
def run
https = Net::HTTP.new @uri.host, @uri.port
https.use_ssl = true
https.verify_mode = (OpenSSL::SSL::VERIFY_PEER)
request = Net::HTTP::Post.new @uri.request_uri
request.body = request_body
request.set_content_type "multipart/form-data", {"boundary" => BOUNDARY}
res = https.request request
res.body
end
private
def multipart_text key, value
content = "Content-Disposition: form-data; name=\"#{key}\"" <<
EOL <<
EOL <<
"#{value}" << EOL
end
def multipart_file key, filename, mime_type, content
content = "Content-Disposition: form-data; name=\"#{key}\"; filename=\"#{filename}\"#{EOL}" <<
"Content-Type: #{mime_type}\r\n" <<
EOL <<
"#{content}" << EOL
end
end #MultipartPost
def call_quinta(url, format, method, params={})
uri = URI.parse(url)
req = case method
when "get"
Net::HTTP::Get.new(uri.path)
when "post"
Net::HTTP::Post.new(uri.path)
when "put"
Net::HTTP::Put.new(uri.path)
when "delete"
Net::HTTP::Delete.new(uri.path)
end
req.body = case format
when "json"
JSON.generate(params)
else
"no"
end
req["Content-Type"] = "application/#{format}"
https = Net::HTTP.new(uri.host, uri.port)
https.use_ssl = (uri.scheme == 'https')
https.verify_mode = (OpenSSL::SSL::VERIFY_PEER)
https.start do |htt|
htt.request(req)
end
end
dtype_id = SecureRandom.urlsafe_base64
app_id = "bsx8kgWR9jWOBdUftcRXf9"
entity_id = "arjadcLJzeWOi1WPddL8ol"
property_id = "bwW68wWP1cSikQqSkhl04I"
post_url = "https://localhost:3001/entities/#{app_id}/upload_file/#{property_id}.json?dtype_id=#{dtype_id}"
# Path to your file
file_path = "/home/igor/Pictures/Selection_001.png"
file = File.open file_path
# getting file's content type, i.e. 'image/png'
file_content_type = `file --b --mime-type '#{file_path}'`.strip
multi_part = MultipartPost.new post_url do
params_part "rest_api_key", rest_api_key
files_part "dtype[#{property_id}]", "Selection_001.png",
file_content_type, file.read
end
p multi_part.run
# And below is the example of how to upload the file to Subform
rest_api_key = "API_KEY"
subform_field_id = "dcL8kXB8npd5pdRmk7BCoR"
subform_file_field_id = "aVWR3cNtvdUikQn8o3yCo1"
subform_form_id = "cCcxjdWRXpWPTLWOjvWPfO"
subform_dtype_id = SecureRandom.urlsafe_base64
file_path = "/home/igor/Pictures/Selection_002.png"
file = File.open file_path
# getting file's content type, i.e. 'image/png'
file_content_type = `file --b --mime-type '#{file_path}'`.strip
post_url = "https://quintadb.com/entities/#{app_id}/upload_file/#{subform_file_field_id}.json?dtype_id=#{subform_dtype_id}"
# upload file into subform record
multi_part = MultipartPost.new post_url do
params_part "rest_api_key", rest_api_key
params_part "subform_field", subform_field_id
params_part "property_id", subform_file_field_id
params_part "subform_dtype_id", subform_dtype_id
files_part "subforms[#{subform_field_id}][#{subform_dtype_id}][#{subform_file_field_id}]", "Selection_002.png",
file_content_type, file.read
end
p multi_part.run
text_field_on_a_form = "agW6rGWQHiWPvdWPL0oCoj"
text_field_on_a_subform = "dcV8k6y8nhWP4JF0r6W5LI"
params = {
:page => 1,
:rest_api_key => rest_api_key,
values: {entity_id: entity_id, id: dtype_id, text_field_on_a_form => "Test"},
subforms: {subform_field_id => {entity_id: subform_form_id, subform_dtype_id => { text_field_on_a_subform => "Test2"}}}
}
response = call_quinta "https://quintadb.com/apps/#{app_id}/dtypes.json", "json", "post", params
puts response.body
Request parameter
Description
rest_api_key
your API key
APP_ID
App ID
property_id
You have to know your field identifier in order to update field settings. You can find ID using Fetch All Form Fields call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties/ID.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties/asdasddVXHdHie1WeGFE8k2.json
DTYPE_ID
You have to know your record identifier. You can find ID using Fetch All Records call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/dtypes/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2/dtypes/asd987asdasd97asd.json
You have to know your field identifier in order to update field settings. You can find ID using Fetch All Form Fields call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/entities/ENTITY_ID/properties/ID.json to /apps/qweWO_dVXHdHie1WeGFE8k2/entities/aOWO_dVXHdHie1WeGFE8k2/properties/asdasddVXHdHie1WeGFE8k2.json
DTYPE_ID
You have to know your record identifier. You can find ID using Fetch All Records call. Once you know it, you'll need to add this ID to URL in the link below, i.e. change /apps/APP_ID/dtypes/ID.json to /apps/aOWO_dVXHdHie1WeGFE8k2/dtypes/asd987asdasd97asd.json
It is well known that software development is very important these days. Having REST API for your software will increase your product popularity very much.This is a basic REST API and it should be enough to create great things. However, if you need anything else, more methods etc., please, feel free to contact us at any time. We look forward to hear from you!
QuintaDB.com uses cookies to provide necessary site functionality and improve your experience. By using our website, you agree to our cookie policy.
English
Español
Deutsch
Italiano
Polski
Nederlands
Português
Français
中文
日本語
हिन्दी
اللغة العربية
Русский
Українська
עִברִית
Ελληνικά
Türk
Latvietis
Log In