Nordcraft provides several advanced API features to give you fine-grained control over your API connections. The following features are accessible through the Advanced tab in the API configuration panel.

By default, Nordcraft treats API responses with status codes 400 and above as errors. However, some APIs communicate errors differently, such as GraphQL APIs that return errors in the response body with a 200 status code.

Configure error definition

The Is error formula allows you to customize what constitutes an error:

1. 1

   Click the fx button to open the formula editor
2. 2

   Create a formula that evaluates to true when the response should be treated as an error

When a response is identified as an error:

• It becomes available in the error property of the API
• The On error event is triggered instead of On success
• The data property is set to null

This customization is essential for properly handling errors in APIs that don't follow standard HTTP error conventions.

Redirect rules allow your application to automatically navigate users to different pages based on API responses. This is useful in several scenarios:

• Redirecting unauthenticated users to a login page
• Handling language or region-specific content availability
• Managing moved or deprecated pages

Configure a redirect rule

To configure redirect rules:

1. 1

   In the Redirect rules section, click the + button to add a new rule
2. 2

   Name your rule descriptively
3. 3

   Create a formula that evaluates to a URL or path when API response conditions are met. It needs to evaluate to null if the conditions are not met.

Rules are evaluated in the order they appear, and the first matching rule determines the redirect destination.

Redirects can happen in two ways:

• Server-side: Occurs before any content is sent to the browser, preventing page flashes
• Client-side: Happens after the page has loaded in the browser

You can use the Is Server formula to create conditional logic based on where the code is executing. This allows different redirect behavior on the server versus in the browser.

The Server-side fetching toggle controls whether an API request executes during server-side rendering before sending the page to the browser.

Enable server-side fetching

When enabled:

• API data is included in the initial page HTML
• Content appears immediately when the page loads
• No additional client-side API call is needed unless parameters change

SSR-enabled API requests have some requirements:

• They must have Auto fetch enabled
• They must return text or JSON data (check the Content-Type header)

The Proxy request toggle determines whether API calls are routed through Nordcraft's edge network.

Enable proxying

When proxying is enabled (default), your API requests pass through Nordcraft's edge network, providing several capabilities:

• Authentication security: Enables the use of HTTP-only cookies for secure token storage
• CORS avoidance: Eliminates cross-origin resource sharing restrictions between domains
• Request enhancement: Allows Nordcraft to add headers or process responses

Proxying is particularly essential for authentication flows and third-party API integrations where direct browser-to-API connections would face security restrictions.

By default, Nordcraft automatically determines how to parse API responses based on the Content-Type header. In some cases, you may need to override this behavior.

Configure response parsing

The Parse as dropdown allows you to select from several parsing options:

• Auto: Uses the Content-Type header to determine the parsing method (default)
• Text: Parses the response as plain text
• JSON: Parses the response as a JSON object
• Event stream: Parses as server-sent events (SSE)
• JSON stream: Parses as a stream of JSON objects (see the NDJSON specification)
• Image: Handles the response as an image

This is particularly useful when working with APIs that return incorrect or missing Content-Type headers.

Debouncing limits how frequently an API can be called, which is useful when API requests are triggered by rapid user actions like typing.

Configure debounce

To set up debouncing:

1. 1

   Go to the Debounce field
2. 2

   Enter a value in milliseconds or use a formula

When an API call is triggered, Nordcraft waits for the specified time period before executing. If retriggered during this wait, the timer resets and starts again. The API call only executes after the specified time has elapsed without any new triggers.

Common use cases include:

• Search inputs where users type quickly
• Filtering controls that trigger on each selection
• Real-time form validation
• Preventing rate limit issues with external APIs

The timeout setting allows you to specify a maximum wait time for API responses.

Configure timeout

To set a timeout:

1. 1

   Go to the Timeout field
2. 2

   Enter a value in milliseconds or use a formula

If the API doesn't respond within this time, the request will be canceled and an error will be triggered.

This is particularly important for:

• Preventing SSR from hanging on slow API responses
• Improving user experience by failing fast when services are unresponsive
• Implementing fallback behaviors for unreliable APIs