GET /api/v2/custom_objects/{custom_object_key}/records/search
Returns an array of custom object records that meet the search criteria
Pagination
- Cursor pagination only.
- Returns the records sorted by relevancy with page limits. Without a
sort
parameter, only the first 10,000 records are returned. With asort
parameter, all records are returned.
Allowed For
- Agents
Servers
- https://{subdomain}.{domain}.com
Path parameters
Name | Type | Required | Description |
---|---|---|---|
custom_object_key |
String | Yes |
The key of a custom object |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
query |
String | No |
The query parameter is used to search text-based fields for records that match specific query terms.
The query can be multiple words or numbers. Every record that matches the beginning of any word or number in the query string is returned. Fuzzy search is supported for the following text-based field types: : Text fields, Multi Line Text fields, and RegExp fields. For example, you might want to search for records related to Tesla vehicles: You can include multiple words or numbers in your search. For example: |
sort |
String | No |
One of |
pageafter |
String | No |
A pagination cursor that tells the endpoint which page to start on. It should be a |
pagebefore |
String | No |
A pagination cursor that tells the endpoint which page to start on. It should be a |
pagesize |
Integer | No |
Specifies how many records should be returned in the response. You can specify up to 100 records per page. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.