API reference
Last updated
Last updated
This endpoint returns the available record types, e.g. movie
, organization
, person
, etc.
name
Name of the record type.
label
Label of the record type.
creatable
The record type supports operation create
.
updatable
The record type supports operation update
.
readable
The record type supports operation read
.
searchable
The record type supports operation search
.
searchesIn
The list of parameters to search by in the records of the record type.
deletable
The record type suuports operation delete
.
triggerable
The record type supports firing webhooks when a new event is logged.
The record type records the date and time of the event.
This endpoint retrieves the JSON file of a record type. This JSON file contains the list of parameters available in the record type.
name
Name of the parameter.
label
Label of teh parameter.
mandatory
The parameter is mandatory.
readable
The parameter is returned in the response body when the record is fetched.
updatable
The parameter can be used to create/update a record.
refersTo
Name of the record type to which the parameter refers. Only available for the parameters of type ID.
type
JSON type of the parameter, e.g. text
, number
, array
.
nestedParameters
The parameters that are nested to the parameter.
The search records endpoint supports chained filters. The filter is sent in body of the request.
In addition to chained filters, records can be queried with single filters as well.
startsWith
endsWith
contains
equalsTo
Each user is granted access to 6 default movie records that cannot be updated or deleted.
Each user can create up to 14 movie records, resulting in 20 retrievable movie records.
The body
of the request contains the parameters available in the selected record type.
Only the records created by the user can be updated.
The body
of the request contains the parameters available in the selected record type.
Only the records created by the user can be deleted.
Each user is granted access to 1 default record that can't be deleted.
Each user can upload up to 1 file, resulting in 2 retrievable files.
The maximum size of a file one can upload to an upload session is 4 bytes. A single request within the upload session cannot exceed 1 byte. Example: If a file has 4 bytes, the file has to be split into 4 separate requests containing a block of data (bytes).
Open a slot for an upload session and save the file's name and the given file path where the file should be uploaded.
Only one slot can be open at a time. The slot can be open for max 1 minute. The session is dropped if the file upload is not finished by that time or if the upload session ends up with an error.
Upload the first block of data to an uplaod session.
Append more data to an upload session.
Finish the upload session by uploading the last block (byte) of the file's data.
The Make Academy API version 3 uses a digital signature which is generated using the secret key entered when creating a webhook and the body of the webhook’s request. This data is contained within the Signature
header.
The header contains the SHA algorithm used to generate the signature. To verify that the request originates from the App Academy API, you'll need to compute the HMAC 256 using your secret key and the body and compare it to the signature contained in the header. The successful matching of these values ensures that the webhook's source is the App Academy API.
You must set up the verification of the webhook.
When a webhook is attached, the verification payload is sent to the webhook. You must respond with the correct HTTP code:
200
for correct signature
400
for incorrect signature
For the 400 code, you must respond with the following response:
eventType
The type of event that fired the webhook. Available types: verification
, create
, update
.
data
The body of the .
Retrieves records. E.g. movies.
Type of the record to retrieve, e.g. movie.
The number of records to skip.
5
Access token for authorization.
Retrieves records. E.g. movies.
Type of the record to retrieve, e.g. movie.
The number of records to skip.
5
Access token for authorization.
Retrieves the record by its ID.
Type of the record to retrieve, e.g. movie.
ID of the record to work with.
Access token for authorization.
No body
Updates the record by its ID.
Type of the record to retrieve, e.g. movie.
ID of the record to work with.
Access token for authorization.
No body
Deletes the record by its ID.
Type of the record to retrieve, e.g. movie.
ID of the record to work with.
Access token for authorization.
No body
Retrieves the list of files or folders.
ID of the parent to work with.
Identification of the page to retrieve.
Access token for authorization.
Retrieves the list of files or folders.
ID of the parent to work with.
Identification of the page to retrieve.
Access token for authorization.
Creates a session ID for a file upload. Stores a file name and the final location of the file (full path to the folder is required).
Access token for authorization.
/8c6e22b7f1a0/e4673b2dff5e/1dca6a93fcf1
test.txt
Uploads the first block of data of a file.
Access token for authorization.
Session ID of the file upload.
application/octet-stream
application/octet-stream
raw(binary)
Uploads the other blocks of data (bytes) of a file, except the last block of data.
Access token for authorization.
Session ID of the file upload.
application/octet-stream
application/octet-stream
Identification of the byte's order in the file to upload.
raw(binary)
Uploads the last block of data a file and closes the session.
Access token for authorization.
Session ID of the file upload.
application/octet-stream
application/octet-stream
raw(binary)