TracCloud: API: Difference between revisions
From Redrock Wiki
No edit summary |
No edit summary |
||
| Line 11: | Line 11: | ||
<hr> | <hr> | ||
<!--------------------------------------- Sending requests ---------------------------------------> | <!--------------------------------------- Sending requests ---------------------------------------> | ||
<!--<div | <!--<div class='collapsible'>Sending Requests</div><div class="mw-collapsible mw-collapsed">--> | ||
===Sending Requests=== | |||
Our API endpoint is: https://traccloud.go-redrock.com/CAMPUSCODE/app/webhook.php <br> | Our API endpoint is: https://traccloud.go-redrock.com/CAMPUSCODE/app/webhook.php <br> | ||
| Line 28: | Line 28: | ||
<hr> | <hr> | ||
<!--------------------------------------- Updating Records ---------------------------------------> | <!--------------------------------------- Updating Records ---------------------------------------> | ||
<div | <div class='collapsible'>Updating Records (Action: update, store, create)</div><div class="mw-collapsible mw-collapsed"> | ||
<br><br> | <br><br> | ||
pass a parameter named "data" in the following format:<br> | pass a parameter named "data" in the following format:<br> | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
data={"action": "update", "APIKey": "YOUR_API_KEY", "KeyID": 1910, "table": "Students", "Last_Name": "Halsteader"} | data={"action": "update", "APIKey": "YOUR_API_KEY", "KeyID": 1910, "table": "Students", "Last_Name": "Halsteader"} | ||
</syntaxhighlight><br> | </syntaxhighlight><br> | ||
The response should be: | The response should be: | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
{"status":"success","message":"data Students record updated #1910","data":{"Sequence":1910}} | {"status":"success","message":"data Students record updated #1910","data":{"Sequence":1910}} | ||
</syntaxhighlight><br> | </syntaxhighlight><br> | ||
Example curl command. | Example curl command. | ||
<syntaxhighlight lang="bash | <syntaxhighlight lang="bash" > | ||
curl -d 'data={ | curl -d 'data={ | ||
"action": "update", | "action": "update", | ||
| Line 73: | Line 73: | ||
<hr> | <hr> | ||
<!--------------------------------------- Query ---------------------------------------> | <!--------------------------------------- Query ---------------------------------------> | ||
<div | <div class='collapsible'>Retrieving Records (Action: query)</div><div class="mw-collapsible mw-collapsed"> | ||
<br><br> | <br><br> | ||
The next API action is “query”, which can be used to retrieve fields from records. Here's an example that finds 20 students who's ID is greater than 1. | The next API action is “query”, which can be used to retrieve fields from records. Here's an example that finds 20 students who's ID is greater than 1. | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
curl -d 'data={ | curl -d 'data={ | ||
"action": "query", | "action": "query", | ||
| Line 98: | Line 98: | ||
This query will return the following. | This query will return the following. | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
{"status":"success","message":"data queried","data": | {"status":"success","message":"data queried","data": | ||
[{"Sequence":1901,"First_Name":"Jackson","Last_Name":"Gomez-Lopez"}, | [{"Sequence":1901,"First_Name":"Jackson","Last_Name":"Gomez-Lopez"}, | ||
| Line 162: | Line 162: | ||
</div> | </div> | ||
<hr> | <hr> | ||
<div | <div class='collapsible'>Query Options</div><div class="mw-collapsible mw-collapsed"> | ||
<br><br> | <br><br> | ||
| Line 169: | Line 169: | ||
<b>fields</b> | Search for specific values, using additional operators if needed. | <b>fields</b> | Search for specific values, using additional operators if needed. | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
"query": { | "query": { | ||
"fields": [{ | "fields": [{ | ||
| Line 180: | Line 180: | ||
<b>orfields</b> | Search for records that match any of the listed criteria. This can include an unlimited number of fields. | <b>orfields</b> | Search for records that match any of the listed criteria. This can include an unlimited number of fields. | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
"query": { | "query": { | ||
"orfields": [ | "orfields": [ | ||
| Line 204: | Line 204: | ||
<b>andfields</b> | Search for records that match all of the listed criteria. This can include an unlimited number of fields. | <b>andfields</b> | Search for records that match all of the listed criteria. This can include an unlimited number of fields. | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
"query": { | "query": { | ||
"andfields": [ | "andfields": [ | ||
| Line 227: | Line 227: | ||
<b>or</b> | Used to combine 2 (and only 2) instances of andfields/orfields. Records are returned if either criteria is met. | <b>or</b> | Used to combine 2 (and only 2) instances of andfields/orfields. Records are returned if either criteria is met. | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
"or": [ | "or": [ | ||
{ | { | ||
| Line 263: | Line 263: | ||
<b>and</b> | Used to combine 2 (and only 2) instances of andfields/orfields. Records are returned if both criteria are met. | <b>and</b> | Used to combine 2 (and only 2) instances of andfields/orfields. Records are returned if both criteria are met. | ||
<syntaxhighlight lang="json | <syntaxhighlight lang="json" > | ||
"query": { | "query": { | ||
"and": [ | "and": [ | ||
Latest revision as of 18:08, 7 April 2026
This section of our technical documentation covers TracCloud's v1 API support. For further assistance, reach out to us using the "Support" tab at the top of the page.
Sending Requests
Our API endpoint is: https://traccloud.go-redrock.com/CAMPUSCODE/app/webhook.php
Replace 'CAMPUSCODE' with your campus code, or replace traccloud.go-redrock.com/CAMPUSCODE with your custom URL if applicable.
For testing purposes, you can send the request from a browser's network tab like this.
That same request with curl looks like this. The rest of this article will use curl. Most of the examples will include line breaks for readability, it will work either way.
pass a parameter named "data" in the following format:
data={"action": "update", "APIKey": "YOUR_API_KEY", "KeyID": 1910, "table": "Students", "Last_Name": "Halsteader"}
The response should be:
{"status":"success","message":"data Students record updated #1910","data":{"Sequence":1910}}
Example curl command.
curl -d 'data={
"action": "update",
"APIKey": "YOUR_API_KEY",
"KeyID": 1931,
"table": "Students",
"Last_Name": "Smith"
}' https://traccloud.go-redrock.com/demo/app/webhook.php
Available fields and their options:
- action
- update will update an existing record, if you try updating when the record does not exist, it will return an error.
- store will update records, or create records if a record doesn't exist.
- create will create the currently non-existent record. If you try creating when the KeyID already exists, it will return an error.
- APIKey
- Your API key.
- Your API key.
- KeyID
- Provide the sequence number of the record being modified.
- Provide the sequence number of the record being modified.
- table
- Provide the table of the record being modified (Students, Registrations, etc).
- Provide the table of the record being modified (Students, Registrations, etc).
- [field]
- Provide the field you want to modify (e.g., Last_Name) as well as the value you want to set it to.
- Provide the field you want to modify (e.g., Last_Name) as well as the value you want to set it to.
The next API action is “query”, which can be used to retrieve fields from records. Here's an example that finds 20 students who's ID is greater than 1.
curl -d 'data={
"action": "query",
"from": "students",
"page": 1,
"page_recs": 20,
"APIKey": "YOUR_API_KEY",
"fields": ["Sequence", "First_Name", "Last_Name"],
"order": "first_name ASC",
"query": {
"fields": [{
"field": "Sequence",
"value": "1",
"op": ">"
}]
}
}' https://traccloud.go-redrock.com/demo/app/webhook.php
This query will return the following.
{"status":"success","message":"data queried","data":
[{"Sequence":1901,"First_Name":"Jackson","Last_Name":"Gomez-Lopez"},
{"Sequence":1910,"First_Name":"Angi","Last_Name":"Halsteader"},
{"Sequence":1911,"First_Name":"Ou00edhare","Last_Name":"Wallace"},
{"Sequence":1912,"First_Name":"Joe","Last_Name":"BarraganIII"},
{"Sequence":1913,"First_Name":"Lori","Last_Name":"Train"},
{"Sequence":1914,"First_Name":"John","Last_Name":"Cunningham"},
{"Sequence":1915,"First_Name":"Jaime","Last_Name":"Tsosie"},
{"Sequence":1916,"First_Name":"David","Last_Name":"Perry"},
{"Sequence":1917,"First_Name":"Luis","Last_Name":"Frias"},
{"Sequence":1918,"First_Name":"Freida","Last_Name":"Miller"},
{"Sequence":1919,"First_Name":"Andre","Last_Name":"Davis"},
{"Sequence":1920,"First_Name":"Alyssa","Last_Name":"Gumeringer"},
{"Sequence":1921,"First_Name":"Nils","Last_Name":"Christianson"},
{"Sequence":1922,"First_Name":"Jeanne","Last_Name":"Patterson"},
{"Sequence":1923,"First_Name":"Rachelle","Last_Name":"Rodriguez"},
{"Sequence":1924,"First_Name":"Damian","Last_Name":"Garcia"},
{"Sequence":1926,"First_Name":"Brandi","Last_Name":"Clee"},
{"Sequence":1927,"First_Name":"Edward","Last_Name":"Ireland"},
{"Sequence":1928,"First_Name":"Nicole","Last_Name":"Love-Cleasby"},
{"Sequence":1929,"First_Name":"Liam","Last_Name":"Howlett"}]}
- Action
- Should be "Query", otherwise review the previous section of this article.
- Should be "Query", otherwise review the previous section of this article.
- from
- The table you wish to retrieve data from (Students, Visits, etc).
- The table you wish to retrieve data from (Students, Visits, etc).
- page
- The page number to get records from, similar to pages on listings. This attribute allows you to write a program that continues hitting the server 1 page at a time getting the number of records in page_recs at a time. The programmer would pass 1 as page the first time, get the results and process, then pass 2 as page, etc, until the number of records is less than the amount in page_recs.
- The page number to get records from, similar to pages on listings. This attribute allows you to write a program that continues hitting the server 1 page at a time getting the number of records in page_recs at a time. The programmer would pass 1 as page the first time, get the results and process, then pass 2 as page, etc, until the number of records is less than the amount in page_recs.
- page_recs (Optional, seems to default to 20)
- The quantity of records to return.
- The quantity of records to return.
- APIKey
- Your API key.
- Your API key.
- fields
- The fields you want to display from the records you're retrieving. Twig tags can be used. Center.Name, etc. Custom fields would be formatted like "Students.CustomData->>``$.cf_123``" with 123 being the sequence number of the custom field.
- The fields you want to display from the records you're retrieving. Twig tags can be used. Center.Name, etc. Custom fields would be formatted like "Students.CustomData->>``$.cf_123``" with 123 being the sequence number of the custom field.
- order
- How data is sorted. Choose a field and sort ascending (ASC) or descending (DESC).
- How data is sorted. Choose a field and sort ascending (ASC) or descending (DESC).
- Query
- Query type
- Detailed further into this article.
- field
- Choose the field you want to search by.
- value
- The value you want to search by.
- op (use | for "or")
- = - Equals.
- != - Not.
- > - Greater than.
- < - Less than.
- <= - Less than or equal to.
- >= - Greater than or equal to.
- LIKE - Similar to, use % as a wildcard.
- NOT LIKE - Similar to, use % as a wildcard.
The examples below only include the "Query" portion of the data for brevity. These can be copied into the example curl command from earlier in this section.
fields | Search for specific values, using additional operators if needed.
"query": {
"fields": [{
"field": "ID",
"value": "1933",
"op": "="
}]
}
orfields | Search for records that match any of the listed criteria. This can include an unlimited number of fields.
"query": {
"orfields": [
{
"field": "First_Name",
"value": "%",
"op": "LIKE"
},
{
"field": "Last_Name",
"value": "%e%|%i%|%son",
"op": "LIKE"
},
{
"field": "Major",
"value": "Biology",
"op": "!="
}
]
}
andfields | Search for records that match all of the listed criteria. This can include an unlimited number of fields.
"query": {
"andfields": [
{
"field": "First_Name",
"value": "Rob",
"op": "="
},
{
"field": "Last_Name",
"value": "S%",
"op": "LIKE"
},
{
"field": "Major",
"value": "Biology",
"op": "="
}
]
}
or | Used to combine 2 (and only 2) instances of andfields/orfields. Records are returned if either criteria is met.
"or": [
{
"andfields": [
{
"field": "Sequence",
"value": "1",
"op": ">"
},
{
"field": "Sequence",
"value": "1000000",
"op": "<"
}
]
},
{
"orfields": [
{
"field": "First_Name",
"value": "%",
"op": "LIKE"
},
{
"field": "Last_Name",
"value": "%e%|%i%|%son",
"op": "LIKE"
}
]
}
]
}
and | Used to combine 2 (and only 2) instances of andfields/orfields. Records are returned if both criteria are met.
"query": {
"and": [
{
"andfields": [
{
"field": "Sequence",
"value": "1",
"op": ">"
},
{
"field": "Sequence",
"value": "1000000",
"op": "<"
}
]
},
{
"orfields": [
{
"field": "TimeIn",
"value": "{{\"now\"|date_modify(\"-7 days\")|date(\"Y-m-d H:i:s\")}}",
"op": ">"
},
{
"field": "Last_Name",
"value": "%e%|%i%|%son",
"op": "LIKE"
}
]
}
]
}
TracCloud Table List
Click here to view a list of TracCloud tables and fields accessible via the API.

