How to paginate and debug the APIs you build in Celigo

Walk through three new API Builder capabilities in Celigo: 1. Cursor-based pagination inside the APIs you publish 2. Step-by-step execution logs for every request 3. Regex-level schema validation you configure in the UI instead of hand-writing JSON. Here's what's new in API Builder: ▸ Pagination is native to the API you build — turn it on, and Celigo holds the cursor position for that lookup. ▸ The next call against that cursor resumes exactly where the prior request stopped, so a client can page through a large result set with no custom logic on either side. ▸ Execution logs come to API Builder — the same drill-down that already existed for flows, now for the APIs you expose. ▸ Open the request history for an API, pick a single request, and see the input and output at every step along the way. ▸ Requests, responses, and the time each individual step took are all visible per step, so a slow API has a specific place to look. ▸ JavaScript steps, filters, and handlebars expressions report their own inputs and outputs, which makes a bad transform traceable to the step that produced it. ▸ Advanced schema validation moves into the UI — set complex regex rules, like an input that has to be a valid email or a number that has to fall between 1 and 10, without writing JSON schema. CHAPTERS 00:00 API Builder pagination 00:32 Turning pagination on: Celigo holds the cursor, the next call resumes 00:55 Execution logs come to API Builder 01:08 Drilling into a single request: input and output at every step 01:19 Step timing, and tracing JavaScript, filters, and handlebars expressions 01:34 Advanced schema validation, now in the UI 01:47 Regex rules — email field types and number ranges, no JSON required 👉 Get a demo: https://www.celigo.com/request-a-demo/ #Celigo #APIBuilder #APIManagement #iPaaS #IntegrationPlatform #LowCode #APIDesign #APIPagination