- Print
Article summary
Did you find this summary helpful?
Thank you for your feedback
Tulip API3.0
The Tulip API gives you programmatic access to your Tulip data.
Query Parameters
Some Tulip API endpoints take parameters specified in the URL query. In the Tulip API, the URL query is expected to be a list of key-value pairs, with pairs separated by &
, keys and values separated by =
, and keys and values being percent-encoded. Keys are parsed as strings, values must be present for each key, and values are parsed as JSON. Simple string values may be specified as-is instead of being JSON-encoded. A query parameter may be specified multiple times, but only the final value will be used. Examples (shown without percent encoding for readability):
a=1&b=true&c="hello"
would parse a parametera
as the number 1,b
as the booleantrue
, andc
as the stringhello
a=foo&b="foo"
would parse a parametera
as the stringfoo
andb
as the stringfoo
data={"points":[{"x":3,"y":4},{"x":2,"y":-9}]}
would parse a parameterdata
as an object with a single fieldpoints
containing an array with two elements: an object withx
as the number 3 andy
as the number 4, and an object withx
as the number 2 andy
as the number -9a=foo&a=bar
would parse a parametera
as the stringbar
Contact |
---|
Tulip Interfaces https://tulip.co/contact-us/ sales@tulip.co |
Servers |
---|
Templates Tulip API Server https://templates.tulip.co/api/v3 |
Terms of Service
Was this article helpful?