API parameters make developers efficient when working with Pipeliner API. API parameters may vary from endpoint to endpoint.
Query parameter Name
Turn offs validation on API requests
*.Create, *.Update, *.Delete
Expand related entity, to get immediate overview
Filter data from API
Filter operators for filtering data
Number of entities to return from beginning of the result set. Max: 100. Default: 30
Returns deleted data Default: False
Return only the "last" number of entities from result set. When used with first parameter, then it returns last M records from the first N records.
Loads only api_fields defined within this parameter. You can use multiple values separated via ',' colon. If not used, then all fields are returned. You can use dots '.' to specify load only fields in nested as well. Example:
Order by values. Use api_name of field to sort by ascending. Prefix api_name with '-' to descending sort. You can use multiple values separated via ',' colon Example:
Used in bulk updates/create, to rollback data that failed. 0 - rollback all, 1 - rollback only failed records.
Default:0 See Bulk Update and Create
Query parameter: validation-level
Helps when a developer doesn´t want to create data inside Pipeliner valid for some reason.
When the business has many required fields on the Entities, you might want to skip the validation of those fields and populate only fields that you actually need.
Validate each field on the entity. Without even specifying this parameter, this is the general behavior of API - all API requests are automatically validated
Validate only changed fields in the actual request
Allows to override readonly fields
Allows setting entity on the deleted relationship. Example: user, an account might be deleted
Example of Request
Using validation as query parameter. In this case example, the validation is skipped for options "4" and "16"
The Majority of Invalid entities in the application look normal, however, after updating the data the user will see the information about invalid data
(Before user update )This record skipped validation and it was created through API without required field "Primary Account name"
(After Update) User cannot save the record, because it is required. He needs to select Primary Account name
Expand related entity. Use api_names of related fields. You can use multiple values separated via ',' comma. If not used, the URI link will be returned instead. You can use '.' to expand nested entities as well.
Use the API name of the field in braces to filter by this field. To do the advanced filter, use with combination with filter-op parameter.
Filter-op stands for filter operator. Below is the list of operators. You can combine several operators with
eq - equals
ieq - case insensitive equals, e.g. "example" will match "Example" as well as "eXAmple"
contains - partial match, e.g. "xampl" will match "example"
starts - matches which starts with string, e.g. "exam" will match "example"
ends - matches which ends with string, e.g. "ample" will match "example"
icontains - same as contains, but case insensitive
istarts - same as starts, but case insensitive
iends - same as end, but case insensitive
null - lookup for null values
empty - lookup for empty values (e.g. string == "", or " ")
gt - greater than
gte - greater or equal than
lt - less than
lte - less or equal than